Five bidirectional data flows. Orders in, purchase orders as ASNs, receipts out, stock updates out, shipments out. Supply Lens connects ShipBob to your ERP, storefronts, and finance systems — with fulfilment centre routing, SKU mapping, bundle handling, and courier configuration all handled correctly.
ShipBob operates as a distributed fulfilment network — inventory spread across multiple fulfilment centres, orders routed automatically by ShipBob to the location closest to the buyer. Each of these five flows has its own logic within that network model.
Orders flow from your ERP or storefront into ShipBob as fulfilment instructions, and ShipBob order status events flow back to keep source systems current. Whether the order originates from Shopify, Unleashed, WooCommerce, or a marketplace, Supply Lens transforms it into the format ShipBob expects — with the correct channel identification, SKU resolution, and any required shipping method preference applied before transmission.
ShipBob's fulfilment network then routes each order to the most appropriate fulfilment centre based on inventory availability and delivery destination. Supply Lens does not interfere with ShipBob's internal routing logic — it ensures each order arrives in ShipBob in a state where that routing can fire correctly.
When a purchase order is raised in your ERP for inbound stock to ShipBob, Supply Lens transforms it into a Warehouse Receiving Order — ShipBob's equivalent of an ASN — and sends it ahead of the goods arriving. ShipBob can then prepare for the inbound and process the receipt against the expected quantities when the stock lands at the fulfilment centre. You can specify which ShipBob fulfilment centre the WRO is destined for, and Supply Lens carries that instruction through from the ERP PO.
When ShipBob processes a WRO — confirming that inbound stock has been received and checked into the fulfilment centre — Supply Lens captures the processing event and creates the corresponding receipt in your ERP. Stock levels update immediately, purchase orders are marked fulfilled to the received quantity, and any discrepancies between expected and received units are recorded against the original PO. Because ShipBob can receive stock across multiple fulfilment centres, Supply Lens maps each receipt back to the correct ERP warehouse or location.
ShipBob holds your physical inventory and reports available quantities across each fulfilment centre. Supply Lens takes those inventory position updates and pushes consolidated available-to-sell quantities to your ERP, Shopify, and any other connected channel. Where you need per-FC visibility in your ERP — for example, to understand regional stock allocation — Supply Lens can map each FC's quantity to a separate ERP warehouse record. Where you just need a single available figure for channel stock, Supply Lens aggregates across FCs and pushes the combined total.
When ShipBob ships an order — from whichever fulfilment centre fulfilled it — Supply Lens captures the shipment event and pushes it to all connected downstream systems. The ERP sales order is marked dispatched. The Shopify fulfilment is created with the carrier name and tracking number. The customer notification fires. The carrier ShipBob uses for a given shipment depends on which FC fulfilled it and ShipBob's own rate selection — Supply Lens maps whatever carrier and service ShipBob returns to the correct label in each downstream system, regardless of which FC the order shipped from.
ShipBob's distributed fulfilment model introduces configuration questions that a single-warehouse WMS does not. Which fulfilment centre does inbound stock go to? How does per-FC inventory map back to your ERP? What carrier does ShipBob use from each location, and what does your downstream system expect to see? Supply Lens handles all of it.
The most common ShipBob integration pairings. Each uses the same five-flow architecture with configuration tailored to the specific systems and fulfilment centre setup involved.
ShipBob's fulfilment network model — multiple FCs, carrier selection handled by ShipBob, stock split across locations — introduces integration edge cases that a single-warehouse WMS connection does not have to deal with.
Supply Lens maps each ShipBob fulfilment centre to a separate ERP warehouse record, or aggregates across FCs into a single available-to-sell figure — whichever your ERP setup requires. When stock moves between FCs, or when a WRO is processed at a specific location, the correct ERP warehouse updates. Your stock position in the ERP reflects what ShipBob actually holds and where it sits.
ShipBob selects the carrier based on its own rate shopping and FC location — you don't always control which carrier fulfils a given shipment. Supply Lens maps whatever carrier code ShipBob returns to the correct label in your ERP and Shopify. The carrier field lands correctly in every downstream system and tracking URLs resolve as expected, regardless of whether ShipBob used USPS, UPS, Royal Mail, or any other carrier for that shipment.
The WRO receipt flow closes this gap. When ShipBob processes a WRO — confirming that your inbound stock has been received and checked into the FC — Supply Lens creates the GRN in your ERP and updates stock immediately. The purchase order is marked fulfilled to the received quantity and the ERP stock position reflects the actual ShipBob inventory without anyone logging into the portal to check.
Bundle explosion happens at the integration layer before the order reaches ShipBob. The bundle SKU is detected, expanded into its components with the correct quantities, and ShipBob receives individual pick lines for each item. The Shopify fulfilment is created against the original bundle SKU. Stock updates return at component level so your ERP position remains accurate across every fulfilment.
Most ShipBob integration projects follow a structured path. The key setup work is mapping your fulfilment centres, SKUs, and channel rules correctly so the five flows work accurately across ShipBob's distributed network.
Ongoing support includes carrier mapping updates, SKU maintenance, and FC routing changes as your ShipBob network evolves.
Five flows across ShipBob's fulfilment network — fully configured. Orders, WROs, receipts, stock, and shipments automated. 30-day trial available.