commercetools

commercetools separates commerce services from the storefront built around them. A development team can use its APIs for a custom consumer shop or a company purchasing system, then manage the project in Merchant Center. The commercial model is based on orders rather than a percentage of gross merchandise value.

A buyer approval flow

The documented B2B launchpad storefront has desktop approval controls under My Account > Approval Rules. Choose Add approval rule, name the rule and select the requester roles. Add conditions, using AND or OR to combine them, then specify the approving roles. Groups and tiers define who must decide and in what order, with up to five approval tiers.

Save the rule as active or inactive. A saved rule cannot be deleted; set it inactive when it should stop applying. Only one rule applies to an order. Buyers review pending decisions through Approval Flows and can approve or reject with a note.

Those instructions concern the B2B launchpad implementation. A custom storefront still needs its own buying interface and integration work.

Trial scope and commercial access

Choose the Merchant Center region, create an account and follow the emailed verification step to set a password. The setup guide supports sample data or a project started from scratch. An invited colleague can join an existing organization.

The 60-day trial includes core commerce APIs and Merchant Center, with B2C and B2B examples. It excludes Frontend, InStore and agentic services, so it does not evaluate every product used in a complete deployment. The project does not automatically become a paid production contract at expiry.

Production pricing is supplied by sales. Advanced B2B, premium audit logs and performance-testing support are separately scoped additions. Catalogue, channel and storefront counts are not the base order-pricing measure; estimate the order workload and the additional services the project actually needs.