Commerce & Payments · Integration
Brightpearl
Add Brightpearl to your product for your customers, and give your AI agents governed access to it.
Brightpearl is the back office behind a retailer's storefronts, and its model reflects that. A sales order records what was agreed, but fulfilment lives on a separate goods-out note, so dispatch status is not a field on the order and any progress view has to read both. Warehouses, contacts, products, custom fields and the accounting journals behind invoices and credits complete the picture. Access is per account too: a customer gives you an account code and a token, and the base URL carries the datacenter their account sits in, so hard-coding one region breaks every customer outside it. Remaining request headroom comes back on each response. fastn keeps account credentials, regions and API changes on its side.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a retailer connect their own account so your product reads sales orders and the goods-out notes that fulfil them.
Show real dispatch progress by pairing an order with its goods-out notes instead of trusting one status field.
Read warehouse and stock detail per tenant so allocation in your product matches what the back office believes.
Write contacts, orders and custom field values back so the retailer's ledger and your product agree.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent explains where an order is by reading its goods-out notes and the warehouse they shipped from.
An agent creates or amends a sales order within scoped permissions, idempotently and with the call logged.
An agent reports which credits were raised this period for one retailer's account.
Example prompt
Which sales orders have no goods-out note yet, and how long have they been sitting there?
Set up Brightpearl in 4 steps
- 01Enable the Brightpearl connector from your fastn dashboard.
- 02Have each customer authorise their own Brightpearl 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 Brightpearl integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Brightpearl integration without building it. Your customers connect their own Brightpearl 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 Brightpearl update is not your on-call problem.
- One integration serves your product and your agents. The same governed Brightpearl 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
ShopifyWorks well with
Cin7
ExtensivOften used alongside
Tools the same teams tend to run next to Brightpearl, across other categories.
NetSuite
Notion
Box
DocusignBrightpearl integration FAQ
How do I add a Brightpearl integration to my product?
Enable the Brightpearl connector in your fastn dashboard, then let each customer authenticate their own Brightpearl account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Brightpearl client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Brightpearl account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Brightpearl 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 Brightpearl 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 explains where an order is by reading its goods-out notes and the warehouse they shipped from.
Who maintains the Brightpearl integration?
fastn does. When Brightpearl 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 Brightpearl 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 Brightpearl integration?
A common starting point: let a retailer connect their own account so your product reads sales orders and the goods-out notes that fulfil them. 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 Brightpearl integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Brightpearl does not change your per-connector cost. You can start free with 3 connected accounts.
Add Brightpearl to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.