> For the complete documentation index, see [llms.txt](https://docs.lidiacommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lidiacommerce.com/suites/lidia-b2b-suite/key-components.md).

# Key Components

## The key components of the **Lidia B2B Suite** 

{% content-ref url="/pages/EhGYZMosJSejUxRIag6y" %}
[Lidia Commerce Engine](/products/lidia-commerce-engine.md)
{% endcontent-ref %}

The core of the platform, providing robust capabilities for managing digital commerce operations, including catalog, customer, and order management.

***

{% content-ref url="/pages/PF9BGFMyWJewBIOk4Hsz" %}
[Lidia Console](/components/lidia-console.md)
{% endcontent-ref %}

A user-friendly administrative interface for managing business operations and customer interactions.

***

{% content-ref url="/pages/euWGj4CnAUmJrFK86NQK" %}
[Lidia API](/components/lidia-api.md)
{% endcontent-ref %}

Open and well-documented APIs to integrate with third-party systems like ERP and PIM.

***

{% content-ref url="/pages/uy1pqu34d5k3IR9uVSyB" %}
[Lidia Custom UI](/components/lidia-custom-ui.md)
{% endcontent-ref %}

Allows for the development of tailored user interfaces to fit specific customer and brand needs.

***

{% content-ref url="/pages/SjGQSYc8I9teOeQE7XTk" %}
[Lidia Worker](/components/lidia-worker.md)
{% endcontent-ref %}

Facilitates the execution of background processes, such as data synchronization and automated tasks.

The suite can also be enhanced with the **Lidia Network Console** for omni-channel capabilities, enabling seamless integration with physical stores for activities such as assisted sales or logistics coordination​​​.


---

# 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://docs.lidiacommerce.com/suites/lidia-b2b-suite/key-components.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.