ShipBob integration for ecommerce fulfilment

iWeb works with you to define a buffer-stock policy: which SKUs are fulfilment-center-only, which are warehouse-only, and which are split with a safety margin. Commerce availability rules are configured to reflect this policy. Stock movements from ShipBob are reconciled back to ERP at a defined cadence so real available-to-sell stays accurate.

iWeb configures a fallback: orders can either be routed to your main warehouse if a node is out of stock, held in a queue for manual triage, or rejected if they cannot be fulfilled within SLA. Exception alerts notify operations so the pick hold does not silently delay the shipment.

ShipBob sends dispatch confirmation with tracking number immediately after the label is generated and the carrier is handed the package. iWeb maps this back to commerce and customer email within minutes. For split orders, tracking is reconciled across shipments and shown as a consolidated list.

ShipBob emits events when inventory is received, picked, damaged or written off at each node. iWeb ingests these events and posts them to ERP as stock adjustments in the correct accounting period. Movements are logged for audit and monitored for reconciliation drift.

iWeb monitors ShipBob exception queues for label failures, carrier unavailability, and pick holds. These alerts trigger operations notifications so your team can intervene (e.g., switch to an alternative carrier, route the order elsewhere). Unshipped orders are visible in a dashboard with SLA tracking.

Commerce triggers an RMA request to ShipBob with return instructions. ShipBob receives the returned item at a node, inspects it, and reports disposition (saleable, damaged, refund only). iWeb reconciles the return back to ERP, updates inventory, and triggers refund processing.

ShipBob has default carrier selection rules by zone and weight. iWeb can help configure custom rules (e.g., preferred carrier by geography, service level). Changes to carrier strategy require out-of-band ShipBob configuration and should be monitored after launch so rules do not drift silently.

iWeb syncs ShipBob node-level stock snapshots back to commerce and ERP at a defined cadence (e.g., hourly). Real-time visibility reduces latency but increases API load. iWeb helps you balance freshness SLA against integration cost.

iWeb maps ShipBob pick-complete and pack-complete events so commerce and operations see order progression. When orders are packed but awaiting label or carrier handoff, they are visible in a queue. This allows teams to forecast dispatch and identify bottlenecks.

iWeb configures a fallback: orders can be routed to your main warehouse or held in a local queue pending ShipBob recovery. Dependency monitoring alerts operations if ShipBob API is unavailable so the team can decide whether to pause fulfilment-center routing.

iWeb logs all dispatch events with quantity, tracking and carrier. At reconciliation time, shipped orders are matched against commerce orders and ERP shipment records. Discrepancies (e.g., order split across nodes, cancelled shipments) are flagged for review.

Yes. iWeb coordinates with ShipBob to ingest initial inventory feeds, validate counts, and trigger stock-received events back to ERP. We run parallel testing to ensure commerce availability and ERP inventory stay in sync during the transition.

ShipBob inspects received inventory and flags damaged items. iWeb ingests these events and posts damage adjustments to ERP so unsaleable stock is removed from available-to-sell. Damaged items can be flagged for return to supplier or write-off.

iWeb builds dashboards for order volume, fulfillment SLA, unshipped-order age, exception queue depth, and reconciliation drift. Alerts notify operations if orders exceed dispatch SLA, if exceptions accumulate, or if stock movements diverge from ERP.