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.
Platform · ERP Integration
Extend commerce without replacing the enterprise system of truth.
Connect Lekhha with SAP and other enterprise ERPs so customer-facing commerce and execution workflows can move quickly while enterprise-governed data remains authoritative in the ERP.
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.
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.
Integration design
Decide ownership first. Then connect the workflows.
The integration should define which system owns each business object, what moves between systems, when it moves and how exceptions are reconciled.
Master data
Define authoritative ownership for products, customers, pricing, tax, locations and other governed master data.
Transactions & events
Exchange agreed orders, inventory movements, fulfilment milestones, payments, returns, ratings or other business events required by the enterprise process.
Reconciliation & controls
Define identifiers, acknowledgements, retries, error handling, auditability and reconciliation so both systems remain operationally consistent.
