What the Revenue Cloud is
You have been given a login and told it is "the new shop system". That is true and it is also not the whole picture. This page is the orientation before any of it becomes a screen you click.
What it actually replaces
The Revenue Cloud is a B2B commerce platform delivered as software-as-a-service. Nothing is installed on your servers, and you do not run an update project twice a year — revenexx runs the platform, you run your business on it.
For a typical Mittelstand distributor or manufacturer, it takes over work that today is spread across an uncomfortable number of places:
| What you do today | Where it lives now | Where it lives here |
|---|---|---|
| Product descriptions and technical attributes | ERP short texts, supplier Excel, a shared drive | The catalog — a full PIM |
| Customer-specific prices | ERP conditions plus a spreadsheet the Innendienst maintains | Price lists |
| "Which customer may see which assortment" | People's heads | Segments and price lists |
| Orders arriving by phone, fax and email | Retyped into the ERP by hand | Orders, placed by the buyer |
| Your customers' procurement systems | A PDF catalog you email once a year | Punchout |
| The shop itself | An agency project nobody dares touch | The storefront you edit yourself |
It does not replace your ERP. Your ERP stays the system that owns stock, invoices, credit management and the general ledger. The Revenue Cloud sits in front of it and is connected to it. Deciding which system owns which field is one of the first real decisions of a project — see Deciding your system of record.
The three surfaces
Three different things get confused in the first week, because all three are "the system".
The Cockpit is where you work. It is the admin interface at
app.revenexx.com, and it is the thing this Help Center mostly documents. Your
colleagues in product management, sales support and marketing log in here to
maintain products, prices, customers and orders. Buyers never see it.
The storefront is what your customers see. It is a separate, public website — your own domain, your branding — that reads its products, prices and stock from the same data the Cockpit edits. You can run more than one: a public shop, a spare-parts portal, and a closed customer portal can all be separate storefronts on one set of data. See How storefronts work.
The Console is the operational layer underneath. It is not a second application you log into — it is what provisions your tenant, keeps the registry of which apps you have installed, and handles your subscription. You meet it through the Cockpit's Settings section (team, domains, billing, API keys) and through App Studio, not as a separate URL.
Your tenant
Everything you do happens inside a tenant. One tenant is one company —
yours. It has an immutable identifier, a lowercase slug like max-mueller-gmbh,
that follows you through every part of the platform.
This matters more than it sounds. Your tenant is the boundary of your data: your products, your prices, your customers, your orders. The platform enforces that boundary in the database itself, not in application code, so no app — not even a badly written one — can read across it. Your data stays in Germany, on German-hosted infrastructure, which is why the DSGVO conversation with your compliance colleague is short.
Inside your tenant you can have several markets. A market is a distinct business context: Germany and Austria, a B2C side-brand, a second sales channel. Markets carry their own currencies, locales and tax treatment while sharing one product catalog. Set up markets before you set up prices — see Languages and markets.
The six Studios
The Cockpit is divided into six Studios, and so is this Help Center. Learning these six names is most of the navigation problem solved:
| Studio | What you do there |
|---|---|
| Commerce Studio | Products, prices, customers, orders. Where you spend most of your time. |
| Experience Studio | The storefronts buyers see — pages, media, domains, transactional email. |
| Integration Studio | Connecting the ERP, PIM and CRM you already run. Workflows, imports, webhooks. |
| Analytics Studio | Revenue, orders, products and customers as numbers, plus your own dashboards. |
| AI Studio | Model-driven help: content enrichment, assistants, agents. |
| App Studio | Which apps make up your platform, and what they are allowed to do. |
Each has a page here that says what it is for and which parts of the Manual document it — start at Studios.
Apps, and why the Cockpit looks different for different customers
The Revenue Cloud is not one monolithic program. It is a set of apps — Products, Prices, Customers, Orders, Inventories, Payments, Shipping, Markets and so on — that are installed into your tenant. Each app brings its own screens, its own data and its own settings, and the Cockpit's navigation is assembled from whatever is installed.
The practical consequence: a screenshot from another customer, or from a sales demo, may show a menu entry you do not have. That is not a bug and not a missing permission — it is an app you have not installed. Which apps you get by default depends on your subscription package. See Apps and the marketplace.
What to do with this
You do not need to understand all six Studios yet. You need three things: you work in the Cockpit, your buyers use the storefront, and everything sits inside your tenant. The next article turns that into something you can navigate with.
Next
- How the pieces fit together — the data flow, and how to guess where a task lives.
- B2B commerce basics — what makes selling to businesses different.