commercetools pricing and store costs in 2026

Preparing a commercetools budget? Separate the platform quote from storefront, catalogue and checkout work so the full operating cost is visible.

commercetools pricing uses an order-based quote from its sales team. A working store budget also needs the storefront, implementation work and continuing service costs around that quote. The proposed architecture determines which of those costs you must fund.

How commercetools pricing is quoted

commercetools’ pricing page describes an order-based model and directs buyers to sales for a proposal. It contrasts this with charging on gross merchandise value, the total value of sales. The page also describes unlimited catalogues, channels and storefronts.

The published add-ons include Checkout, additional regions and connectors, Premium Support, Audit Log Premium and advanced B2B APIs. Ask the proposal to name every included product and each separately priced option. A product appearing in an architecture diagram does not establish that it is included in your contract.

The sales contact page starts with a discovery call about your challenges and next steps. Prepare order forecasts and the store requirements below for that discussion. Those are budgeting inputs, not a published formula for calculating a fee.

Have the commercial proposal state the order definition, contracted volume, billing period and treatment of excess usage. Record the currency, tax treatment, minimum commitment and renewal terms alongside the quoted amount. Use the written terms to model spend instead of applying an assumed rate per order.

Separate the commerce engine from the storefront

A composable store combines services that you can select separately. commercetools’ architecture guide describes independent commerce APIs alongside Frontend for the storefront, Checkout for checkout and Connect for integration connectors. It says these products can be adopted independently.

An illustrative retail design could use commercetools commerce APIs, Frontend and Checkout, with an existing warehouse system supplying stock. This is an example architecture, not a standard package. Your proposal needs to price the selected products and the work between them.

Store requirementDecision to put in the briefCost to allocate
StorefrontUse Frontend or build another customer interfaceTemplates, hosting responsibility and release support
Editorial contentDecide where landing pages and buying advice are editedContent migration and any content-management subscription
SearchDefine product search, filters and ranking requirementsConfiguration, indexing and any separate search service
PaymentsUse Checkout or build a custom checkout flowIntegration work and payment-provider charges
IntegrationChoose connectors or custom connections to existing systemsConnector subscriptions, development and monitoring

Product search can use the capabilities already in your store design. Reusing your content-management system also avoids buying a replacement subscription. Price each capability against the selected design and reuse existing services where they meet the requirements.

Checkout itself has different implementation boundaries. Complete Checkout handles the checkout interface and flow, while Payment Only leaves the surrounding flow to your team. Both choices need a defined payment provider. The guide to ecommerce payments explains the processing responsibilities to include in that work.

Cost the catalogue-to-checkout workflow

Budget for the data moving through the store, including the checks that prevent a stale product answer from becoming an incorrect basket. The following example assigns responsibilities to a retailer with a separate product-information system and warehouse system.

Information or actionResponsible system in this exampleWork to price
Product attributesProduct-information system supplies descriptions, materials and variant identifiers to commercetoolsField mapping, publication rules and rejected-record handling
Selling pricecommercetools selects the price for the applicable currency, country, customer group and channelPrice import and tests for customer-specific prices
Available stockWarehouse system supplies stock updates to commercetools inventory by SKU and supply channelSync frequency, failure alerts and reconciliation
Basketcommercetools Cart stores the chosen variants and quantitiesStorefront cart actions and refresh rules
Payment and orderCheckout connects payment processing to cart-to-order conversionPayment failure, retry and duplicate-order handling
Delivery progressOrder-management and carrier systems supply fulfilment eventsStatus mapping and customer access checks

commercetools supports embedded and standalone prices. Its inventory API tracks stock per SKU and, optionally, per supply channel. Decide which upstream system can change each value so two integrations do not overwrite each other.

A cart line item is a snapshot of a product variant. Later product changes do not automatically update that snapshot. Include the required cart refresh behaviour in the build and test price changes between adding an item and paying.

Shopping support needs the same ownership map. Product questions use the approved catalogue attributes, availability questions use stock data and order questions use authenticated order information. Delivery promises and returns eligibility also need the retailer’s policy documents. An order status alone cannot explain a returns exception.

Specify how quickly changes must reach every customer-facing service and what happens when an update fails. For example, require the team to demonstrate a warehouse stock change reaching both the storefront and shopping support. Use product feed optimisation to prepare the attributes those services need.

Implementation and continuing operations

Implementation pays for the store to launch. Continuing operations pay for it to remain available and for its connections to keep working.

Budget categoryInitial project workContinuing spend
Design and storefrontPage design, templates and checkout presentationPlanned design changes and frontend maintenance
MigrationCatalogue cleanup, customer mapping and import rehearsalsLater imports and changes to the data model
IntegrationsConnections to warehouse, finance and payment systemsMonitoring, incident response and connector changes
Platform and servicesConfiguration and launch supportContract charges and selected subscriptions
OperationsMonitoring setup, recovery procedures and staff trainingHosting you own, alerting and support cover

More attributes and customer-specific prices can expand mapping and testing work. More traffic can change the capacity required by your own storefront or connected services. Those are implementation and operating effects, not evidence of a commercetools traffic surcharge.

The published platform model is order-based, so request scenarios with different order volumes under the proposed contract. Additional channels need their own integration and testing estimate even where the pricing page describes unlimited channels. Include separately selected regions or connectors when they change the package.

Ask who handles failures across suppliers. A support agreement for the commerce service does not assign ownership of your warehouse connection or custom storefront. Put incident triage and recovery responsibilities in the operating proposal.

Ask for a comparable total-cost proposal

Give every supplier the same requirements and ask for an initial project total plus recurring spend over the same period. Use this checklist to prevent a cheaper-looking proposal from omitting part of the store.

  • State product and variant counts, attribute types and expected catalogue changes.
  • List countries, currencies, customer groups and required sales channels.
  • Supply expected order volumes and peak traffic separately.
  • Name the storefront, content and search services to retain or replace.
  • Define checkout mode, payment methods, shipping rules and tax requirements.
  • Identify the source of stock and the permitted delay before customers see changes.
  • Include product questions, policy answers and order support in the data requirements.
  • Request migration scope, launch acceptance tests and responsibilities after launch.
  • Require contract inclusions, usage rules and payment-processing charges as separate lines.

For an illustrative budget worksheet, keep the initial project total in one field and monthly operating spend in another. First-year spend adds the project total to twelve months of recurring spend, plus usage charges and transaction fees. If a service bills annually, include its annual amount once. Keep tax treatment consistent across the worksheet.

A second-year budget removes completed migration work but retains maintenance and contracted services. Add any planned expansion as a separate project. Ask suppliers to return both periods against the same requirements so you can see what the store costs to launch and to run.

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.

See it in actionFree trial · Simple setup