Commerce & Payments · Integration
commercetools
Add commercetools to your product for your customers, and give your AI agents governed access to it.
commercetools is region-pinned: the OAuth host and the API host both carry the region, as in auth.us-central1.gcp.commercetools.com and api.us-central1.gcp.commercetools.com, and every request path begins with the project key. Tokens are issued by client credentials against an explicit scope list such as view_products:{project} or manage_orders:{project}, so an API client created with the wrong scopes fails at call time rather than at setup. Writes use optimistic concurrency: an update posts the resource's current version plus an array of update actions, and a stale version returns 409 rather than silently overwriting. Products exist as both a staged and a current projection, so a read has to state which one it wants or it will not see unpublished changes. Custom fields live in types you define per project, so field names are never the same across two customers. fastn stores each customer's client credentials, refreshes tokens and resolves the region and project routing for you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own commercetools project so your app reads their orders without a shared service account.
Push fulfilment status back onto orders as versioned update actions, retrying cleanly on a 409.
Read current product projections to keep a merchandising surface in step with what is actually published.
Create and update customer records from your own onboarding flow, including project-specific custom fields.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which orders are stuck awaiting payment, with every commercetools call audited per tenant.
Have an agent look up a cart and its line items before a support reply is drafted.
Let an agent apply a pre-approved order state transition and record the version it wrote against.
Example prompt
Which orders in our store are still awaiting payment?
Set up commercetools in 4 steps
- 01Enable the commercetools connector from your fastn dashboard.
- 02Have each customer authorise their own commercetools account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the commercetools integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a commercetools integration without building it. Your customers connect their own commercetools account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a commercetools update is not your on-call problem.
- One integration serves your product and your agents. The same governed commercetools connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to commercetools, across other categories.
NetSuite
Notion
Box
Docusigncommercetools integration FAQ
How do I add a commercetools integration to my product?
Enable the commercetools connector in your fastn dashboard, then let each customer authenticate their own commercetools account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no commercetools client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own commercetools account?
Yes. Every connection is scoped to the individual customer, so each authorises their own commercetools account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this commercetools integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which orders are stuck awaiting payment, with every commercetools call audited per tenant.
Who maintains the commercetools integration?
fastn does. When commercetools changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the commercetools integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the commercetools integration?
A common starting point: let a customer connect their own commercetools project so your app reads their orders without a shared service account. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the commercetools integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding commercetools does not change your per-connector cost. You can start free with 3 connected accounts.
Add commercetools to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.