Experience Studio

Build customer-facing B2B commerce storefronts and themes on top of revenexx Revenue Cloud

This section is for frontend developers who are building a storefront for a B2B commerce customer. In Cockpit, customers manage their sites, domains, pages, media, and themes in Experience Studio; this section is the developer's side — how you build the storefronts and themes they run. New here? Start with the tutorials.

That usually means you're at a partner agency or on a customer's own product team, and you're shipping the website that the customer's buyers will use to log in, browse catalogs, place orders, and manage their accounts.

What you're actually building

A storefront on revenexx is a Nuxt 4 application running as the customer-facing shopfront. The platform gives you a substantial head start — multi-tenant data, identity, catalog, checkout primitives, search — and your job is to wrap that in a brand experience that fits the customer's business.

In practice, a storefront project usually involves four kinds of work:

  1. Composition — laying out pages that the customer's marketing team can edit themselves. That's where Blökkli (the visual block builder) comes in: pre-built blocks like Hero, Product Grid, FAQ, plus your own custom Vue components if needed.
  2. Customization — tailoring the checkout to the customer's order process. Most B2B checkouts need things a B2C template doesn't have: cost centers, approval flows, ERP-validated SKUs, contract-priced line items. Formily-driven forms make this configurable per customer without a rebuild.
  3. Identity — wiring up login, registration, and password recovery. Buyers authenticate through Customers, the platform's buyer identity, which is separate from the admin/Cockpit identity (signed in through ID). You consume an SDK; you don't roll your own auth.
  4. Branding — applying the customer's visual identity. Theming is done with CSS custom properties so the same codebase can be themed per tenant without rebuilds.

What you don't have to build: multi-tenancy plumbing, the catalog data model, the order system, payment integrations, the search infrastructure, user roles. Those come from the platform.

What you'd typically build with this

Three realistic project types:

A wholesaler webshop for a Mittelstand distributor. Buyers log in, see their contract pricing, browse SKUs, place orders that flow into the customer's ERP. You build on top of the standard Nuxt template, customize the checkout for net-30 payment terms and cost-center routing, and theme it to the customer's brand. Most of the work is in the integration between the storefront and the ERP — which is itself usually built in Integration Studio, not directly in the storefront.

A spare-parts portal for a manufacturer. Each registered workshop sees parts compatible with their installed equipment. You wire identity to a customer database, customize the catalog views to show compatibility data, and add a quick-reorder workflow on the account page.

A configurator-driven storefront for industrial supplies. Buyers configure complex products (e.g. cable assemblies with specs) before adding them to the cart. You build custom Vue components for the configurator, and the rest (catalog, cart, checkout, account) comes from the standard template.

In all three, the unique work is in the customization and integration. The boilerplate (multi-tenant data, identity, basic checkout flow) is solved by the platform.

What's in this section

The pages here go progressively deeper:

  • Architecture — How the storefront fits together: Nuxt 4, the BFF pattern between browser and platform APIs, how Blökkli renders pages, and how multi-tenancy works in the storefront layer.
  • Checkout — The 4-step checkout flow (cart, address, payment, confirmation), how Formily lets you customize forms per customer, and the PCI-safe Stripe integration pattern.
  • Authentication — Login, registration, and password reset for buyers. JWT sessions, route protection, and what the SDK does versus what you write.
  • Theming — CSS custom properties for per-tenant branding. Preview — token list may evolve.
  • Blökkli Blocks — The visual page builder. Preview — integration is in progress (PO-46).

Building, deploying & operating

Reference pages for getting a storefront live and running:

Where to go next

If you're new to revenexx as a whole, start with Platform Overview. If you already understand the platform and are ready to build, go straight to Architecture to see how the storefront actually fits together.

Was this page helpful?