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

# Emporix Components Overview

Emporix is a sophisticated, modular solution designed to support modern digital commerce, focusing heavily on central control, intelligent automation, data unification, and seamless integration.

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

<figure><img src="https://2028662919-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6GTRpjfleJymwcc6AX3v%2Fuploads%2Fgit-blob-aac419550b7a9a48ce103d6ebe474ec2a9f4aa1e%2Fmarchitecture-a2-v20-business.svg?alt=media" alt="Emporix components architecture overview"><figcaption><p>Emporix components overview</p></figcaption></figure>

{% hint style="info" %}
**Context Model Integration**, **Interaction Hub**, and **AI Experience Builder**, shown in the diagram, are still in development and planned for early 2027. For more information, visit the [Emporix website](https://www.emporix.com/ace-launch-fall-2026#context-model).
{% endhint %}

The diagram groups the components into three layers: execution and consumption at the top, intelligence and trust in the middle, and data and context at the bottom.

**Execution and consumption**

This layer is where customers, buyers, employees, and AI agents interact with the solution. It contains the following channels:

* **B2B Storefronts** – Customer-facing B2B shops built on the [B2B Commerce Frontend](https://developer.emporix.io/frontend-guides/).
* **Agents** – AI agents that work with the solution on behalf of buyers and employees.
* **Cockpits** – Workspaces where employees handle specific business tasks. For example, the [Document Intake Cockpit](https://developer.emporix.io/document-intake-cockpit/) receives documents of configured types and lets you monitor intake and review them.

**Intelligence and trust**

This layer contains the following components that control and automate commerce processes:

* **Value Stream Orchestration** – A tool-agnostic layer for process orchestration, integration, and automation platforms. It embraces the functionality of [Value Stream Modeller (VSM)](https://developer.emporix.io/vsm-guides/) and the [Orchestration Engine (OE)](https://developer.emporix.io/oe-user-guides/). VSM also offers ready-made process templates for core commerce processes, which you can customize and use right away.
* **Commerce Foundation** – The trusted commerce core, covering customers, products, pricing, quotes, and orders. It is provided by the [Commerce Engine (CE)](https://developer.emporix.io/user-guides/) and powered by explicit APIs.
* **Extensibility** – Agentic deployment of business logic, including hosting. It also covers [extensions](https://developer.emporix.io/user-guides/extensibility-and-integrations/extensibility-cases/custom-extensions.md), which add custom logic to the solution, and [mixins](https://developer.emporix.io/user-guides/core-commerce/mixin-schemas.md), which add custom attributes to existing entities.
* **Agentic Commerce Intelligence** – The layer that uses AI agents, MCP, and tools to act on live commerce context. It enables smart decisions that accelerate processes, reduce operational costs, and take over routine or time-consuming tasks. It comes with a library of AI agents and space to create custom agents using different tools and resources. See the [Agentic Commerce Intelligence](https://developer.emporix.io/agentic-commerce-intelligence/) documentation.
* **Interaction Hub** – (In development) Design and run processes by prompt. See the [Interaction Hub](https://www.emporix.com/ace-launch-fall-2026#interaction-hub) page on the Emporix website.
* **AI Experience Builder** – (In development) Provide the right information and actions for every customer and employee. See the [AI Experience Builder](https://www.emporix.com/ace-launch-fall-2026#experience-builder) page on the Emporix website.

**Data and context**

This layer provides the data that the components above rely on. It contains the following components:

* **Business Systems** – Connections to systems such as SAP, ERP, CRM, and PIM, with more than 4,000 connectors. This eliminates the need for complex interface projects.
* **Live Operational Data** – The current state of customers, orders, and inventory.
* **Context Model Integration** – (In development) A unified model of events, objects, relations, process context, and history. It connects systems, processes, and teams, which enables consistent decisions across the organization. See the [Context Model Integration](https://www.emporix.com/ace-launch-fall-2026#context-model) page on the Emporix website.

**Cockpits and tools**

In addition to the layers in the diagram, the following cockpits and tools support specific business tasks:

* **Order Intake Cockpit** – A workspace for uploading purchase order files, monitoring extraction and validation, and working with the sales orders created from them. See the [Order Intake Cockpit](https://developer.emporix.io/order-intake-cockpit/) documentation.
* **Document Intake Cockpit** – A workspace for receiving documents of configured types, monitoring intake, and completing the review actions available in your tenant. See the [Document Intake Cockpit](https://developer.emporix.io/document-intake-cockpit/) documentation.
* **Search Cockpit** – A workspace for managing search indexes for custom instances, customers, and legal entities, and for running and reusing saved searches. See the [Search Cockpit](https://developer.emporix.io/search-cockpit/) documentation.
* **Import Tool** – A tool that brings data from external systems into Emporix with connections, streams, and import monitoring. See the [Import Tool](https://developer.emporix.io/import-tool/) documentation.


---

# 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/core-concepts/components-overview.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.
