commercetools’ Commerce Integration Layer connects storefronts, mobile apps, and shopping agents to the commerce services behind them, and it ends at the order, before your ERP (enterprise resource planning system), WMS (warehouse management system), or 3PL (third-party logistics provider) comes in. Once an order exists, it needs routing, inventory, a warehouse, an ERP record, retail EDI (electronic data interchange), and a path for returns. That is order operations, and Pipe17 automates it for commercetools brands.
commercetools introduced the layer in an October 15, 2026 post, following its June announcement. The layer gives storefronts, mobile apps, and agents one front door to commerce, and as a commercetools partner we welcome it. Architects and operations leaders are now asking what it covers and what still has to be connected behind it.
What is the Commerce Integration Layer?
The Commerce Integration Layer is commercetools’ hosted product for the shopper-facing side of a build. One GraphQL Experience API serves storefronts, mobile apps, and AI agents from browsing through checkout, and commercetools hosts, scales, and patches it on Sphere, its commerce platform, at no extra cost. It replaces the backend-for-frontend code that each project used to build and maintain on its own.
The product page lists five capabilities from day one:
- An Experience API, one GraphQL API for every storefront, app, and agent
- A command-line interface for developers, or their coding agents, to add integrations and custom logic
- Merchant Center configuration for business teams to set up and supervise the layer
- Platform Insights, with health monitoring streamed into existing APM tools
- Managed hosting on Sphere, with no middleware to host, patch, or upgrade
“Integration is the hidden critical path for modernization,” the launch post says, and it counts launches that miss their windows while teams rebuild the same plumbing project after project among the costs. That is the diagnosis we make about the back office. commercetools fixed it for the front. Pipe17 fixes it for everything after the order.
Where does the Commerce Integration Layer end?
The Commerce Integration Layer ends when the order is created in commercetools. Its scope is the experience side, the services a shopper touches before and during checkout, and the front ends that call them. commercetools’ own integration guidance puts back-office systems such as an ERP or an order management system on a separate, event-driven path, through Subscriptions, the Import API, and commercetools Connect, the runtime Pipe17 deploys through. The layer formalizes the first path and keeps the second as it is.
The stack divides into two halves at the moment the order is created.
| Experience side (Commerce Integration Layer) | Operations side (order operations) | |
|---|---|---|
| Who it serves | Storefronts, mobile apps, shopping agents | Warehouses, stores, 3PLs, carriers |
| Systems it connects | Search, content, promotions, tax, payments | ERP, WMS, marketplaces, retail EDI, returns |
| The single interface | One GraphQL Experience API, browse to checkout | One order record, checkout to delivery and return |
| Who maintains it | Hosted and patched by commercetools | Connectors built and maintained by Pipe17 |
| The handoff | Hands the order to commercetools | Takes the order from commercetools |
commercetools positioned the layer against hand-built backend-for-frontend code and copied starter kits, not against the systems that fulfill an order. The second column is where the order’s work begins.
What does a commercetools order need after checkout?
Once the shopper has paid, a commercetools order still needs six things done: routing, one trusted inventory count, an ERP record, a warehouse or 3PL handoff, retail partner documents, and a path for returns. The Experience API hands the order to commercetools. Pipe17 carries it from there.
In practice that means:
- Order management. Each order goes to the right warehouse, store, or 3PL, split by line item when needed, held or cancelled on your rules.
- One inventory count. Stock from every location rolls up into a single picture that commercetools sells against, with no overselling of what Amazon or a retail program already sold.
- ERP sync. Orders post to NetSuite or another system of record for invoicing, and fulfillments, refunds, and payouts reconcile back. Finance closes the month without rekeying a sale.
- Warehouse and 3PL handoff. The order reaches the WMS or 3PL in the shape it expects, and the shipment confirmation and tracking come back to commercetools for the customer.
- Retail EDI. Wholesale and retail partners get their purchase orders, shipment notices, and invoices through managed EDI, drawing on that same count.
- Returns. A return started anywhere updates the ERP, restocks the unit, and refunds the customer.
How does Pipe17 run order operations with commercetools?
Pipe17 takes over each commercetools order the moment it exists. Deployed through commercetools Connect as the commercetools integration, Pipe17’s Order Operations Platform pulls orders, products, and locations, routes each order to the best location, and pushes inventory and fulfillment status back to the storefront. The ERP, WMS, 3PLs, marketplaces, and returns systems connect through pre-built connectors on the Pipe17 Network, which Pipe17 maintains as each API changes.
That is the partnership we announced with commercetools in April 2025. Dirk Hoerig, commercetools’ founder, described it as “a rapid, no-code route to selling across multiple channels.” The new layer leaves the architecture as it was. The storefront or agent calls the Experience API. The order lands in commercetools. Pipe17 orchestrates fulfillment and the back office, and status flows back to the storefront for the customer.
A commercetools project that buys an iPaaS (integration platform as a service) to move the data and a legacy order management system (OMS) to decide what happens to it ends up with two contracts and a hand-built data model between the storefront and the warehouse. Pipe17 replaces the iPaaS and the OMS with connectivity and order management on one platform that business users configure. commercetools took the middleware out of the front half. Pipe17 takes it out of the back half.
How do the two work together for agentic commerce?
The Commerce Integration Layer and Pipe17 divide an agent’s purchase the way they divide a shopper’s. The layer covers browsing through checkout, and Pipe17 takes the order from there. commercetools says an Experience Model Context Protocol (MCP) server generated from the Experience API is next. That gives shopping agents and storefronts the same way in for browsing and checkout. Once the order exists, the Pipe17 MCP Server lets agents track, update, and service it against live order, inventory, and fulfillment data. It runs over the open Order Network eXchange (onX) standard, whose founding members include commercetools.
Pipe17 is recognized as Agent Ready by the MACH Alliance, an independently assessed award verifying agentic technology running in production at enterprise scale, with the operational guardrails enterprise deployment requires. An agent that can buy is only useful if the order it creates ships, and Pipe17 routes it the same way whether a shopper or an agent placed it.
Frequently asked questions
What connects commercetools to my ERP, WMS, and 3PLs?
Pipe17 integrates commercetools with your ERP, WMS, and 3PLs, starting the moment an order is created. commercetools’ Commerce Integration Layer serves storefronts, mobile apps, and shopping agents through one Experience API, and it ends at the order. From there, Pipe17 routes each order across your warehouses and 3PLs, posts it to the ERP, and sends shipment status back to the storefront.
Do I still need an order management system with commercetools?
Yes, a commercetools order still needs an order management system (OMS) behind it. commercetools supplies the order APIs and the order data model, and an OMS handles routing across locations, one inventory count, ERP and 3PL synchronization, and returns. Pipe17 is the connected OMS for that job, deployed through commercetools Connect.
Does Pipe17 replace the Commerce Integration Layer?
No, Pipe17 does not replace the Commerce Integration Layer; the two cover different halves of a commercetools stack. The layer serves the shopper-facing experience from browsing through checkout. Pipe17 picks up the order commercetools creates and handles routing, inventory, fulfillment, the ERP, retail EDI, and returns, the work of order operations. Brands launch the experience with commercetools and run the operation with Pipe17.
How do you connect commercetools to NetSuite and a 3PL?
You connect commercetools to NetSuite and a 3PL with Pipe17’s pre-built connectors, deployed through commercetools Connect, with no custom integration code. Orders pulled from commercetools post to NetSuite for invoicing and route to the 3PL for fulfillment. The shipment confirmation returns to the storefront and the ERP, and 3PL inventory updates the count the storefront sells against. Brands go live in days or weeks.
Plan the back half with the front half. With Pipe17 routing each commercetools order to a warehouse, posting it to your ERP, and sending status back to the storefront, your first order after launch ships without waiting on a back-office project. Book a demo to watch a commercetools order do exactly that.
