Logistics & Supply Chain · Integration
Direct Supply
Add Direct Supply to your product for your customers, and give your AI agents governed access to it.
Embed a Direct Supply integration so your customers can work their own procurement records from inside your product, reading catalog items, submitting purchase orders, and following order status through their own account. Writes are idempotent, so a retry after a timeout does not raise the same order twice, and every call is logged per tenant so an order can be traced back to the event that created it. fastn handles each customer's credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own contracted catalog and pricing into your product for ordering.
Raise purchase orders from your product so buyers do not switch to a separate portal.
Read order and delivery status so your product shows where an order actually is.
Trigger your product when an order is acknowledged, shipped, or changed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up an order's current status before answering a facility manager's question.
An agent raises or updates a purchase order within governed permissions, with the action audited.
An agent reacts to a delivery or backorder update and runs the next step of a workflow.
Example prompt
Show purchase orders raised this month that are not yet delivered and flag any with a changed expected date.
Set up Direct Supply in 4 steps
- 01Open the Direct Supply connector from your fastn dashboard.
- 02Have each customer authenticate their Direct Supply account with least-privilege credentials.
- 03Map the catalog and purchase order 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 Direct Supply integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Direct Supply integration without building it. Your customers connect their own Direct Supply 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 Direct Supply update is not your on-call problem.
- One integration serves your product and your agents. The same governed Direct Supply 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
DescartesWorks well with
NetSuite
SAPOften used alongside
Tools the same teams tend to run next to Direct Supply, across other categories.
Shopify
Stripe
QuickBooks
BigCommerceDirect Supply integration FAQ
How do I add a Direct Supply integration to my product?
Enable the Direct Supply connector in your fastn dashboard, then let each customer authenticate their own Direct Supply account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Direct Supply client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Direct Supply account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Direct Supply 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 Direct Supply 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 an order's current status before answering a facility manager's question.
Who maintains the Direct Supply integration?
fastn does. When Direct Supply 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 Direct Supply 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 Direct Supply as things move?
Whatever Direct Supply 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 Direct Supply integration?
A common starting point: read their own contracted catalog and pricing into your product for ordering. 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 Direct Supply integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Direct Supply does not change your per-connector cost. You can start free with 3 connected accounts.
Add Direct Supply to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.