> 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/generalconcepts.md).

# General Concepts of Emporix

Get an overview of Emporix's main characteristics and features.

This page introduces the main concepts of the Emporix solution: tenants and sites, working with the API, audit logs, and the free trial.

{% hint style="info" %}
Emporix products work together as **Autonomous Commerce Execution**<sup>**®**</sup>**&#x20;(ACE**<sup>**™**</sup>**)**. To see how the components fit together, check out the [Components Overview](https://developer.emporix.io/core-concepts/components-overview.md).\
If you're interested in these products, contact the [Sales Team](mailto:sales@emporix.com).

To explore the products, see the documentation of [Commerce Engine](https://developer.emporix.io/user-guides/), [Value Stream Modeller](https://developer.emporix.io/vsm-guides/), [Agentic Commerce Intelligence](https://developer.emporix.io/agentic-commerce-intelligence/), and [B2B Commerce Frontend](https://developer.emporix.io/frontend-guides/).
{% endhint %}

## Solution overview

Emporix brings its products together as Autonomous Commerce Execution<sup>®</sup> (ACE<sup>™</sup>). Commerce Engine provides the commerce core, Value Stream Modeller automates your business processes, Agentic Commerce Intelligence adds AI agents, and the B2B Commerce Frontend offers a ready-to-use storefront. Cockpits and tools support orders, documents, search, and data imports. See the [Components Overview](https://developer.emporix.io/core-concepts/components-overview.md) for details.

Emporix Commerce Engine is a digital commerce solution for B2B businesses and advanced B2C scenarios. It uses a composable architecture, which makes it flexible and scalable. It follows MACH principles (Microservices, API-first, Cloud-native, and Headless), so you can adapt it to a wide range of business needs. The headless architecture lets you choose your own front-end presentation layers, so you can decide how you engage with customers. The cloud-native design provides high availability and dynamic scalability, so you can focus on your business and not on the underlying infrastructure.

For B2B commerce, Emporix provides features that support business operations and improve the customer experience:

* **Customer-Specific Pricing** – Manage individual pricing agreements and frame contracts.
* **Bulk Pricing and Discounts** – Support volume-based pricing and discount algorithms.
* **Coupons and Rewards** – Offer coupons and reward points to your customers.
* **Advanced Quoting and Approval Workflows** – Streamline quoting processes and compliance workflows.
* **Flexible Invoicing and Payment Options** – Provide detailed invoicing and support various payment methods.
* **Customer-Specific Catalogs** – Manage tailored catalogs for different customer groups.

Emporix offers many more services, from catalogs and pricing to checkout, orders, and AI. For all services and their API references, see the [List of API Services](https://developer.emporix.io/api-documentation/quickstart/list-of-api-services.md). To make your first API call, follow the [Getting Started with Emporix API](https://developer.emporix.io/api-documentation/quickstart/api-intro.md) guide.

## Tenants and sites

### Tenants

Emporix is a multi-tenant SaaS solution. All tenants share the same hardware and software infrastructure. They are virtually separated by tenant IDs and access tokens.

You can get a tenant in two ways:

* **Free trial** – a time-limited tenant for evaluation. See [Free trial](#free-trial).
* **Licensed setup** – a tenant for your company after you become a customer. To create one, follow the [Creating your first tenant](https://developer.emporix.io/getting-started/creating-a-tenant.md) guide.

### Sites

A site represents a specific shop, warehouse, or other independent facility. You can run multiple sites in one tenant, for example to serve different markets or brands.

{% hint style="info" %}
To learn more about sites in the Emporix ecommerce system, check out the [Sites guide](https://developer.emporix.io/user-guides/core-commerce/sites.md).
{% endhint %}

## Working with the API

### Regions

Emporix is hosted on Google Cloud in Europe, Netherlands – Eemshaven.

### API base URL

`https://api.emporix.io`

{% hint style="danger" %}
We strongly advise you to use the host and domain names in your applications instead of hardcoding any IP address of the API hosts. IP addresses can change at any time without prior notice.
{% endhint %}

### Authentication and authorization

All requests sent to the Emporix API require authorization with a valid access token. To obtain an access token, you need your Emporix API keys. The keys are generated automatically when you create a tenant.

{% hint style="info" %}
To learn more about access tokens in the Emporix API, check out the [Authorization and scopes guide](https://developer.emporix.io/api-documentation/quickstart/authentication-and-authorization/tokens-and-scopes.md).
{% endhint %}

### JSON

The majority of the HTTP API endpoints consume and produce standard `application/json` payloads. To ensure that payloads are encoded correctly, use `Content-Type: application/json` in your HTTP header when sending POST requests.\
When consuming a JSON response, ignore any unrecognized fields in JSON objects of responses, or deal with them so that they do not cause the client application to crash. The API assumes clients behave properly and considers the addition of new fields to be backward-compatible for existing clients. In addition, client applications must not rely on the presence of undocumented fields. Fields returned by an undocumented endpoint can be renamed or removed at any time without prior notice.

### Identifiers

Some resources contain a field named `id` that uniquely identifies a resource. The `id` value is generated by Emporix when a resource is created.\
Some resources contain an additional field named `code` that also uniquely identifies a resource. However, you need to specify the `code` field in the request body when creating a resource.

### Update guarantees

Different kinds of requests in the Emporix API offer one of two update guarantees, as described below.

#### Strong consistency (read-after-write consistency)

Whenever a resource is successfully updated or created, it is guaranteed that in a subsequent read (called *read-after-write*), the returned resource contains all the values from the latest successful update.

This type of consistency is usually available for all CRUD endpoints that do not require complex background processing. For example, an update to the `Customer.firstName` field is accessible across the Emporix API immediately.

#### Eventual consistency

Eventual consistency applies to all APIs that require background processing conducted in a non-blocking manner, usually through event-based processing or batching. In this scenario, it is guaranteed that all successful updates are processed and reflected by the system as soon as possible (or according to the detailed specification for a particular API). However, a read subsequent to a successful write may return non-updated values.\
An example of eventual consistency is the `Product` search API, which requires indexing of `Product` data. As this is a costly operation that leverages an integration, the indexing runs asynchronously and may take longer than a subsequent read after a successful write.

## Customer audit logs

Admin users can review customer change history in the Management Dashboard on the customer **Audit Logs** tab, and across entities in **Administration** -> **Audit Logs**. See [Audit Logs](https://developer.emporix.io/user-guides/management-dashboard/administration/audit-logs.md).

You can also request customer audit logs from Emporix by contacting the [Support Team](mailto:support@emporix.com). The logs are kept for 2 years and include create, update, or delete operations with the tenant, timestamp, and the person who performed the actions.

## Free trial

You can try out Emporix completely free of charge for 14 days before you decide to buy. With the free trial, you get instant access to the solution, an interactive sandbox, and sample data, with onboarding support from the Emporix team, so you can test the functionality before you decide to become our customer. To start, go to the [free trial page](https://www.emporix.com/emporix-free-trial).

{% hint style="success" %}
***What are the differences between a free trial and a paid plan?***

The free trial gives you access to the full feature set for evaluation. It is time-limited and intended for testing. This approach brings the following benefits:

* Full experience of the Emporix system during the free trial.
* Easy migration from a free trial to a paid plan (your data remains in the system).
  {% endhint %}

When your free trial ends, the Sales Team will contact you to hear about your experience with our products.


---

# 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/generalconcepts.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.
