The Flexport connector in the app allows you to use Flexport (formerly Deliverr) as a 3PL (third-party logistics) provider for e-commerce fulfillment.
It supports:
Outbound flows: Products, Shipping Requests, Arrivals
Inbound flows: Inventory, Fulfillments, Receipts, Locations
This integration enables you to send orders to Flexport for fulfillment while keeping inventory, shipment status, and warehouse data synchronized.
Flexport primarily operates using a pull model, meaning that instead of Pipe17 pushing data to Flexport, Flexport's system periodically retrieves (pulls) data from Pipe17.
Before You Begin
Confirm you can log in to your Flexport account.
Review your order routing rules to ensure orders are directed to Flexport when intended.
Disable any previous fulfillment service or direct fulfillment in your selling channel to prevent duplicate shipments.
Ensure SKU data in the app is accurate and complete.
Also, check instruction on how to connect the Pipe17 API to Flexport and sync inventory with Flexport.
Connecting Flexport
Sign in to the app.
Go to Connections → Add Connection → Flexport (was Deliverr).
-
Choose the API version:
REST API
Logistics API
If using Logistics API, enter your Logistics API key.
-
(Optional) Enable Force webhook registration. When enabled, this option forces the app to re-register or update webhook configurations with Flexport.
This ensures Flexport sends real-time event notifications to the app when:
Inventory updates occur
Fulfillment statuses change
Other supported operational events are triggered
Enable this option if webhook-driven updates appear delayed or after reconnecting the integration.
Click Connect.
You can create the connection without credentials and complete configuration later in the Connection Details tab.
Connector Flows
Flow |
Direction |
What It Does |
Key Details |
Important Notes |
|---|---|---|---|---|
Products |
OUT |
Creates and updates products in Flexport. |
Sends SKU, name, dimensions, weights, and standard product attributes. Supports syncing all eligible products or limiting by SKU. |
|
Shipping Requests |
OUT |
Sends shipping requests to Flexport for fulfillment. |
Workflow: Shipping request created in the app → Flexport pulls the order → Fulfillment processed → Fulfillment data syncs back. Supports SKU exclusions and order ID filtering. Requires shipping method mapping in Flexport. |
|
Fulfillments |
IN |
Pulls shipment confirmations from Flexport. |
Retrieves tracking numbers, carrier details, shipped quantities, and shipping dates. |
|
Inventory |
IN |
Pulls inventory levels from Flexport into the app. |
Syncs aggregate inventory totals. Can include Reserve Storage as a separate location. |
|
Arrivals (Logistics API) |
OUT |
Sends inbound arrivals to Flexport for warehouse receiving. |
Creates shipping plans in Flexport for inbound inventory. Supports filtering by specific order IDs. |
|
Receipts (Logistics API) |
IN |
Pulls receipt confirmations from Flexport. |
Updates inbound inventory status after warehouse processing. |
|
Locations (Logistics API) |
IN |
Pulls warehouse location data from Flexport. |
Creates or updates warehouse locations in the app. |
|
Connector Settings
Products Settings
Setting |
Description |
|---|---|
Push only products with specific SKUs |
Sync only listed SKUs. Ideal for testing or partial rollout. |
Force products catalog resync |
Performs a full product catalog refresh and automatically disables after completion. |
Shipping Requests Settings
Setting |
Description |
|---|---|
Process only shipping requests for specific order IDs |
Limits processing to selected |
Push shipping requests exclude products with specific SKUs |
Excludes specified SKUs from outbound shipping requests before sending to Flexport. |
When shipping request is canceled in Flexport |
Defines which status is applied in the app when Flexport cancels a request. |
When shipping request is STOCKOUT in Flexport |
Defines which status is applied in the app when Flexport reports a stockout. |
Canceled Restock
Review Required
Canceled
Failed
Inventory Settings
Setting |
Description |
|---|---|
Pull inventory information from Flexport “Reserve Storage” |
Includes reserve storage inventory and creates a location named Reserve with ID |
Process only inventory items with specific SKUs |
Restricts inventory sync to listed SKUs. |
Force inventory resync |
Triggers a full inventory refresh to correct discrepancies. |
Arrivals Settings
Setting |
Description |
|---|---|
Process only arrivals for specific order IDs |
Restricts arrival processing to selected order IDs. |
Force arrivals resync |
Reprocesses all eligible arrivals. Useful when inbound shipping plans fail to create. |
Connector Notes
Pull Model Behavior
The Flexport connector operates differently from most connectors in the app because it uses a pull model.
Although products and shipping requests appear to be sent from the app to Flexport, Flexport periodically retrieves this data from the app.
Products are pulled every 4 hours.
Orders (shipping requests) are pulled every 15–30 minutes.
By default, Flexport pulls all published simple and child products from the app.
However, you can limit which products sync by using the Push only products with specific SKUs setting in the Flexport integration configuration.
If you only want a subset of SKUs to sync, you can:
Configure the SKU filter in the Flexport integration settings, or
Avoid creating unnecessary products in the app and use a product CSV upload to create only the SKUs you want managed by Flexport.
This ensures only the intended products are recognized and processed.
Shipping Method Mapping
Shipping method mappings must be configured in Flexport using their Shipping Method Mapping functionality.
If shipping methods are not properly mapped, orders may fail to process or route correctly.
Inventory Behavior
Flexport’s portal displays inventory by fulfillment center or warehouse location.
However, Flexport only sends aggregate inventory totals to the integration.
As a result, the app displays total inventory and does not show a per-location breakdown.
Flexport Fast Tags
Flexport Fast Tags require additional configuration beyond the standard connector setup.
Required Order Data
To support Fast Tags:
The source order channel name (for example, Shopify) must be passed to Flexport.
The source order ID must be passed to Flexport.
If orders originate from another system (such as NetSuite), ensure the original source channel name exists on the order and is mapped to orderSource in the app.
Required Connections in Flexport
Two connections must be configured in Flexport:
The standard Pipe17 connection for Orders, Fulfillments, and Inventory.
A separate Flexport Fast Tag connection to the original order source channel.
The Fast Tag connection is configured with assistance from Flexport Support.
Routing Fast-Tagged Orders
If you use multiple fulfillment providers, ensure all Fast-Tagged orders route to Flexport.
There are two recommended approaches:
Route all fulfillable orders to Flexport.
This guarantees Fast-Tagged orders are not routed to another provider.
Or, route based on shipping method.
Flexport assigns specific shipping method names to Fast-Tagged orders. You can configure Order Routing rules to check for these values and route those orders to Flexport.
Eligible Fast Tag shipping methods:
Free NextDay Delivery
Free 2-Day Delivery
Free 3-Day Delivery
NextDay Delivery
2-Day Delivery
3-Day Delivery
If routing based on shipping method, place this routing rule first in your routing configuration so it is evaluated before other rules.
Troubleshooting
Orders are not being fulfilled
Confirm shipments.out is enabled.
Verify order routing directs orders to Flexport.
Confirm SKUs exist in both systems and have available inventory.
Review shipping method mappings in Flexport.
Inventory levels look incorrect
Confirm inventory.in is enabled.
Check SKU filters under Inventory settings.
Use Force inventory resync to refresh quantities.
Remember inventory is displayed as aggregate totals only.
Fulfillments are not syncing
Confirm fulfillments.in is enabled.
Enable Force webhook registration and reconnect if needed.
Review the Events page for mapping or status errors.
Arrivals or receipts are not processing
Confirm Logistics API is selected and the API key is valid.
Verify arrivals.out and receipts.in are enabled.
Check order ID filters that may restrict processing.
Need Help?
If you need additional assistance:
Use Ask Pippen, our AI agent, located at the top of the app page.
Submit a support request with as much relevant detail as possible. Learn how to submit a request.
For urgent issues, email us directly at support@pipe17.com.
We're here to help you succeed with your operations.
Comments
0 comments