ShipBob integration

What does the ShipBob connector do in SuppliFlex?

When a brand hands fulfillment to ShipBob, the stock is physically somewhere else and its counts arrive on ShipBob's schedule, in ShipBob's format. The usual result is a second inventory system that has to be reconciled by hand against the storefront and the books.

The SuppliFlex connector removes that second system from your working day. ShipBob becomes one location among others in the SuppliFlex ledger, next to your own warehouse and Amazon FBA. You still use ShipBob to pick, pack and ship; SuppliFlex is where you see what is there, decide where orders go and account for every movement.

What syncs with ShipBob, and in which direction?

Sync is two-way and runs through the SuppliFlex modules that already handle orders and stock:

• Orders out. Orders from Shopify, Amazon or wholesale accounts sit in one order queue. Those allocated to ShipBob are sent there to be fulfilled.
• Stock in. Quantities at ShipBob are recorded against the ShipBob location in the append-only ledger, per SKU.
• Shipments and tracking. Carrier tracking events attach to the order, so customer service and finance work from the same status.
• Returns. Units coming back through ShipBob are handled as returns and RMAs, so they re-enter stock only once they are checked.

From there, the accounting effect of each movement flows to the inventory sub-ledger and on to QuickBooks Online or Xero.

How often does ShipBob data refresh?

SuppliFlex syncs in near real time, not in nightly batches, with a freshness design target of under 60 seconds at the 95th percentile. For an outsourced warehouse, that means a shipment confirmed at the 3PL changes your available stock across channels within the same working session.

What happens when ShipBob's counts disagree with the ledger?

Counts at a 3PL drift from what you expect: a receiving short, damaged units, a cycle count that comes out differently. SuppliFlex treats each of these as an exception rather than silently taking one side.

The mismatch appears in the exception inbox with the cause and a one-click fix. The conflict policy in beta is "always ask": someone on your team accepts the 3PL's count, keeps the ledger figure or records an adjustment. Because the ledger is append-only, the decision is a new, auditable entry. Cycle counts and adjustments are standard ledger actions, so the same tools work whether the stock is in your building or ShipBob's.

What can you see 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, so you can see how a 3PL location sits next to your own stock, how orders split between them and how mismatches surface. The hosted simulator emits carrier tracking events as well as channel orders. Anything not in production yet carries a "coming to production" label.

From the production beta on Fri 13 Nov 2026, the ShipBob connector is live on real accounts, along with the migration wizard and CSV import for bringing existing stock positions across.

Which plan includes ShipBob?

3PL connectors are part of the Scale tier, and ShipBob is a 3PL connector. Scale covers up to 7,500 orders and 10,000 SKUs a month, three warehouses, unlimited users, the advanced API and white-glove onboarding. As with every tier, pricing is a flat monthly fee with no usage fees, published at general availability on 23 Nov 2026. See pricing.

How do you get started with ShipBob?

Load the apparel seed pack in the sandbox to see a 3PL location working next to owned warehouses. For a broader view of how SuppliFlex treats outsourced warehouses, read 3PL integrations. To plan a move with a real ShipBob account, book a demo or apply to the pilot program.