commercetools B2B: model buyers, prices and orders
Map commercetools B2B business units, buyer permissions, tailored prices and order approvals to the storefront your team needs to build.
- Published
- Last updated
commercetools B2B provides business-to-business commerce services for company purchasing, with buyer permissions, tailored catalogues and negotiated orders. Your implementation connects those services to the buyer storefront and your business systems. Choose it when your team needs control over purchasing rules and can own that integration.
Separate platform services from the buyer storefront
commercetools separates commerce data and operations from the screens buyers use. A Business Unit can hold company purchasing context, while your storefront presents the permitted actions to each buyer.
There is an existing starting point for the interface. The Store Launchpad for B2B Manufacturing is a commercetools Frontend template. It includes company administration, quotes, orders and purchase lists, plus quick ordering and approval screens. Scope the work around adapting that template or building your own interface.
For example, a requirement to let branch staff reorder supplies needs more than an order-history screen. The commerce service needs the correct company context and permissions. Your implementation partner must connect the screen to those services, refresh prices and handle products that are no longer available. The merchant’s operations team must decide which staff can buy for each branch.
Write those responsibilities into the build scope. A supplied component can shorten interface work, while your team still owns its connection to your company data and fulfilment process.
Model business units and authorised buyers
Business Units model the buying organisation as a Company with Divisions beneath it. Customers become Associates through membership of a Business Unit, with Associate Roles defining their permissions.
Consider a fictional maintenance company with Perth and Melbourne branches. Create a Company for the organisation and a Division for each branch. A Perth buyer can have a purchasing role in Perth, while a head-office manager has the agreed access across branches. Decide explicitly which Stores, Associates and Approval Rules each Division inherits.
Sign-in establishes the person’s identity. Resource permissions determine what that person can do for the selected Business Unit. Associate Roles distinguish actions on the buyer’s own resources from actions on other Associates’ resources.
A buyer might create their own cart and request a quote without permission to edit another buyer’s cart. Giving that buyer order-creation permission is a separate decision. An approver needs the permissions and role required by the approval process.
The storefront must send requests in the authenticated Associate’s Business Unit context. The Associate access rules explain which endpoints enforce permissions. General seller endpoints skip Associate Role checks. Trusted middleware must resolve the buyer’s identity before calling Associate endpoints. A hidden button helps the interface, but the service must also reject the same unauthorised action submitted directly.
Design catalogue and price selection
Product Selections define assortments, while Stores connect those assortments with a selling context. Assign the appropriate Stores to Business Units so buyers use the intended range.
The assortment configuration supports inclusion and exclusion models. Specify the intended behaviour when a selection is inactive or empty. A configuration mistake can expose a wider range than the merchant intends.
Stores also connect distribution and supply Channels. These help organise price and stock context. The storefront’s search and product-detail requests must use the same permitted assortment as the cart.
commercetools supports Embedded Prices within variants and Standalone Prices linked by stock keeping unit (SKU). Its pricing documentation describes price scope through currency, country, Customer Groups and Channels. External pricing can supply amounts from another system when the implementation uses that approach.
Map each contract to a supported price-selection model. For example, assign a customer group for an agreed price level or a distribution Channel for a particular commercial agreement. Define the fallback when a matching price is absent, and show an unavailable state instead of inventing a zero price.
A price record alone does not enforce storefront confidentiality. The integration must prevent another company’s prices appearing in search results, product pages or cached responses. Revalidate the purchasing context when the buyer switches Business Units and before adding a product to the cart.
Connect quotes, approvals and purchase completion
The documented quote workflow moves a buyer’s cart through negotiation into an order. The seller prepares the offer, and buyer permissions govern the buyer’s actions.
- The buyer creates a cart in the correct Business Unit and submits a Quote Request from it.
- The seller accepts the request and prepares a Staged Quote. Its working cart lets the seller adjust quantities or negotiated discounts.
- The seller issues a Quote. A valid Pending Quote can be used to create an order with the negotiated prices.
- If the new order matches configured Approval Rules, commercetools creates an Approval Flow for that order.
Approval Rules define matching conditions and approver tiers. The Approval Flow records the decisions. All required approvals must be satisfied, and a rejection rejects the flow.
Keep order creation separate from release to fulfilment. The integration must hold an order that requires approval until the approval outcome permits release. Connect payment timing to that rule so a pending approval does not accidentally trigger the wrong capture or dispatch.
The launchpad’s checkout flow uses Checkout’s Payment Only mode and documents credit-card and purchase-order options. Your payment owner must connect the chosen provider and define authorisation, capture and failure handling. Purchase-order entry also needs your credit-control and invoicing rules.
Assign tax configuration to the merchant’s finance owner and its implementation to the commerce team. The enterprise resource planning (ERP) integration owner must map account references, purchase-order numbers and order lines. That owner must also reconcile order acceptance, fulfilment status and failures between systems.
Define a useful buyer-service experience
A useful buyer storefront lets an authorised customer complete a purchasing task with their own assortment and prices. Define acceptance outcomes for the jobs your buyers perform.
| Buyer task | Expected outcome | Implementation responsibility |
|---|---|---|
| Find a replacement part | Search by SKU or product attributes returns eligible variants with the buyer’s price | Search integration applies assortment and price context |
| Place a bulk order | The buyer enters several SKUs and quantities and sees a result for each line | Quick-order flow reports unknown, unavailable or unpriced items before submission |
| Repeat a purchase | Previous lines become a new cart with current availability and applicable prices | Reorder flow checks current permissions and stock |
| Ask about an order | The buyer sees status only for orders their role can access | Order service authorises each lookup before returning details |
Shopping assistance must use the same access rules. A conversational search result must stay within the buyer’s eligible catalogue. An order number supplied in a message must still pass an authorisation check before the service returns order details.
Keep these outcomes in the integration acceptance criteria. A fluent answer cannot compensate for the wrong contract price or another company’s order becoming visible.
Validate the integration contract
Validate company isolation with two fictional buyers whose catalogue access and prices differ. The following scenario specifies expected results for an acceptance test.
Company A can buy a pump and a restricted spare part. Company B can buy the pump only. Set the pump’s illustrative unit price to $90 excluding tax for A and $100 excluding tax for B.
When A signs in, its search results and cart must show $90 for the pump and permit the spare part. For B, the pump costs $100. The spare part stays denied or unavailable, including through a direct add-to-cart request. An A buyer without approval authority must also be denied when trying to approve their own pending order.
Repeat the checks after switching companies in one session and after changing an Associate’s permissions. Cached results must follow the new authorised context. Reordering must use the applicable current price, while ordering from a valid negotiated Quote must preserve that Quote’s agreed price.
Assign operational ownership before release. The catalogue integration owner sets the update schedule and handles failed imports. Your pricing integration owner controls contract-price changes and stale-price handling. The storefront team presents actionable errors without discarding the buyer’s cart. The ERP integration owner detects duplicate delivery attempts and reconciles each commerce order against its downstream record.
Require a named support owner for failed synchronisation and blocked orders. Accept the implementation when a denied action stays denied and every permitted purchase can be traced from buyer context to the correct downstream order.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.