Example sales orders fact table used throughout the qdo docs and tests. One row per order line, linking a customer to a product with fulfillment status, order amount, region, and order date.
connectiontest
dialectduckdb
rows5,000
generated2026-04-24T18:26:10+00:00
metadata
description
Example sales orders fact table used throughout the qdo docs and tests. One row per order line, linking a customer to a product with fulfillment status, order amount, region, and order date.
owner
Revenue Operations Analytics
coverage
7/7 columns documented
schema
column
type
null %
distinct
samples
id
BIGINT
0.0%
5,000
idSynthetic order-row identifier used in the sample fixture. Useful for row-level debugging, but not a business key to share externally.
customer_id
INTEGER
0.0%
1,232
customer_idForeign-key-style reference to the customer that placed the order. Joins to the customers fixture table on customer_id.
product_id
INTEGER
0.0%
1,217
product_idForeign-key-style reference to the ordered product. Joins to the products fixture table on product_id.
status
VARCHAR
0.3%
10
shippeddeliveredprocessingcancelledreturned
statusFulfillment lifecycle status for the order row. Use this for workflow and delivery-state analysis, but normalize malformed values before treating it as a strict enum.
amount
DOUBLE
2.7%
5,000
amountOrder amount in the fixture currency. Most analyses should exclude NULL amounts and review negative values before summing revenue.
region
VARCHAR
0.0%
4
LATAMNAEMEAAPAC
regionSales region used for rollups and reporting. Good first dimension for grouped query examples.