Receiving
Overview
A Warehouse Receiving Order (WRO) is how ShipBob manages inbound shipments into their fulfillment centers. Some other solutions call this an “ASN” (Advanced Ship Notice).
This guide will walk you through building an integration to send inventory to ShipBob and sync it back to your system.
How It Works
Here’s the flow of creating and tracking a Warehouse Receiving Order:
Step 1: Check if Products Exist in ShipBob
Before creating a WRO, every product needs an inventory_id from ShipBob.
Check if a product exists:
If the product doesn’t exist, create it first:
inventory_id when you create products in your system. This way, you won’t need to look them up every time.Step 2: Create a WRO
Once you have your inventory_id values, create the WRO:
Example request (sending packages):
What you’ll get back:
box_labels_uri from the response in the next step if you are fetching box labels.Package types:
- Package - For boxes (max 50 boxes per request)
- Pallet - For palletized freight shipments (each pallet is a separate box)
- FloorLoadedContainer - For container shipments (entire container as one box)
Creating WROs with Lot Items
If you’re sending lot-tracked items (products with expiration dates or batch numbers), you must include lot_date and lot_number for each item in your WRO.
Example request with lot items:
Key fields for lot items:
Both lot_number and lot_date are required for lot-tracked items. If you omit either field, the WRO creation will fail.
Make sure the product is already created in ShipBob and you have the inventory_id before creating the WRO. You can check if a product is lot-tracked by looking at the product details in the ShipBob dashboard or via the GET Product API.
Multiple lots in one box:
You can include multiple lots of the same product or different products in a single box:
Step 3: Generate Box Labels (Optional)
Print box labels to help the warehouse identify your shipment:
This returns a PDF with labels for each box/pallet. Print and attach them to your shipment before sending.
Step 4: Poll for Completed WROs
Set up a recurring job (every 15-30 minutes) to check for completed WROs that need to be synced.
Check for completed WROs:
This returns all WROs that are:
- Completed - The warehouse has finished processing them
- Not synced - You haven’t updated your system yet (ExternalSync=false)
Here’s what to do with each completed WRO:
- Get the inventory quantities from the WRO
- Update your system with the new inventory levels
- Mark the WRO as synced so you don’t process it again
Example code:
Step 5: Mark WRO as Synced
After updating your inventory system, mark the WRO as synced to prevent duplicate processing:
This endpoint accepts an array of WRO IDs, allowing you to mark multiple WROs as synced in a single request.
Advanced: Track Individual Boxes
Want to see details for each box? Use this endpoint:
This shows you the status and quantities for each box, which would enable you to do partial receiving.
Understanding the Inventory Quantities
When you sync a completed WRO, you’ll see three quantity fields:
stowed_quantity when updating your system. This may be less than expected if items were damaged or missing.Example:
Important Fields
package_type - Determines how your shipment is configured. Choose based on your shipping method:
- Package - Standard boxes shipped via carrier (max 50 per request)
- Pallet - Palletized freight shipments (each pallet = one box)
- FloorLoadedContainer - Full container shipments (entire container = one box)
expected_arrival_date - The date your shipment is expected to arrive at the fulfillment center. Must be set to a future date - using today’s date or a past date will result in an error.
purchase_order_number - Your internal PO number or shipment identifier. Use a unique value for each WRO to simplify tracking and reconciliation.
tracking_number - The carrier tracking number for each box or pallet. This enables the warehouse to scan and verify your shipment upon arrival.
is_external_sync - A boolean flag that tracks whether you’ve synced the WRO data back to your system:
- Default value:
falsewhen the WRO is created - Query unsynced WROs: Use
ExternalSync=falseto find WROs that need processing - Mark as synced: Set to
trueafter updating your inventory system - Purpose: Prevents duplicate processing of the same WRO
To mark one or more WROs as synced, use the batch endpoint:
WRO Status Flow
Your WRO goes through these stages:
Awaiting status.For complete status reference including hub-related statuses, see the Status Reference documentation.
Common Issues
Arrival date must be in the future
Set expected_arrival_date to tomorrow or later. Don’t use today’s date or past dates.
Product with inventory_id X does not exist
Create the product first, then use the inventory_id it returns.
WRO stuck in Processing for days
Contact ShipBob support with your WRO ID. The warehouse might be experiencing delays.
How to find the fulfillment center ID?
Make a request to the GET Fulfillment Center endpoint at /2026-01/fulfillment-center to get a list of fulfillment centers you have access to.
Tips
- Poll every 15-30 minutes - Receiving can take hours or a few days depending on warehouse volume
- Use unique PO numbers - Makes tracking and reconciliation easier
- Always verify
inventory_idexists - Prevents WRO creation failures - API rate limit - 150 requests per minute
- Consider time zones - Dates are in UTC; convert appropriately

