Skip to content

Order Backorder

Table name:

  • referenced in Insights SQL queries: "ORDER_BACKORDER"
  • in data catalog export: marts_mdc__order_backorder

History of the backorders on your orders since 2024-06-07, one row per backorder and product that caused it. A backorder starts when an order cannot get its stock and ends when the order gets its stock (processing status queued_to_submit) or stops waiting for another reason, for example a cancellation. Time on hold is reported in on_hold_hours and is not part of backorder_hours. The time an order waits to be submitted to the warehouse after it got its stock is not counted. An order can have several backorders, and a backorder caused by several products has several rows, so count a backorder once by order_id and backorder_number. Backorders that begin and end within the same second, and backorders of orders that no longer have product lines, are not listed. Join with the Order model on order_id.

Columns

Column Type Description
account_id number Identifier for the account that placed the order.
order_id number Unique identifier for the order within the system.
order_number varchar The primary order identifier as defined by the order source. Typically the customer-facing order number (e.g. shown in confirmation emails), but is also commonly set to an internal reference such as a shipment or fulfillment number when sent from an ERP.
backorder_number number Number of the backorder within the order: 1 for the order's first backorder, 2 for the second, and so on.
backordered_at_utc timestamp_ntz When the backorder started, in UTC.
backorder_warehouse_id number Identifier of the warehouse the order was in when the backorder started. The order may have been moved to another warehouse later.
backorder_warehouse_name varchar Name of the warehouse the order was in when the backorder started.
product_id number Unique identifier of the product.
sku varchar SKU of the product.
product_name varchar Name of the product.
ordered_quantity number Units of the product currently on the order. This is not the number of units short (see missing_quantity). Null when the product has since been removed from the order.
missing_quantity number Units of the product that were short when the order went on backorder. Filled only when sku_attribution is recorded, otherwise null.
sku_attribution varchar How the product is known to have caused the backorder.
recorded: ShipMonk recorded the product as short when the order went on backorder. Available for part of the backorders since 2026-11-10.
certain: nothing was recorded and the order has a single product.
estimated: nothing was recorded, and the daily stock snapshot showed the product short in that warehouse on that day or the next.
unknown: nothing was recorded and the stock snapshot showed no product short, so every product of the order is listed.
released_at_utc timestamp_ntz When the backorder ended, in UTC. Null while the backorder is open.
release_status varchar Processing status of the order when the backorder ended, with the same values as processing_status in the Order model. queued_to_submit means the order got its stock. Any other value means the order stopped waiting for another reason, most often cancelled, submitted, fulfilled_by_3rd or subscription. Null while the backorder is open.
released_to_warehouse_id number Identifier of the warehouse the order was in when the backorder ended. It differs from backorder_warehouse_id when the order was moved to another warehouse during the backorder. Null while the backorder is open.
released_to_warehouse_name varchar Name of the warehouse the order was in when the backorder ended. Null while the backorder is open.
backorder_hours number Hours the order waited on backorder, from start to end without the time on hold, rounded to two decimals. Null while the backorder is open.
on_hold_hours number Hours the order was on hold during the backorder, rounded to two decimals. Add it to backorder_hours for the full time from start to end. Null while the backorder is open.