Do you see an order in Walmart, Shopify, or another integration but it's not showing up in Flexport? There are several common reasons this happens — all related to how your account or integration is configured. Work through each section below to find and fix the issue.
1. Order hasn't imported yet
Some integrations hold orders for up to 30 minutes after creation to allow the buyer to cancel. Orders still in "payment processing" are also not imported until payment clears.
What to do: Wait 30 minutes and check Flexport Portal → Orders again. Make sure you're searching by the correct order ID, or try searching by product name or buyer name instead.
2. Listing not linked to the correct Flexport SKU
When Flexport sees an incoming order, we look for a link between the marketplace SKU and a Flexport DSKU. If there's no link — or if the listing is linked to the wrong DSKU (e.g. one with 0 inventory) — the order won't import. This commonly happens when connecting multiple integrations, since the SKU value may differ across marketplaces, causing Flexport to create a duplicate DSKU instead of linking to an existing one.
What to do: Go to Flexport Portal → Inventory and find the DSKU with available inventory. Click it to open the details page and check whether there's an alias for the integration you're having trouble with. Click (+) to add a new link and search by product name, SKU value, or product ID. Once the alias is fixed, the order will automatically import. See Checking & Fixing SKU Mismatches for a full walkthrough.
3. Order not assigned to Flexport
Some integrations route orders to specific nodes, locations, or warehouse entities. Flexport only imports orders assigned to our node — if your integration isn't configured correctly, orders may go to a different fulfillment method.
What to do:
- Walmart — Check if the order is on the Seller Fulfilled Node. Flexport can only fulfill orders on the Partner Fulfilled Orders (Flexport) node. Read about Walmart multinode setup. A common fix is to zero out inventory on the seller fulfilled node.
- Shopify — Most sellers use the default auto-fulfill configuration. If using multiple locations, verify your location priority setup.
- Other integrations — Find your integration in the help center and confirm setup is correct.
4. Another app is acknowledging orders first
Third-party apps or plugins connected to your marketplace account may be marking orders as "acknowledged" or "fulfilled" before Flexport can import them. Flexport won't import already-acknowledged orders to avoid double-shipping.
What to do: Check for other apps connected to your marketplace — especially any that fulfill or acknowledge orders. If you're only using Flexport, disconnect those apps. If you need both, read their documentation to configure them to work together. For ShipStation: exclude certain SKUs from importing into ShipStation so Flexport handles those orders instead.
5. Flexport can't connect to your integration
Flexport can't import orders if we can't connect with your integration credentials. Credentials can expire naturally, break due to a bug, or stop working if your subscription on the integration has lapsed.
What to do: Go to Flexport Portal → Channels, find the integration you're having trouble with, and click Update Credentials. Go through the setup flow again — any available unfulfilled orders should import automatically once reconnected. You don't need to disconnect unless you want to stop using the integration entirely.
Still not showing up?
Contact support and include the order IDs from your integration. Learn how to find the right order ID. The more detail you provide upfront, the faster we can resolve it.