---
title: Orders
slug: uDhX-orders
docTags: 
createdAt: 2024-12-04T01:04:21.646Z
---

### Overview

Chord utilizes transactional data from the OMS (Chord OMS, Shopify, etc.) to derive the orders dataset.

### Created vs. Completed Orders

Chord has two different order concepts:

- **Created Order: **When the order was first created in the OMS. This date will be most closely aligned with how OMSes report orders.
- **Completed Order: **When the order is considered complete, either when it's closed or fully fulfilled. This timestamp is useful for financial reporting, such as revenue recognition.
  - For Shopify, the `closed_at` timestamp is generated for orders in Shopify that are automatically archived. If this feature is not enabled, the last updated closed fulfillment date is used as the completed at date.
  - For Chord OMS, the order is considered completed when the `completed_at` date is not null. This means that the order does not necessarily have a state = 'complete', since states can change after the order completion (for example in the case of a refund).

### Orders vs. Sales Explores

The "Orders" explore contains all orders regardless of status, whereas the "Sales" explore includes only completed orders.







:::hint{type="success"}
if you have any questions or need help, please reach out to us at [help@chord.co](mailto\:help@chord.co)
:::