Report Purpose
The purpose of this report is to
- enable the seller and Deliverr to reconcile shipments, and
- serve as a source of truth on all shipment data for the seller at the time at which it's generated.
Report Description
A seller creates shipping plans in Seller Portal to send inventory to Deliverr. Every shipping plan contains one or more shipments, every shipment contains one or more boxes, and every box contains one or more SKUs. This report provides information about shipments broken down by the SKUs that comprise them. It enables the seller to understand the status of their shipments and where their constituent units are until they are received by a fulfillment center.
For the seller's convenience, the first five columns of this report contain information about the shipping plan to which each shipment belongs. These rows are not used to compute subsequent rows. This report can be aggregated by shipping plan, shipment, or SKU (or any combination thereof) if desired. This is a snapshot report; that is, it contains information only about the time at which it's generated in Seller Portal at https://sellerportal.deliverr.com/reports.
Column Descriptions
| Column | Description |
| SHIPPING_PLAN_NAME |
Shipping plan name entered by the seller in Seller Portal. The shipment is part of this shipping plan. Note: If the seller updates the shipping plan name in Seller portal, this value will update. |
| SHIPPING_PLAN_ID | Unique identifier of the shipping plan |
| SHIPPING_PLAN_CREATION_TIME_ET | Time in ET at which the shipping plan was created by the seller in Seller Portal |
| SHIPPING_PLAN_TYPE |
This column will have one of the following values: 2. FORWARDING: A forwarding plan is comprised of a single shipment to a cross dock. Deliverr forwards this shipment to one or more fulfillment centers. |
| IS_PLAN_ARCHIVED |
This column will have one of the following values: 1. YES: The shipping plan has been archived by the seller in Seller Portal. 2. NO: The shipping plan has not been archived by the seller. |
|
SHIPMENT_ID |
Unique identifier of the shipment |
| EARLIEST_CROSS_DOCK_SCAN_DATE |
(Forwarding plans only) Date on which the first box in the shipment was scanned at a cross dock |
| SHIPMENT_STATUS | Current status of the shipment. See Understanding Inbound Shipment Status for the values this column can have. |
| DSKU | Deliverr's unique identifier for the SKU in the shipment |
| MSKU | The seller's unique identifier for the SKU in the shipment |
| EXPECTED_UNITS |
Units of the SKU that the seller input in the shipping plan. This is the quantity of the SKU that Deliverr expects in the shipment. Note: If the seller updates expected units in Seller Portal, this value will update. |
| RECEIVED_UNITS |
Units that have been received at a fulfillment center. These units cannot be damaged at the time of receiving, non-compliant, in transit, or shortshipped. Note: Occasionally, units may be received without an associated shipment recorded due to seller or fulfillment center error. Due of the lack of an associated shipment, such units will not appear in this report. |
| DAMAGED_UNITS | Units recorded as damaged by a fulfillment center. These units have arrived at a fulfillment center but are not sellable and will not leave this column until removed by the seller or disposed by a fulfillment center. |
| NONCOMPLIANT_UNITS | Units recorded as non-compliant by a fulfillment center. These units have arrived at a fulfillment center but are not sellable and will not leave this column until removed by the seller or disposed by a fulfillment center. |
| IN_TRANSIT_WITHIN_DELIVERR_UNDER_60_DAYS |
(Forwarding plans only) Units belonging to boxes that were scanned at a cross dock within the past 60 days and are in transit to a fulfillment center. Note: This value doesn't exist for direct plans because direct plan shipments are not sent to a cross dock. This value is based on time elapsed since box scan time, which may be later than EARLIEST_CROSS_DOCK_SCAN_DATE. |
| SHORTSHIPPED_IN_BOX |
(Forwarding plans only) Units missing from their boxes when they were received at a fulfillment center. This occurs when the seller ships fewer units in a box than indicated on the shipping plan. Note: This value doesn't exist for direct plans because box-level content information from fulfillment centers is currently only available for forwarding plans. |
| IN_TRANSIT_WITHIN_DELIVERR_OVER_60_DAYS |
(Forwarding plans only) Units belonging to boxes that were scanned at a cross dock over 60 days ago but have not been received at a fulfillment center. Note: This value doesn't exist for direct plans because direct plan shipments are not sent to a cross dock. This value is based on time elapsed since box scan time, which may be later than EARLIEST_CROSS_DOCK_SCAN_DATE. |
| IN_TRANSIT_TO_DELIVERR |
1. Direct plans: Units that have not been received at a fulfillment center. These units are either on their way from the seller to the FC or have not been shipped by the seller yet. 2. Forwarding plans: Units belonging to boxes that have not been scanned at a cross dock. These units are either on their way from the seller to a cross dock or have not been shipped by the seller yet. Note: For time in transit, compare report generation time to SHIPPING_PLAN_CREATION_TIME_ET. |
| EXCESS_RECEIVED_UNITS |
Units received over EXPECTED_UNITS, accounting for units in all prior columns. This occurs when the seller ships more units to Deliverr than indicated on the shipping plan. Note: If the seller updates the inbounded quantity on a shipping plan in Seller Portal, EXCESS_RECEIVED_UNITS here will update. |
| SUPPORT_CONFIRMED_LOST |
Units investigated and confirmed by Deliverr as lost. Deliverr will reimburse the seller for these units. |
| SUPPORT_CONFIRMED_SHORTSHIPPED |
Units investigated and confirmed by Deliverr as shortshipped by the seller |
| DISCREPANT_UNITS |
A positive value represents units requiring further investigation. A negative value represents units received, found, and/or reimbursed over EXPECTED_UNITS. 1. Direct plans: For complete direct plans, DISCREPANT UNITS = IN_TRANSIT_TO_DELIVERR - EXCESS_RECEIVED_UNITS - CONFIRMED_LOST_UNITS - CONFIRMED_SHORTSHIPPED_UNITS. For incomplete direct plans, DISCREPANT_UNITS = 0 until the plan is complete. 2. Forwarding plans: DISCREPANT UNITS = IN_TRANSIT_WITHIN_DELIVERR_OVER_60_DAYS - EXCESS_RECEIVED_UNITS - CONFIRMED_LOST_UNITS - CONFIRMED_SHORTSHIPPED_UNITS |
| SHIPMENT_DETAILS |
Link to shipment's page in Seller Portal |
Column Relationships
- There is exactly one MSKU per DSKU.
- EXPECTED_UNITS = RECEIVED_UNITS + DAMAGED_UNITS + NONCOMPLIANT_UNITS + IN_TRANSIT_WITHIN_DELIVERR_UNDER_60_DAYS + SHORTSHIPPED_IN_BOX + IN_TRANSIT_WITHIN_DELIVERR_OVER_60_DAYS + IN_TRANSIT_TO_DELIVERR - EXCESS_RECEIVED_UNITS.
- RECEIVED_UNITS, DAMAGED_UNITS, NONCOMPLIANT_UNITS, IN_TRANSIT_WITHIN_DELIVERR_UNDER_60_DAYS, SHORTSHIPPED_IN_BOX, IN_TRANSIT_WITHIN_DELIVERR_OVER_60_DAYS, and IN_TRANSIT_TO_DELIVERR are mutually exclusive; that is, a given unit can appear in only one of these columns.
- SHORTSHIPPED_IN_BOX supersedes SUPPORT_CONFIRMED_SHORTSHIPPED. Otherwise put, SUPPORT_CONFIRMED_SHORTSHIPPED is subordinate to SHORTSHIPPED_IN_BOX. As units are recorded by Deliverr as shortshipped against a forwarding plan shipment at a fulfillment center, SUPPORT_CONFIRMED_SHORTSHIPPED is decremented until it is 0 to keep these columns mutually exclusive.
- EXCESS_RECEIVED_UNITS is a subset of RECEIVED_UNITS. See (2) for how it is computed.
- IN_TRANSIT_WITHIN_DELIVERR_OVER_60_DAYS and EXCESS_RECEIVED_UNITS are never both nonzero. This is because as units are received against a forwarding plan shipment, IN_TRANSIT_WITHIN_DELIVER_OVER_60_DAYS is decremented until it is 0, after which IN_TRANSIT_WITHIN_DELIVERR_UNDER_60_DAYS is decremented until it is 0, after which EXCESS_RECEIVED_UNITS starts being incremented.
Row Relationships
- Unique Identification: Each row represents units of a single SKU within a single shipment. Otherwise put, each row is uniquely identified by a shipment-SKU pair. As a result, no two rows share both SHIPMENT_ID and MSKU.
- Grouping and Ordering: Rows are grouped by MSKU. Separate shipments sharing MSKU appear in reverse chronological order of SHIPPING_PLAN_CREATION_TIME_ET. Separate MSKUs appear in alphabetical order.