3PL integrations

Why is 3PL stock hard to keep accurate?

A growing brand rarely keeps all its stock in one building. A common setup is a home warehouse for wholesale and returns, one or more third-party logistics (3PL) warehouses for DTC orders, and Amazon FBA for marketplace sales. Each location reports in its own portal, on its own timing.

The question "how many units do we have" then has three or four answers, and someone stitches them together in a spreadsheet. Reorder decisions, oversell risk and the inventory value in the books all depend on that spreadsheet being right.

How does SuppliFlex hold stock across 3PLs, FBA and your own warehouses?

SuppliFlex keeps a single append-only ledger per SKU and location. A 3PL warehouse is a location in that ledger, exactly like your own warehouse or Amazon FBA. Every receipt, shipment, transfer, adjustment and cycle count is a ledger entry, so stock at a given location is the sum of what has happened there, and the history is never overwritten.

That structure gives you:

• One number per SKU, broken down by location. Owned, outsourced and FBA stock side by side.
• Transfers you can follow. Moving a pallet from your warehouse to a 3PL is a transfer between two locations, not a write-off in one system and a receipt in another.
• Detail that survives the handoff. Lots, batches and serials stay attached to units wherever they sit, and bundles and kits are built from component stock.
• Valuation in one place. Weighted average or FIFO across all locations, feeding the inventory sub-ledger that syncs to QuickBooks Online or Xero.

What does a 3PL connector sync?

A 3PL connector keeps the 3PL location current without manual uploads. Sync is two-way and near-real-time, with a freshness design target of under 60 seconds at the 95th percentile. In terms of the SuppliFlex modules, a 3PL connection touches:

• the order queue, for orders allocated to the 3PL;
• available quantities at the 3PL location;
• carrier tracking events for shipments it sends;
• returns and RMAs for units sent back through it.

ShipBob is the named 3PL connector, and its page covers the details.

What happens when a 3PL count does not match?

It will happen. A 3PL receives fewer units than the advance notice said, a cycle count finds damage, or a sync fails. Each discrepancy goes to the exception inbox with its cause and a one-click fix. The beta conflict policy is "always ask", so your team decides whether to accept the 3PL figure or record an adjustment. Recurring patterns can be routed to a task queue and documented in the knowledge base.

The inbox also flags risks that span locations: oversell risk when channel demand spikes, and a projected stockout date when a supplier keeps missing delivery windows.

What can you try in the sandbox, and what is live from 13 November?

The public sandbox opens Fri 30 Oct 2026 at 12:00 CT. The apparel DTC and wholesale seed pack includes two warehouses and a 3PL with 18 months of history, B2B price lists and open purchase orders. It is the quickest way to see own and outsourced stock in one ledger, run a transfer and watch an exception appear. Connectors are simulated in the sandbox; anything not yet in production is flagged "coming to production".

From the production beta on Fri 13 Nov 2026, the ShipBob connector is live, along with CSV import and the migration wizard. If your 3PL is not ShipBob, CSV import is the route at beta; the custom connector framework, Python SDK and GraphQL follow after API v1. We do not have a date for further named 3PL connectors.

Which plan includes 3PL connectors?

Scale. It covers up to 7,500 orders and 10,000 SKUs a month, three warehouses, unlimited users, 3PL connectors, the advanced API and white-glove onboarding. Prices are published at general availability on 23 Nov 2026; see pricing.

How do you get started?

Open a sandbox with the apparel seed pack. If you are running stock across your own warehouse, a 3PL and FBA today, book a demo to map your locations, or apply to the pilot program, which accepts brands with one to twenty stock locations.