Understand the Studios

The Cockpit is divided into six Studios, and so is this Help Center. Once you know what each Studio owns, you can guess where any task lives before you open a menu. This page is that map. It does not explain screens; the Product Help does that, one Studio at a time.

One sentence each

Commerce Studio

Where you will spend most of your time. It holds what you sell, what it costs, who buys it and what happened to their order, in four sidebar sections: PIM, CRM, Order Management and Configuration.

Read it as one sentence: a product says what it is, a price list says what it costs this buyer, an organization says who the buyer is, and an order records what all three agreed on. Every screen in the Studio serves one of those four. It is also the Studio that grows most, because most new apps add their screens here. See Commerce Studio.

Experience Studio

Where the data becomes something a person can look at. Sites are the deployed storefronts; Pages and blocks are their content; Domains connect a site to a hostname; Themes carry the look; Forms collect what the shop cannot sell directly; Messaging sends the order confirmations and password resets.

The one idea that ties it together: what renders depends on who is looking. An anonymous visitor, a logged-in contact and a contact with an approval role see three different pages from the same content, because visibility of prices, stock and order history is bound to the customer model in Commerce Studio. See Experience Studio.

Integration Studio

Where the Revenue Cloud talks to everything around it: your ERP, your PIM, your warehouse, and in the other direction your customers' procurement systems. A workflow reads, transforms and writes; a run is what happened when it executed; events are the platform's own signal that something happened; webhooks carry those signals across the boundary; Data Exchange handles the files, which in German B2B is still most of it.

You will open this Studio for two reasons: to build the ERP connection once, and to open Runs every time someone asks why the stock figures are stale. See Integration Studio.

Analytics Studio

When it arrives it is the place for prepared dashboards on revenue, orders, products and customers, and for building your own. The guide is written already, at the state the Studio will ship in, so the decisions you can make now, such as what counts as an order and which currency reports are in, are in Analytics.

AI Studio

The concept it grows into is described where it first applies: How smart reordering works explains how the platform reads a customer's order history to suggest the next order before the workshop runs out.

App Studio

The smallest Studio by screen count and the one with the widest reach. Every screen in the other Studios comes from an installed app: Products, Prices, Customers, Orders and the rest are apps themselves. App Studio is where you see which apps you have, install more from the Marketplace, read what each one is allowed to reach, and remove one without losing its data.

Two things follow. Your Cockpit is not the same as anybody else's, so a menu entry a colleague has and you do not is an installed app you lack. And the permission list at install time is a contract worth reading slowly. See App Studio.

Settings is not a Studio

The gear at the bottom of the rail opens your tenant's own administration: Team, Billing, Profile, Mail, Search, Auth & Security, API Keys, Git Accounts. It is about your company rather than your customers, and the Help Center covers it under Administration.

What to check

Pick three tasks from your own to-do list and name the Studio for each without opening the Cockpit. Fixing a product description: Commerce. Changing the text on the landing page: Experience. Finding out why the ERP did not get an order: Integration. If you got all three, the map is in your head.

Next

• Invite your team: the first walkthrough.
• Product Help: each Studio, screen by screen.