Logistics & Supply Chain · Integration
Cin7
Add Cin7 to your product for your customers, and give your AI agents governed access to it.
Cin7 runs inventory and order management for businesses that hold physical stock, so what your product reads is stock on hand per location, purchase orders and their receipts, sales orders, product families with their variants, suppliers and price tiers. Two things make it awkward. Quantity is never a single number, because the same product has different availability in every warehouse and bin, so anything you display has to say where it is. And the brand covers more than one platform, Cin7 Core and Cin7 Omni, which authenticate differently and do not expose an identical model, so a customer's plan changes what you can call. fastn puts that behind one connector and carries the credentials and upkeep per account.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Cin7 account so your product reads their stock on hand without a nightly export.
Show availability by warehouse and bin rather than one total, because that is the number a picker acts on.
Raise or update a purchase order from your product so replenishment follows what your app actually forecast.
Serve customers on either Cin7 platform from one connector, with the authentication difference handled for you.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers which locations hold enough of a product to cover an order, reading one account only.
An agent creates a stock adjustment or a transfer within scoped permissions, and the location is recorded.
An agent reports which purchase orders are overdue against their expected receipt date.
Example prompt
Which products are below their reorder point at this warehouse, and is a purchase order already open for them?
Set up Cin7 in 4 steps
- 01Enable the Cin7 connector from your fastn dashboard.
- 02Have each customer authorise their own Cin7 account, so calls run under their credentials rather than a shared key.
- 03Decide which shipments, tracking events and orders 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 Cin7 integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cin7 integration without building it. Your customers connect their own Cin7 account inside your product and work their shipments, tracking events and orders there, with no per-customer code on your side.
- Handle the part that actually costs time: tracking data arrives from many carriers in inconsistent formats and at unpredictable times. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Cin7 update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cin7 connection powers in-product features and gives AI agents scoped, audited access, so you keep physical movement and stock visible inside your product without wiring it twice.
Used by these teams
Compare with
Extensiv
SellbriteWorks well with
BrightpearlOften used alongside
Tools the same teams tend to run next to Cin7, across other categories.
NetSuite
Shopify
Stripe
QuickBooksCin7 integration FAQ
How do I add a Cin7 integration to my product?
Enable the Cin7 connector in your fastn dashboard, then let each customer authenticate their own Cin7 account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cin7 client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cin7 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cin7 account and only ever sees their own shipments, tracking events and orders. 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 Cin7 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 which locations hold enough of a product to cover an order, reading one account only.
Who maintains the Cin7 integration?
fastn does. When Cin7 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.
Can I track shipments from Cin7 inside my product?
Yes. Shipment and tracking events are read per customer and can trigger your workflows, so status changes surface in your product instead of your users checking a carrier site.
What does my product get back from Cin7 as things move?
Whatever Cin7 actually holds. Where it moves goods, that is shipment and tracking events, read per customer and delivered as they land. Where it holds stock, levels can be read on demand or kept in step through events, so your product is not deciding on a stale count. Where it carries orders and documents between trading partners, it is the acknowledgement, ship notice or status change that says what moved.
What can I build with the Cin7 integration?
A common starting point: let a customer connect their own Cin7 account so your product reads their stock on hand without a nightly export. 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 Cin7 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cin7 does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cin7 to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.