Skip to content

Lekhha Platform

Start with what you have. Connect every transaction underneath.

Inventory, commerce, orders, fulfilment, logistics, payments, customer feedback and business visibility work as one operating journey — regardless of whether demand starts offline, at the counter, on an Online Store, through WhatsApp or social media, on a marketplace or on ONDC.

Commerce

Make inventory available for sales, shared-catalog journeys and supported peer transactions.

Explore Commerce →

Analytics

Understand what is happening across inventory, transactions, fulfilment, feedback and operating activity.

Explore Analytics →

Lekhha AI

Build future intelligence on connected operational data, not isolated records.

Explore Lekhha AI →

Enterprise integration

Connect Lekhha to the ERP. Keep the ERP as the system of truth.

Lekhha can operate at the commerce and execution edge while an enterprise ERP — for example SAP S/4HANA or ECC, Oracle ERP, Microsoft Dynamics 365, or another enterprise platform — remains the authoritative source for the master and transactional data that the enterprise chooses to govern there.

ERP remains authoritative

Keep enterprise-governed product, customer, pricing, inventory, finance and other agreed records mastered in the ERP according to the enterprise data-ownership model.

Integrate through governed interfaces

For SAP landscapes this can include supported APIs and OData services, IDoc/ALE messaging, REST/SOAP endpoints or middleware such as SAP Integration Suite. Equivalent governed interfaces can be used for other ERPs.

Lekhha extends the commerce edge

Use Lekhha for catalogue sharing, WhatsApp and social discovery, channel commerce, order orchestration, fulfilment, logistics, ratings and feedback while synchronising agreed events and data with the ERP.

ERP system of truth⇄Integration / middleware⇄Lekhha commerce & operating edge

Integration scope, direction, frequency, conflict rules and data ownership are defined per enterprise. A specific ERP connector or automated flow should only be represented as live after it has been configured and validated for that customer.