Commerce & Payments · Integration
WooCommerce
Add WooCommerce to your product for your customers, and give your AI agents governed access to it.
WooCommerce is a plugin rather than a hosted platform, so every store is somebody's own WordPress site. The API lives at that site's address, the credentials are a consumer key and secret generated inside their admin, and what a store can actually do depends on which extensions its owner installed. An embedded WooCommerce integration reads and writes orders and line items, products and their variations, customers, coupons and refunds, and subscribes to webhooks so a purchase reaches your product as it happens rather than on a poll. Two things bite in practice. Order status is a workflow rather than a flag, and shops rename and add statuses freely, so status is mapped per store. And writes have to be idempotent, because a retried order or refund on a live shop is money somebody then has to unpick. fastn keeps each store's endpoint and keys per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own WooCommerce store, its address included, since the API sits on their site rather than on a shared platform.
Read and write orders, line items and refunds so fulfilment or accounting steps run on what the shop actually recorded.
Create and update products, variations and stock levels so your product and the storefront never disagree about what is for sale.
Subscribe to order and customer webhooks so entitlement or delivery follows a purchase immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers what a shopper bought and where that order sits in the store's own status workflow.
An agent issues an approved refund idempotently, so a retry cannot return the money twice.
An agent reports which products in one store are close to running out of stock.
Example prompt
Which orders in this WooCommerce store are paid but still unfulfilled, and how old are they?
Set up WooCommerce in 4 steps
- 01Enable the WooCommerce connector in your fastn dashboard.
- 02Have each customer supply their own store address and a consumer key and secret generated in their WordPress admin.
- 03Map that store's own order statuses and product fields, then enable the webhooks and writes you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the WooCommerce integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a WooCommerce integration without building it. Your customers connect their own WooCommerce 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 WooCommerce update is not your on-call problem.
- One integration serves your product and your agents. The same governed WooCommerce 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
StripeOften used alongside
Tools the same teams tend to run next to WooCommerce, across other categories.
NetSuite
Notion
Box
DocusignWooCommerce integration FAQ
How do I add a WooCommerce integration to my product?
Enable the WooCommerce connector in your fastn dashboard, then let each customer authenticate their own WooCommerce account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no WooCommerce client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own WooCommerce account?
Yes. Every connection is scoped to the individual customer, so each authorises their own WooCommerce 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 WooCommerce 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 bought and where that order sits in the store's own status workflow.
Who maintains the WooCommerce integration?
fastn does. When WooCommerce 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 WooCommerce 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 WooCommerce integration?
A common starting point: let each customer connect their own WooCommerce store, its address included, since the API sits on their site rather than on a shared platform. 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 WooCommerce integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding WooCommerce does not change your per-connector cost. You can start free with 3 connected accounts.
Add WooCommerce to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.