Logistics & Supply Chain · Integration
PackageX
Add PackageX to your product for your customers, and give your AI agents governed access to it.
Embed a PackageX integration so your product can see what physically arrived, what is in stock and what shipped out without anyone typing it in. PackageX runs receiving, inventory, fulfilment and shipping on one platform, using label scanning to capture inbound items and keep counts current across locations. The records your product works with are inbound items and their scans, inventory by location, orders through pick and pack, and outbound shipments. Each customer authorises their own PackageX account, so reads and writes run under their credentials and one operation's stock and shipments never mix with another's. fastn owns the auth, retries, rate limits, webhook delivery and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own PackageX account so receiving, inventory and fulfilment records appear inside your product with no per-customer code.
Trigger your product when an inbound item is received so the next step starts immediately rather than at the end of a shift.
Read inventory by location per tenant so your product is not making decisions on a stale count.
Create and track outbound shipments from your product so fulfilment status is visible where the order lives.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers whether a shipment arrived and where it was put away, reading only that customer's account.
An agent finds inventory discrepancies across locations and lists them for someone to check, with every read audited.
An agent updates an order's fulfilment state within scoped permissions, with the write attributed.
Example prompt
Did the shipment from this supplier arrive yesterday, and how much of it has been put away?
Set up PackageX in 4 steps
- 01Enable the PackageX connector in your fastn dashboard.
- 02Have each customer authorise their own PackageX account so calls run under their credentials.
- 03Map the item, inventory, order and shipment fields your product uses, per customer, and enable triggers.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the PackageX integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PackageX integration without building it. Your customers connect their own PackageX 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 PackageX update is not your on-call problem.
- One integration serves your product and your agents. The same governed PackageX 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
AfterShip
EasyPost
FedExOften used alongside
Tools the same teams tend to run next to PackageX, across other categories.
NetSuite
Shopify
Stripe
QuickBooksPackageX integration FAQ
How do I add a PackageX integration to my product?
Enable the PackageX connector in your fastn dashboard, then let each customer authenticate their own PackageX account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PackageX client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PackageX account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PackageX 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 PackageX 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 whether a shipment arrived and where it was put away, reading only that customer's account.
Who maintains the PackageX integration?
fastn does. When PackageX 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 PackageX 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 PackageX as things move?
Whatever PackageX 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 PackageX integration?
A common starting point: let each customer connect their own PackageX account so receiving, inventory and fulfilment records appear inside your product with no per-customer code. 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 PackageX integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PackageX does not change your per-connector cost. You can start free with 3 connected accounts.
Add PackageX to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.