> 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/connect-sources/data-sources/sales-channel-module/omni-channel-sales-data-modeling.md).

# Omni-channel sales data modeling

## Omni-channel sales data modeling

{% hint style="info" %}
**This Explore is only available to Shopify OMS customers at this time.**
{% endhint %}

## Overview

E-commerce brands don’t sell in just one place—and your data shouldn’t treat each sales channel as a silo. Chord’s new omni-channel sales data modeling brings together sales data from all your key commerce channels—including Shopify, Chord OMS, Salesforce, and third-party marketplaces like Amazon—into a unified, comprehensive dataset.

For Chord brands with the Amazon Selling Partner source, this Explore combines Amazon and Shopify transactional line items into a unified Explore.

This omni-channel approach allows you to:

* Analyze total sales across all channels in one place.
* Compare performance across categories or by individual channel.
* Break down revenue by channel to support reporting and strategy.
* Track trends and customer behavior regardless of point of sale.

## Core event attributes

* Line Items
  * Source System: Can be Amazon or Shopify
* Order
* Order Created Date

## Where to find this data in Chord

Once your Amazon Selling Partner source events are ingested by Chord, you will be able to further analyze this data on Chord.

{% hint style="info" %}
For assistance with getting Amazon Selling Partner data ingested on Chord, please contact <help@chord.co>.
{% endhint %}

Once your Amazon Selling Partner data has been ingested and synced, follow the steps below to dig into your data:

1. Log into the Chord Commerce data platform.
2. Navigate to **Explores** tab on the **Analytics** page.
3. Click on the **Explores** dropdown on the left side of the page.
4. Select the\*\* Omni-Channel Sales\*\* Explore.


---

# 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/connect-sources/data-sources/sales-channel-module/omni-channel-sales-data-modeling.md?ask=<question>&goal=<user_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.