Logistics & Supply Chain · Integration
Descartes
Add Descartes to your product for your customers, and give your AI agents governed access to it.
Embed a Descartes integration so your customers can work their own shipments, tracking events, carriers, and delivery status from inside your product, with governed agent access to the same records. Logistics data arrives from many parties in inconsistent formats and at unpredictable times, so events are normalised, deduplicated, and delivered per tenant. fastn handles each customer's credentials and API upkeep, so onboarding a new logistics account is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own shipments and tracking events into your product instead of checking a portal.
Surface delivery status and exceptions against the order or job they belong to in your app.
Submit shipment and transportation requests from your product using each customer's own account.
Trigger your product when a shipment status changes or a delivery exception is raised.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up a shipment's latest tracking events before answering a where-is-my-order question.
An agent submits or updates a shipment request within governed permissions, with the action audited.
An agent reacts to a delivery exception and starts the customer's recovery workflow.
Example prompt
List shipments due yesterday that have not been marked delivered and show the last tracking event for each.
Set up Descartes in 4 steps
- 01Open the Descartes connector from your fastn dashboard.
- 02Have each customer authenticate their Descartes account with least-privilege credentials.
- 03Map the shipment and tracking fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Descartes integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Descartes integration without building it. Your customers connect their own Descartes 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 Descartes update is not your on-call problem.
- One integration serves your product and your agents. The same governed Descartes 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
EasyPostWorks well with
NetSuite
SAPOften used alongside
Tools the same teams tend to run next to Descartes, across other categories.
Shopify
Stripe
QuickBooks
BigCommerceDescartes integration FAQ
How do I add a Descartes integration to my product?
Enable the Descartes connector in your fastn dashboard, then let each customer authenticate their own Descartes account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Descartes client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Descartes account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Descartes 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 Descartes 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 a shipment's latest tracking events before answering a where-is-my-order question.
Who maintains the Descartes integration?
fastn does. When Descartes 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 Descartes 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 Descartes as things move?
Whatever Descartes 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 Descartes integration?
A common starting point: read their own shipments and tracking events into your product instead of checking a portal. 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 Descartes integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Descartes does not change your per-connector cost. You can start free with 3 connected accounts.
Add Descartes to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.