Successful customer orders in the webshop.
All orders since 2020-01-01.
Orders with their line items are in their current state (no history included).
| Name | Type | Attributes |
| —- | —- | ———- |
| production | s3 | One folder per model. One file per day.
• environment: prod
• format: json
• delimiter: new_line
• location: s3://datacontract-example-orders-latest/v2/{model}/*.json
• roles: [{‘name’: ‘analyst_us’, ‘description’: ‘Access to the data for US region’}, {‘name’: ‘analyst_cn’, ‘description’: ‘Access to the data for China region’}] |
No description.
usage: Data can be used for reports, analytics and machine learning use cases. Order may be linked and joined by other tables
limitations: Not suitable for real-time use cases. Data may not be used to identify individual customers. Max data processing per day: 10 TiB
One record per order. Includes cancelled and deleted orders.
| Field | Type | Attributes |
| —– | —- | ———- |
| order_id | None | No description.
• ref: #/definitions/order_id
• required
• primaryKey
• unique |
| order_timestamp | timestamp | The business timestamp in UTC when the order was successfully registered in the source system and the payment was successful.
• required
• tags: [‘business-timestamp’]
• examples: [‘2024-09-09T08:30:00Z’] |
| order_total | long | Total amount the smallest monetary unit (e.g., cents).
• required
• examples: [9999] |
| customer_id | text | Unique identifier for the customer.
• minLength: 10
• maxLength: 20 |
| customer_email_address | text | The email address, as entered by the customer.
• format: email
• required
• pii
• classification: sensitive
• quality: [{‘type’: ‘text’, ‘description’: ‘The email address is not verified and may be invalid.’}]
• lineage: {‘inputFields’: [{‘namespace’: ‘com.example.service.checkout’, ‘name’: ‘checkout_db.orders’, ‘field’: ‘email_address’}]} |
| processed_timestamp | timestamp | The timestamp when the record was processed by the data platform.
• required
• config: {‘jsonType’: ‘string’, ‘jsonFormat’: ‘date-time’} |
A single article that is part of an order.
| Field | Type | Attributes |
|---|---|---|
| line_item_id | text | Primary key of the lines_item_id table • required |
| order_id | None | No description. • ref: #/definitions/order_id • references: orders.order_id |
| sku | None | The purchased article number • ref: #/definitions/sku |
| Name | Type | Domain | Attributes |
| —- | —- | —— | ———- |
| order_id | text | | An internal ID that identifies an order in the online shop.
• title: Order ID
• format: uuid
• pii
• classification: restricted
• tags: [‘orders’]
• examples: [‘243c25e5-a081-43a9-aeab-6d5d5b6cb5e2’] |
| sku | text | | A Stock Keeping Unit (SKU) is an internal unique identifier for an article.
It is typically associated with an article’s barcode, such as the EAN/GTIN.
• title: Stock Keeping Unit
• pattern: ^[A-Za-z0-9]{8,14}$
• tags: [‘inventory’]
• links: {‘wikipedia’: ‘https://en.wikipedia.org/wiki/Stock_keeping_unit’}
• examples: [‘96385074’] |
The server is available during support hours
Data is retained for one year
Data is available within 25 hours after the order was placed
The age of the youngest row in a table.
Data is delivered once a day
The data is available during typical business hours at headquarters
Data is backed up once a week, every Sunday at 0:00 UTC.
