> 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/administration/account/data-support-for-multiple-stores.md). # Data support for multiple stores Chord supports a "multi-store" architecture, i.e. sending data from more than one store to the same Chord instance. Chord displays the resulting data in aggregate while also providing the ability to filter by store. {% hint style="warning" %} This is an advanced feature. Please speak with someone at Chord before acting on the following. {% endhint %} ## Requirements These must be true: 1. All stores use the same OMS, such as Shopify. 2. It is acceptable that store data will not be isolated. ## Recommendations When configuring your **Chord CDP**: * We recommend creating unique Sources per store. The schema name of these Sources must follow a naming convention that we can provide. Use the correct write keys when sending events to each Source. * All sources should point to the same Chord Data Warehouse Destination. * We recommend the same approach for other Destinations (e.g. GA4, Klaviyo). It is up to how your business uses those services, but having multiple instances of each may make our data less effective. ## Limitations The **Integrations > Data Sources** portion of Chord does not currently have multi-store support. Please consult with us with regards to any implications that might have. Chord does not currently support **multiple currencies**. As a result: * All currency will be shown as USD, but will not have been converted. For example, sales worth €1,000 will be shown as $1,000. The correct symbol (e.g. "€") will not appear, nor will that $1,000 reflect any conversion rates between EUR and USD. * Given the above, reports that aggregate data between multiple currencies will not be accurate. For example, sales across three stores worth $100, €50, and £25 would be shown as $175. That total will not reflect any conversation rates between USD and other currencies. It is worth noting that despite the above, our data does have record of what currency each transaction was made in. That information will be used as we add multi-currency support. --- # 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/administration/account/data-support-for-multiple-stores.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.