Logistics & Supply Chain · Integration
Shippo
Add Shippo to your product for your customers, and give your AI agents governed access to it.
Shippo is a layer over many carriers, so the object worth understanding is the rate: one shipment produces many rates, and choosing between them is the actual decision a product helps with. Buying a label is the commitment step and it is not free to get wrong, since a purchased label is a real cost even when unused. Tracking arrives as carrier events with wildly different vocabularies underneath, which Shippo normalises, and that normalisation is much of the reason to use it. Customers can bring their own carrier accounts and negotiated rates, so the same shipment costs different amounts per tenant. fastn scopes each customer's token so their carrier accounts and rates stay theirs.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Shippo account so shipping runs on their carrier accounts and negotiated rates.
Compare rates across carriers for a shipment rather than defaulting to one.
Buy a label from your product once a rate is chosen.
React to normalised tracking events instead of parsing each carrier's own vocabulary.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent compares rates and recommends one against a cost and speed constraint.
An agent buys a label within governed permissions, with the purchase audited per tenant.
An agent reports which shipments are delayed and where they last scanned.
Example prompt
What are the cheapest and fastest rates for this shipment, and which shipments are delayed?
Set up Shippo in 4 steps
- 01Enable the Shippo connector from your fastn dashboard.
- 02Have each customer authorise their own Shippo 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 Shippo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Shippo integration without building it. Your customers connect their own Shippo 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 Shippo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Shippo 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
FedEx
OnfleetWorks well with
ShopifyOften used alongside
Tools the same teams tend to run next to Shippo, across other categories.
NetSuite
Stripe
QuickBooks
BigCommerceShippo integration FAQ
How do I add a Shippo integration to my product?
Enable the Shippo connector in your fastn dashboard, then let each customer authenticate their own Shippo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Shippo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Shippo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Shippo 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 Shippo 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 compares rates and recommends one against a cost and speed constraint.
Who maintains the Shippo integration?
fastn does. When Shippo 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 Shippo 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 Shippo as things move?
Whatever Shippo 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 Shippo integration?
A common starting point: let a customer connect their own Shippo account so shipping runs on their carrier accounts and negotiated rates. 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 Shippo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Shippo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Shippo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.