Headless commerce Composable / MACH API-first

Custom commercetools integration development

Appfront builds custom commercetools integrations for headless and composable e-commerce. Via the commercetools HTTP/REST and GraphQL APIs, we connect your catalogue, carts, orders and customers to your frontend, ERP, PIM or custom application. With OAuth2 scopes, API Extensions and Subscriptions, you stay in control of permissions and synchronise in real time, with no vendor lock-in on your storefront.

What is a commercetools integration?

commercetools is a composable commerce platform built on the MACH principles: Microservices, API-first, Cloud-native and Headless. Instead of one monolithic webshop, it offers separate, API-driven building blocks for catalogue, carts, orders, customers, prices and discounts. You decide which frontend, checkout and surrounding systems you connect to it, and you can renew each component independently.

In practice, a custom integration means: reading and updating products and categories via the HTTP/REST or GraphQL API, setting up OAuth2 clients with fine-grained scopes per project and store, connecting cart and order flows to your checkout, synchronising customer data with your CRM, and setting up event-driven processes with Subscriptions so that external systems move along in real time.

Appfront builds in line with the official commercetools HTTP API documentation and the OWASP ASVS security standard. We tailor scopes, queries, API Extensions and error handling to your actual commerce processes, so the integration grows with your product range and international catalogues and keeps running reliably even at peak volumes.

Headless catalogue

You manage products, variants, attributes and categories through the HTTP/REST or GraphQL API. Your frontend controls its own presentation; the catalogue remains the single source of truth and can be managed centrally across all sales channels.

Carts & orders

Carts, prices, discounts and orders run through the cart and order APIs, with optimistic concurrency based on version numbers. This keeps checkout and back office consistent, even with simultaneous updates and high volumes.

Event-driven sync

With Subscriptions, you receive real-time events when orders, products or customers change, via Google Cloud Pub/Sub, AWS SNS/SQS or Azure Event Grid. API Extensions add synchronous validation or enrichment to an API call.

Our development process for commercetools integrations

We follow a proven method that removes uncertainty early and delivers a stable integration. From an initial analysis of your commerce processes, projects and scopes through to go-live and ongoing maintenance, every step is aimed at an integration your own team can understand and trust.

1
Analysis & scope

We map out which resources you want to integrate (catalogue, carts, orders, customers), which projects and stores are involved, which OAuth2 scopes are needed, and whether event-driven processes via Subscriptions come into play.

2
Architecture

We design the integration architecture, choose between HTTP/REST and GraphQL for each use case, set up OAuth2 clients with least-privilege scopes, and define an error-handling and retry strategy.

3
Development

We implement the queries, API Extensions and Subscriptions with automated tests, structured logging and monitoring. You see working builds along the way.

4
Go-live & maintenance

A controlled go-live with data validation and a safety net, followed by ongoing maintenance, client credential rotation and further development.

What a commercetools integration delivers in practice

Every commercetools integration is tailored to your catalogue, commerce flows and adjacent systems. Below are the features we deliver most often for organisations that use commercetools at the core of their composable commerce stack.

HTTP/REST API & OAuth2

Authentication via OAuth2 with access tokens and fine-grained scopes, such as manage_products or view_customers per project, or store-specific scopes. Each integration gets exactly the permissions it needs, and all requests run over HTTPS with optimistic concurrency.

GraphQL API

The GraphQL API lets your frontend request exactly the fields it needs, meaning less over- and under-fetching and faster storefronts. Access works through the same scopes as the REST endpoints, so permissions stay consistent across both APIs.

Product & catalogue sync

We synchronise product types, variants, attributes, categories and prices between your PIM or ERP and commercetools. With user-defined keys, data stays consistent across staging and production, and international catalogues remain centrally manageable.

Carts & orders

We connect carts, line items, discounts and orders to your checkout and back office. Version-based updates prevent race conditions, and order events can flow straight to your ERP, OMS or fulfilment system via Subscriptions.

Customers & customer groups

You manage customer accounts, addresses and customer groups through the API, with separate view and manage scopes. You can securely synchronise customer data with your CRM, and groups form the basis for B2B pricing and audience-specific discounts.

API Extensions & Subscriptions

API Extensions run your own logic synchronously on a call to carts, orders, payments or customers, for validation or enrichment. Subscriptions deliver events asynchronously to message brokers (Pub/Sub, SNS/SQS, Event Grid) in CloudEvents format, for reliable event-driven webhooks.

Typical use cases in practice

A commercetools integration looks very different from one organisation to the next. We see a number of patterns come up often, and for each of them we have a working setup that pays attention to scopes, catalogue sync and the right cart, order and event logic.

Enterprise retail

Large retailers and brands building a headless storefront on commercetools who want to manage their catalogue, prices and orders centrally across web, app and marketplaces. We connect your frontend, PIM and ERP via REST and GraphQL. See also our e-commerce development and API integrations.

B2B commerce

Wholesalers and manufacturers with customer-specific prices, business units, approval flows and orders on account. Customer groups and store-bound scopes enable separate catalogues and prices per customer group, with orders flowing through to your ERP. See also middleware.

Headless & composable

Organisations that want to renew their frontend, checkout and backend independently of one another, following MACH principles. We build the integration layer between commercetools and your own storefront, payment providers and search or CMS systems. See also our web app development.

International & multichannel

Brands selling in multiple countries, languages and currencies via web, app, marketplaces and physical channels. With multiple projects, stores and local catalogues, we serve every channel from a single platform, while Subscriptions keep external systems synchronised in real time.

Technology we use

We build commercetools integrations using the official HTTP/REST and GraphQL APIs, combined with the backend stack that suits you. The exact choice depends on your frontend, message broker and adjacent systems, following MACH and composable principles so that your own team can manage or renew each component independently.

commercetools HTTP/REST API commercetools GraphQL API OAuth2 with scoped access tokens Projects, stores & channels Products, carts, orders & customers API Extensions Subscriptions & messages Google Cloud Pub/Sub AWS SNS / SQS Azure Event Grid CloudEvents Node.js / Java / Python / .NET / Go PIM / ERP / OMS integrations MACH & composable commerce Optimistic concurrency (versioning) GitHub Actions

Why Appfront for your commercetools integration?

Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes, because an integration must not only be technically sound but also add practical value to the way you work.

For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.

You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also take a look at our broader services around API integrations, middleware, e-commerce development, custom software and web app development. Working with a different platform? Check out our integrations for Shopware and BigCommerce.

  • Experience with the commercetools HTTP/REST and GraphQL APIs
  • Familiar with OAuth2 scopes, projects, stores and channels
  • Builds event-driven integrations with API Extensions and Subscriptions
  • Thinks along on MACH and composable architecture, not just code
  • Secure by default: client credential rotation, signature validation, least-privilege scopes
  • Structured error handling and retry mechanisms
  • Extensive logging and monitoring from day one
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance and proactive further development

Security and privacy in commercetools integrations

Orders and customer accounts always contain personal data, and catalogue and pricing data are commercially sensitive. Appfront builds in line with commercetools security best practices and the OWASP ASVS. Among other things, that means client credentials in secure vaults, signature validation on incoming Subscription events, least-privilege OAuth2 scopes per project and store, and regular audits of the order and customer flows.

commercetools runs API-first over HTTPS with TLS and OAuth2, where each API client receives only the scopes strictly necessary, for example view_customers instead of manage_customers where read access is enough. We document the data flows, scopes and customer personal data processed so that your record of processing activities is complete and you can demonstrably comply with the GDPR.

More about our approach to security: information security policy and CVD policy.

  • GDPR-compliant data processing and minimisation
  • Encryption in transit (TLS 1.2+) and at rest
  • Least-privilege OAuth2 scopes per project and store
  • Audit logs with traceable data flows
  • Automatic retry and dead-letter queues
  • Monitoring and alerting for anomalies
  • Secrets management following best practices
  • Documentation for your record of processing activities

Frequently asked questions about commercetools integrations

Answers to the questions we get asked most often about commercetools implementations.

A commercetools integration is a technical integration between the commercetools platform and another system, such as your headless frontend, ERP, PIM, OMS or in-house application. Products, categories, carts, orders and customers are read and updated programmatically via the commercetools HTTP/REST API and the GraphQL API. Authentication runs via OAuth2 with scoped access tokens. With API Extensions you add your own business logic synchronously to an API call, and with Subscriptions you receive events asynchronously whenever something changes in a project.

commercetools is a composable commerce platform built on MACH principles: Microservices, API-first, Cloud-native and Headless. It suits enterprise and mid-market retailers who want to control their own frontend and customer experience, manage international catalogues and multiple sales channels, or serve both B2C and B2B from a single platform. If you need a simple, standardised webshop, we'll look with you at whether a more traditional platform is a better fit.

A first integration, such as setting up OAuth2 authentication and reading a product catalogue via the HTTP API or GraphQL, can be up and running relatively quickly. A full composable setup with catalogue sync from a PIM, cart and order flows, customer integration and event-driven processes via Subscriptions usually takes longer. After an intake conversation in which we map out your projects, scopes and data flows, we'll give you a realistic estimate.

We work with the official commercetools HTTP/REST API and the GraphQL API, using OAuth2 for authentication and fine-grained scopes per resource. On the backend, we choose the stack that suits you: Node.js, Java, Python, PHP, .NET or Go. For event-driven integrations, we use Subscriptions on a message broker such as Google Cloud Pub/Sub, AWS SNS/SQS or Azure Event Grid, with CloudEvents as the format. We handle synchronous validation and enrichment with API Extensions.

The cost depends on the number of systems to be integrated, the complexity of the catalogue and order data flows, the scopes and stores you need, and the amount of custom business logic via API Extensions and Subscriptions. Ongoing maintenance, monitoring and support also affect the total investment. After a no-obligation analysis of your situation, we always provide a clear quote.

Yes. commercetools works API-first over HTTPS with OAuth2 and scoped access tokens, so every integration only gets the permissions it strictly needs. Appfront builds in line with OWASP ASVS: client credentials in secure vaults, least-privilege scopes per project and store, signature validation on incoming Subscription events and separate permissions per integration. We document the data flows, including any customer personal data being processed, so your record of processing activities stays complete and you can demonstrate GDPR compliance.

Yes. Appfront regularly takes over the maintenance of existing commercetools integrations, even when they were originally set up by another party or system integrator. We review the API clients and scopes, the GraphQL and REST queries, the API Extensions and Subscriptions, and the error handling, document the current setup and draw up improvement proposals. From that point on, we can handle changes, extensions and monitoring, including timely rotation of client credentials.

commercetools targets enterprise and mid-market e-commerce businesses that want to work headless or composable: international retailers with multiple catalogues and channels, brands serving both B2C and B2B, and organisations that want to be able to renew their frontend, checkout and backend independently of one another. Typical use cases include a headless storefront on the catalogue and cart APIs, synchronising product data with a PIM, passing orders on to an ERP or OMS, and event-driven processes via Subscriptions. For small, standardised webshops, we'll look with you at whether a simpler platform is a better fit.

Ready to build your commercetools integration?

Tell us which resources you want to integrate — catalogue, carts, orders or customers — and which frontend, PIM, ERP or message broker commercetools needs to work with. We're happy to think along on scopes, API Extensions, Subscriptions and the composable architecture. A no-obligation first consultation quickly gives you a clear picture of what's possible.

Edit content