Commerce & Payments · Integration
BigCommerce
Add BigCommerce to your product for your customers, and give your AI agents governed access to it.
With a BigCommerce integration embedded in your product, a store owner authorises their own store and your app works the catalogue, orders, customers, carts and price lists in it. The detail that trips people up is addressing: every request is namespaced by a store hash rather than by a domain, and the platform runs two generations of API side by side. Catalogue, customers and price lists live in V3 with a consistent envelope and pagination, while some order and shipping surfaces still answer on V2 with different field names and different paging. Knowing which version owns a resource is half the work. fastn keeps each store's hash and token, spans both API versions and absorbs the changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a store owner authorise their own store so your product reads their catalogue and writes orders without you tracking store hashes by hand.
Publish tiered or contract pricing through price lists so a B2B store shows the right number to the right customer group.
Work order and shipping data on V2 and catalogue data on V3 through one connector, instead of maintaining two clients.
Create and update customers and their addresses from your product, so checkout is not the only place records appear.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up an order, its shipments and its status before it answers a question about where a parcel is.
An agent adjusts a price list entry within scoped permissions, and the store and the entry are both recorded.
An agent reports which catalogue products are missing images or descriptions for one store.
Example prompt
Show orders awaiting fulfilment in this store and tell me which ones had a price list discount applied.
Set up BigCommerce in 4 steps
- 01Enable the BigCommerce connector from your fastn dashboard.
- 02Have each customer authorise their own BigCommerce 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 BigCommerce integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BigCommerce integration without building it. Your customers connect their own BigCommerce 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 BigCommerce update is not your on-call problem.
- One integration serves your product and your agents. The same governed BigCommerce 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
WooCommerce
WixOften used alongside
Tools the same teams tend to run next to BigCommerce, across other categories.
NetSuite
Notion
Box
DocusignBigCommerce integration FAQ
How do I add a BigCommerce integration to my product?
Enable the BigCommerce connector in your fastn dashboard, then let each customer authenticate their own BigCommerce account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BigCommerce client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BigCommerce account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BigCommerce 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 BigCommerce 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, its shipments and its status before it answers a question about where a parcel is.
Who maintains the BigCommerce integration?
fastn does. When BigCommerce 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 BigCommerce 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 BigCommerce integration?
A common starting point: let a store owner authorise their own store so your product reads their catalogue and writes orders without you tracking store hashes by hand. 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 BigCommerce integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BigCommerce does not change your per-connector cost. You can start free with 3 connected accounts.
Add BigCommerce to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.