Connecting Flexport (was Deliverr) to Pipe17

With this connector, you can:

• Make your product catalog available to Flexport.
• Send shipping requests to Flexport for fulfillment.
• Pull fulfillments with tracking numbers, carriers, and shipped quantities from Flexport.
• Pull aggregate inventory from Flexport, including Reserve Storage if you choose.
• Send inbound arrivals to Flexport and pull receipts back into the app.
• Pull your Flexport warehouse locations into the app.

Setup

Before you begin

Make sure you have:

• A Flexport account that you can sign in to.
• If you plan to use the Logistics API, the Administrator role in your Flexport organization, so you can create an API token.
• Order routing rules that send orders to Flexport when intended.
• Any previous fulfillment service or direct fulfillment in your selling channel turned off, to prevent duplicate shipments.
• Accurate and complete SKU data in the app.

Also see how to connect the Pipe17 API to Flexport and sync inventory with Flexport.

Prepare Flexport

The app connects to Flexport in one of two ways. You choose it in Use Deliver API:

• REST API (default): you sign in to Flexport during setup to authorize the app. You don’t need a key.
• Logistics API: you paste a Flexport Logistics API token. Use it if you plan to send arrivals or pull receipts.

To create a Logistics API token:

1. Sign in to the Flexport portal as an Administrator.
2. Go to Settings > API Tokens, and then click Create Token.
3. Select the permission scopes. Give read and write access to Products, Bundles, Inbounds, Orders, and Webhooks.
4. Copy the token and store it somewhere safe until you paste it in the app.

To learn more, see Flexport’s Logistics API Getting Started guide.

Note: Flexport merchant tokens expire one year after you create them. Before the token expires, create a new one and enter it on the integration’s Connection Details tab.

For either API, map your shipping methods in the Flexport portal under Settings > Shipping Option Mapping. If shipping methods aren’t mapped, orders may fail to process.

Connect in the app

1. Navigate to Integrations in the app.
2. Click Add Integration, and then select Flexport (formerly Deliverr). The connection pop-up opens.

3. In Use Deliver API, select REST API (default) or Logistics API.
4. If you use the Logistics API, paste your token in Use Flexport (formerly Deliverr) Logistics API key. Leave it empty for the REST API.
5. Optional: Turn on Force webhook registration to make the app register or update its webhooks with Flexport. If Flexport already has webhooks from an earlier connection, for example after you reconnect or replace the integration, the app replaces them with its own. Use it if inventory or fulfillment updates seem delayed.
6. Click Connect.
   • With the REST API, you’re redirected to the Flexport sign-in page. Sign in with your Flexport credentials to authorize the app. Finish within 15 minutes, or the authorization times out.
   • With the Logistics API, the app connects with your token. You don’t sign in to Flexport.
7. In the integration settings, toggle on the flows you want to use: Pull locations from Flexport (formerly Deliverr), Push product catalog information to Flexport (formerly Deliverr), Push shipping requests to Flexport (formerly Deliverr), Pull fulfillments from Flexport (formerly Deliverr), Pull inventory information from Flexport (formerly Deliverr), Push arrivals to Flexport (formerly Deliverr), and Pull receipts from Flexport (formerly Deliverr). Turn on shipping requests only when you’re ready to process live orders.

Note: Add without credentials adds the integration without connecting it. It doesn’t sync until you enter the connection details on the Connection Details tab and click Connect.

Contact Pipe17 support before you change Use Deliver API on an integration that has orders or arrivals in progress.

Confirm the connection

1. On Integrations, check that Flexport (formerly Deliverr) shows Connected and that the integration switch is on. If it shows Not Configured, the Flexport sign-in didn’t finish. Open the integration and click Connect on the Connection Details tab. If it shows Error with “Authorization timed out”, connect again and finish the sign-in within 15 minutes. With the Logistics API, check that the token is active and has the scopes listed above.
2. With Pull locations from Flexport (formerly Deliverr) on, wait about 5 minutes, and then check that your Flexport warehouses appear on the Locations page.
3. With Push product catalog information to Flexport (formerly Deliverr) on, wait about 5 minutes, and then check that one of your SKUs appears in the Flexport portal.
4. With Pull inventory information from Flexport (formerly Deliverr) on, check that SKU on the Inventory page in the app. Flexport sends aggregate totals only.
5. When you’re ready for live orders, turn on Push shipping requests to Flexport (formerly Deliverr). The app sends every Ready for Fulfillment shipping request routed to Flexport, so test with an order you plan to ship. Within about 5 minutes, check that its shipping request moves to Sent to Fulfillment.
6. After Flexport ships the order, check that the fulfillment with the tracking number appears on the order. If it doesn’t, run Pull fulfillments from Flexport (formerly Deliverr) by order ID on the Integration Actions tab.

Settings

Flows

The app sends product updates and shipping requests to Flexport every 5 minutes. By default, the app sends all published simple and child products. To limit products, use Push only products with specific SKUs, or create only the SKUs you want Flexport to manage, for example with a product CSV upload.

Integration actions

Flexport Fast Tags

Flexport Fast Tags need more setup than the standard connection:

• The source order channel name, for example Shopify, and the source order ID must be passed to Flexport. If orders come from another system, such as NetSuite, make sure the original source channel name is on the order and mapped to orderSource in the app.
• You need two connections in Flexport: the standard Pipe17 connection for orders, fulfillments, and inventory, and a separate Fast Tag connection to the original order source channel. Flexport Support helps you set up the Fast Tag connection.
• If you use more than one fulfillment provider, make sure all Fast Tag orders route to Flexport. Either route all fulfillable orders to Flexport, or route by shipping method. Flexport uses these shipping method names for Fast Tag orders: Free NextDay Delivery, Free 2-Day Delivery, Free 3-Day Delivery, NextDay Delivery, 2-Day Delivery, and 3-Day Delivery. If you route by shipping method, put that rule first in your routing configuration.

Troubleshooting

• The integration shows Error with “Authorization timed out”
  The Flexport sign-in for the REST API wasn’t finished within 15 minutes. Click Connect on the Connection Details tab and finish the sign-in.
• The integration stops syncing with the Logistics API
  The Logistics API token expired after one year, was revoked, or is missing a scope. Create a new token in the Flexport portal under Settings > API Tokens, enter it in Use Flexport (formerly Deliverr) Logistics API key, and then click Connect.
• Orders aren’t being fulfilled
  Check that Push shipping requests to Flexport (formerly Deliverr) is on, that order routing sends the orders to Flexport, and that the SKUs exist in both systems with available inventory. Also review the shipping method mappings in Flexport.
• Inventory levels look wrong
  Check that Pull inventory information from Flexport (formerly Deliverr) is on and review Process only inventory items with specific SKUs. Turn on Force inventory resync to refresh quantities. Flexport sends aggregate totals only.
• Fulfillments aren’t syncing
  Check that Pull fulfillments from Flexport (formerly Deliverr) is on. Turn on Force webhook registration and reconnect if needed, and review the Events page for mapping or status errors.
• Arrivals or receipts aren’t processing
  Check that Use Deliver API is set to Logistics API with a valid key, that the arrivals and receipts flows are on, and that Process only arrivals for specific order IDs isn’t limiting them.

Need Help?

If you need additional assistance:

• Use Ask Pippen, our AI agent, located at the top of the platform page.
• Submit a support request with as much relevant detail as possible. Learn how to submit a request.

We’re here to help you succeed with your operations.