Description
Inbound - Inventory Reconciliation Report provides detailed status of your inventory at SKU (and shipping plan) level.
Documentation
| Column | Description |
| Expected_Qty | Quantity of DKSU that seller input on shipping plan. This is the quantity that Deliverr expects |
|
Current_On_Hand_Qty (only on Inbound - Inventory Reconciliation report) |
Units currently available for sale with Deliverr |
|
Current_Unavailable_Qty |
Units currently unavailable for sale with Deliverr. These are processing at a fulfillment center, being transferred, are held for customer orders, etc. as broken down in the Seller Portal Product Detail Inventory details |
| SOLD_SHIPPED (only on Inbound - Inventory Reconciliation report) | Lifetime Units sold and shipped by Deliverr |
| Received_Qty | Units that have been received (on the PO) |
| Arrived_at_FC_Qty | Units that have arrived at FC but are yet to be received. This is inferred through carrier tracking timestamps |
|
In_Transit_Within_network (for forwarding plans only) |
Units that have been scanned at the crossdock and now are on their way from Deliverr's crossdock to the Fulfillment Center |
| In_Transit_to_Deliverr | For forwarding plans - units that are yet to arrive at Deliverr's crossdock. For direct plans - units that are yet to arrive at the Fulfillment Center |
| Noncompliance_Qty | Units in non compliance at the FC |
| Damaged_Qty | Units damaged while receiving or units that came in damaged |
| Never_Shipped_by_sellers |
This column sums up the following 2 inventory buckets: Box_Shortship_at_crossdock: For completed shipping plans, units in boxes that were never scanned at the crossdock. Hence the seller did not send in some boxes due to which we do not have a scan at the crossdock Abandoned_Qty: Units belonging to Shipping plans created more than 90 days ago and if the shipping plan has had no activity. We assume that the seller never plans on sending this shipping plan in |
|
Short_shipped_missing _scanned_at_cd |
Units belonging to boxes that were scanned at crossdock more than 50 days ago but have not been received yet. This can happen due to two reasons: 1) the units were lost while in transit from crossdock to FC or lost at FC; 2) seller shortshipped units in boxes |
| Shortship_missing_no_scan | Difference between expected_qty and all columns above. If we are unable to attribute inventory in any of the above buckets - the remaining (unaccounted for inventory) shows up here. If these units were confirmed to be lost or short ship, they would show up in the confirmed_lost_qty column |
| Confirmed_lost_qty | Units that were reported as lost |
| Row | Description |
| Excess Receive (only on Shipping Plan Report) |
For each DSKU, if there is a difference between PO received and (on hand + shipped & sold), a new row excess_receive would populate. If excess_receive is positive, this means that we received more than what PO data indicates. Possible reasons include receiving against incorrect or null ASNs. If excess_receive is negative, possible reasons include - damaged/lost qty post receiving, incorrect PO received number input by warehouses and later corrected through an audit |
| Other rows | Each row corresponds to a unique DSKU (and Shipping plan) |