Shipping and fulfillment
Bring ShipBob on-hand and inbound inventory, fulfilled orders, and tracking into Unison. Use AI to answer fulfillment questions with the right stock context, keeping inbound units separate until ShipBob confirms receipt.
ShipBob is a third-party fulfillment provider. Unison can bring together the inventory and order context available through ShipBob with related channel activity, helping teams understand what is on hand, inbound, and being fulfilled.
Connect available on-hand and inbound inventory, orders ShipBob is fulfilling, and shipment tracking. Keep inbound inventory distinct from the confirmed available count for channels ShipBob serves.
What is pickable today is available as the current ShipBob count. Review warehouse availability alongside channel inventory so the team can coordinate using current fulfillment context.
Inbound inventory remains incoming until ShipBob confirms receipt. Teams can see what is expected without treating a shipment in transit as sellable stock.
Orders ShipBob is fulfilling can be reviewed with the channel that received them. Questions about last week can include what shipped, not only what the storefront captured.
Tracking can be associated with the order so the channel that sold it can see the shipment status alongside its fulfillment details.
When supported and in scope, an approved channel stock update can use ShipBob’s confirmed inventory. Inbound receipts remain ShipBob’s to confirm; they are not treated as on-hand. Portal-only receiving and exception work stays with a person.
A stock figure drawn from ShipBob's confirmed count can go out to the channels ShipBob serves, after you approve it. Receiving stays with ShipBob. Unison does not mark inbound as on-hand.
Use the API or MCP permissions available for ShipBob inventory, orders, and tracking. The connection is limited to granted objects and actions, with proposed writes held for a person when required.
If a receiving or exception step only lives in the ShipBob portal, it stays with the person who can see that login. The count that the API already exposes can still feed the channels.
Amazon FBA is a different building and a different receipt. Automations that push stock from ShipBob leave FBA as its own bin. The call is where we mark that split.
Ask AI what is available versus still inbound, which orders ShipBob is fulfilling, and where tracking is available. Prepare an in-scope channel stock update from confirmed counts for approval, while keeping Amazon FBA stock separate.
We’ll confirm which channels ShipBob fulfills, how inbound inventory is confirmed, who approves stock updates, and how ShipBob inventory is separated from FBA or other locations.
Some brands send every channel through ShipBob. Others keep Amazon in FBA and the store in ShipBob. We ask which channels this 3PL fulfills so stock writes only go where the receipt is true.
Warehouse access may be shared with a 3PL account manager. We ask who can access the account, who may approve a write, and which API or MCP permissions are available.
If Amazon FBA holds stock, it is not ShipBob's receipt. We ask that on the call so the available count for Amazon does not get overwritten by the 3PL count.
A receipt stays ShipBob’s to confirm. We ask whether inbound should appear as incoming only and which portal tasks stay with the person at the dock.
Extensiv ShipStation Veeqo ShipHero All integrations Platform Free assessment