LCE Overview

Lidia Commerce Engine

Build composable commerce experiences

Lidia Commerce Engine (LCE) is a headless, API-first commerce platform. Use its domain APIs to build storefronts, mobile applications, business portals and integrations without coupling the customer experience to the commerce backend.

Headless API-first Microservice-based Cloud or on-premises

What LCE provides

LCE separates commerce capabilities from presentation. Each business domain is exposed through RESTful JSON APIs, so teams can compose only the services required by a solution and integrate them with existing ERP, CRM, PIM, payment and logistics systems.

01

Catalog

Products, variants, categories, brands, attributes and localized product data.

02

Pricing and inventory

Stores, warehouses, price lists, stock levels, reservations and SKU movements.

03

Customers and organizations

Users, roles, contacts, branches, organizational structures and permissions.

04

Carts and orders

Cart operations, checkout data, order lifecycle and order orchestration.

05

Fulfillment and returns

Delivery providers, fulfillment workflows, shipment tracking, claims and returns.

06

Promotions and content

Campaigns, coupons, storefront content, menus and dynamic pages.

How LCE fits into your architecture

Experiences Web, mobile, marketplace and business portals
Experience layer Your backend-for-frontend, integration API or Lidia UI layer
LCE domain APIs Commerce capabilities grouped by business responsibility
Enterprise systems ERP, CRM, PIM, payment, logistics and analytics providers

Deployment flexibility

Option Typical use Runtime API access
Cloud Managed or customer-governed deployments on supported cloud platforms. Kubernetes or virtual machines, according to the project architecture. An environment-specific HTTPS base URL.
On-premises Deployments requiring infrastructure, data residency or network control. Kubernetes or virtual machines in the customer environment. A private or public HTTPS base URL defined by the deployment.

Before you start

Ask your Lidia project administrator for:

  • The base URL for the environment you will use
  • A valid JWT access token or the approved credential flow for obtaining one
  • Your tenant and application context, when required by the selected operation
  • The roles and permissions enabled for your integration