Getting Started
You have a login and a project with a deadline. This area is the hour of reading that makes everything after it faster. It is deliberately short: four groups, sixteen pages, and each one tells you where to go next.
The rest of the Help Center is large. Getting Started is not. If a page here starts explaining a screen in detail, it has gone wrong; the detail lives in the Guides and in Product Help, and every page here links to them at the point you need them.
Meet revenexx
What the platform is and why it is shaped the way it is. Read these before you click anything, because most of the product's decisions follow from how businesses buy from each other.
- What the Revenue Cloud is: the Cockpit, the storefront, your tenant, and what it replaces.
- How the pieces fit together: product data, prices, customers, orders, storefront, in that order.
- B2B commerce basics: negotiated prices, companies as customers, approvals, punchout.
- B2B commerce glossary: the vocabulary, in plain language.
Cockpit tour
Where things are. Ten minutes on the shape of the screen saves a week of searching menus.
- Tour the Cockpit: the dashboard, the Studio rail, the topbar, and where each job lives.
- Understand the Studios: the six Studios, what each is for, and which two are still on their way.
First setup
Six short walkthroughs, in the order that works. Each one gets one real thing into your tenant and hands you on to the guide that goes deeper.
Go live
The road from a working tenant to a shop your customers use.
- Going live: the first week of foundations, and the months after it, in the order that pays off.
- Go-live checklist: six questions to answer before you point a domain at the shop.
Where to go afterwards
Three doors into the rest of the Help Center. Solutions starts from a business outcome such as sell spare parts online. Guides is the manual, one book per subject, and most first projects begin with Product data. Product Help mirrors the Cockpit screen by screen, for the moment you are looking at a field and want to know what it does. When something is broken, the FAQ collects the questions we hear most, each with a one-paragraph answer and a link.