Commerce & Payments · Integration
Demandware
Add Demandware to your product for your customers, and give your AI agents governed access to it.
Embed a Demandware integration, now sold as Salesforce B2C Commerce, so your customers can work their own products, catalogs, orders, and shoppers from inside your product. Writes are idempotent, so a retry cannot duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it. Each storefront is configured differently, so catalog and attribute mapping is configuration per customer rather than code on your side.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own product catalog and pricing into your product, mapped to their attributes.
Read orders and shopper records so your product works from the same commerce data as the storefront.
Write product, inventory, or order updates back from your product without a nightly file.
Trigger your product when an order is placed, updated, or refunded.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up an order and its line items before answering a shopper question.
An agent updates a product or order record within governed permissions, with the action audited.
An agent reacts to a new order and runs the next fulfilment or entitlement step.
Example prompt
Find orders placed in the last 48 hours that are still unfulfilled and group them by shipping method.
Set up Demandware in 4 steps
- 01Open the Demandware connector from your fastn dashboard.
- 02Have each customer authenticate their commerce instance with least-privilege credentials.
- 03Map the catalog, order, and customer fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Demandware integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Demandware integration without building it. Your customers connect their own Demandware 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 Demandware update is not your on-call problem.
- One integration serves your product and your agents. The same governed Demandware 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
StripeWorks well with
SalesforceOften used alongside
Tools the same teams tend to run next to Demandware, across other categories.
NetSuite
Notion
Box
DocusignDemandware integration FAQ
How do I add a Demandware integration to my product?
Enable the Demandware connector in your fastn dashboard, then let each customer authenticate their own Demandware account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Demandware client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Demandware account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Demandware 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 Demandware 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 looks up an order and its line items before answering a shopper question.
Who maintains the Demandware integration?
fastn does. When Demandware 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 Demandware 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 Demandware integration?
A common starting point: read their own product catalog and pricing into your product, mapped to their attributes. 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 Demandware integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Demandware does not change your per-connector cost. You can start free with 3 connected accounts.
Add Demandware to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.