> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/api-documentation/api-guides/configuration/site-settings-service.md). # Site Settings Service Sites are used as virtual entities within a tenant. Sites can represent a web store, a physical store, a branded store, or a store for a specific market ### Key features and benefits * Associates information such as catalog, payment methods, shipping, and other details with a site * Overwrites or augments tenant-specific configuration with site-specific configurations * Configures information such as for which customer this site is intended * Configures whether all prices are shown site-wide, including or excluding taxes by default * Configures assisted buying for a particular site * Creates sites specific to a brand, a customer, or a market * Runs stores within your store * Creates a virtual representation of your physical stores, warehouses, or other locations --- # 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://developer.emporix.io/api-documentation/api-guides/configuration/site-settings-service.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.