> 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/architecture-overview/components-overview.md).

# Emporix Components Overview

The architecture comprises several core components that work together to create an autonomous and efficient ecommerce environment.

<figure><img src="/files/XhOc4mVm64PYuhDfS3As" alt="Emporix components architecture overview"><figcaption><p>Emporix components overview</p></figcaption></figure>

**Core Architectural Components**

* **Commerce Orchestration** - This layer serves as the central control mechanism for all business processes within the platform. Its purpose is to centrally control critical operations, ranging from managing orders to handling promotional processes. Commerce Orchestration embraces functionalities of [Commerce Engine - CE](https://developer.emporix.io/ce/) and [Value Stream Modeller - VSM](https://developer.emporix.io/value-stream-modeller/), powered by explicit APIs.
* **Agentic Commerce Intelligence** - This is the layer that leverages AI agents to introduce intelligent automation. The layer enables smart decisions that accelerate processes and reduce operational costs. It allows the platform to function without the need for human intervention in many routine or time-consuming tasks, driving operational efficiency and extensibility. Agentic comes with a library of AI agents and space to create custom agents using different tools and resources.
* **Semantic Commerce Data Layer** - This layer addresses data consistency and accessibility across the platform. Its role is to provide a unified, understandable database. It connects systems, processes, and teams, which enables consistent decisions across the entire organization.
* **Embedded Integration Layer** - This component is responsible for ensuring the seamless connection and embedding of various external systems. It integrates critical services such as ERP (Enterprise Resource Planning), PIM (Product Information Management), and other third-party systems. This layer is designed to eliminate the need for complex interface projects.

**Supporting and Functional Layers**

In addition to the core structural components, the architecture also includes:

* **Value Stream Examples** - The [Value Stream Modeller - VSM](https://app.gitbook.com/o/z8MNPigQv25NZe33g3AV/s/rSc4haeKWrTrOPHzdrMO/value-stream-examples/pl-introduction) offers ready-made process templates for all core commerce processes. These templates are designed to be customizable and available for immediate use.
* **Journey Aware Frontend** - This component is focused on the customer experience. It helps merchants to better understand the customer experience and design it appropriately.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.emporix.io/architecture-overview/components-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
