> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/commerce-data-models/chords-methodology-as-compared-to-other-platforms/shopify.md). # Shopify ### Overview Chord ingests raw data directly from Shopify and then transforms this data through a data modeling layer to clean and enrich for more efficient, enriched, and meaningful analyses. Chord's data models can differ from what users see directly in the Shopify platform. ### Variations between Chord's data models and the Shopify platform **Order State** Chord provides two views of orders: * Orders placed regardless of fulfillment status or cancellation. * Completed orders, a subset of all orders defined as an order that has a `closed_at` timestamp and has been fully fulfilled. 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 date. Shopify includes any orders placed regardless of fulfillment status or cancellation. The "Orders" dataset displays all orders, whereas the "Sales" dataset includes completed orders only. To get to a view closer to Shopify, use the “Orders” Explore to view all orders and use the "Order Created At" date field instead of "Order Completed At." **Timestamps** Chord's models provides options for both `Order Created At` and `Order Completed At`, or `Closed At`, timestamps. Shopify uses the last `Edited At` timestamp in reporting if the order was edited, and if not edited, the `Order Created At` timestamp. For example, if an order were placed in January and edited in Shopify in February, it would show in February orders. Yet, unedited orders placed in January would show in January orders. Within Chord, these orders would show either when placed in January or when closed. **Timezones** Chord provides various timezones for both the "Order Created At" and "Order Completed At" fields so you can customize them to your timezone. Chord's default timezone is UTC and provides the following additional timezone options: Pacific, Mountain, Central, and Eastern. In Shopify, the timezone can be configured in settings, so you can check the timezone of your account to then use the same timezone within Chord. {% hint style="success" %} if you have any questions or need help, please reach out to us at {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/model-your-data/commerce-data-models/chords-methodology-as-compared-to-other-platforms/shopify.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.