Flexport connector for Claude

Yes. Flexport's Logistics API replaced the Deliverr API, and Porter reads through the Logistics API, so a Seller Portal account that began on Deliverr works. When you migrate, create a new Logistics API token, as Flexport asks.

Claude gets Order Cost, what Flexport charged to fulfill each order, and sums it by Marketplace or Order Date, so you see fulfillment cost per channel and per day. For storage, inbound, return and other fees, use the Seller Portal's billing reports.

Each question to the Flexport connector for Claude triggers a fresh Logistics API read, so answers show what Flexport has recorded at that moment. Paid Porter plans set no history cut-off, while the free plan reads 15 days in AI chats (30 days of history). Flexport doesn't publish how far back its API returns tracking events.

Porter gives Claude reports on the fulfillment data you already have. To create orders or webhooks from code, work from Flexport's Logistics API docs, and keep Porter for the reporting side. Porter's MCP servers also list what else Claude can read.

Claude's Flexport counts through Porter can be different from the Seller Portal's for 3 usual reasons. Split orders: one marketplace order can become several Flexport orders sharing one Marketplace Order Reference. Portal reports use the time zone you pick, and carriers time a scan before Flexport records it.

Create a token that includes the read scope for that data, then paste it in Porter. A 403 error means Porter's token lacks that scope. A 401 means the token expired (after one year by default) or an admin revoked it, so create a new one.

Check your Flexport account access first. Orders and inbounds need a Flexport billing account, while parcels and returns need account approval from Flexport support. A sandbox account holds no parcels or returns, so test those on a live account.