Commerce & Payments · Integration
Shopware
Add Shopware to your product for your customers, and give your AI agents governed access to it.
Shopware is an open commerce platform with a large European merchant base, and it exposes two APIs for two different jobs: the Admin API for the shop's own data and the Store API for anything acting on behalf of a shopper. An embedded Shopware integration works through the Admin API on products and variants, orders with their line items and transactions, customers, categories and media, and it can react to entity changes rather than polling for them. What complicates the build is the platform's flexibility: sales channels, custom fields and plugins all change the shape of a shop, and a self hosted installation is not reached the same way as one on Shopware Cloud. Writes are idempotent, because a duplicated order is a real problem rather than a cosmetic one. fastn holds the per-shop credentials and follows the releases.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Shopware shop, self hosted or on Shopware Cloud, with no per-merchant code.
Write products, variants and prices into the sales channel the merchant nominates rather than a default one.
Read orders with their line items and transactions so your product acts on what was actually paid for.
Map the custom fields and plugin data a shop has accumulated as per-tenant configuration.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers what a shopper ordered and what state the payment is in, reading only that shop's records.
An agent updates stock or a price within scoped permissions, idempotently and audited.
An agent explains which sales channel an order came through before anybody opens the admin.
Example prompt
Which orders in this shop are paid but not yet dispatched, and what is in them?
Set up Shopware in 4 steps
- 01Enable the Shopware connector in your fastn dashboard.
- 02Have each customer supply credentials for their own shop, and note whether it is self hosted or on Shopware Cloud.
- 03Map the product, order and customer fields your product uses, including custom fields, then enable actions and change events.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Shopware integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Shopware integration without building it. Your customers connect their own Shopware 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 Shopware update is not your on-call problem.
- One integration serves your product and your agents. The same governed Shopware 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
BigCommerce
Magento 2Often used alongside
Tools the same teams tend to run next to Shopware, across other categories.
NetSuite
Notion
Box
DocusignShopware integration FAQ
How do I add a Shopware integration to my product?
Enable the Shopware connector in your fastn dashboard, then let each customer authenticate their own Shopware account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Shopware client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Shopware account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Shopware 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 Shopware integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent answers what a shopper ordered and what state the payment is in, reading only that shop's records.
Who maintains the Shopware integration?
fastn does. When Shopware 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 Shopware 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 Shopware integration?
A common starting point: let each customer connect their own Shopware shop, self hosted or on Shopware Cloud, with no per-merchant code. 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 Shopware integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Shopware does not change your per-connector cost. You can start free with 3 connected accounts.
Add Shopware to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.