Start from the ERP, not the storefront
An online store that lives beside the management system always drifts: a price changed on one side, stock sold out on the other, a customer ordering an unavailable item. The right starting point is the list of data the ERP must push to the store.
In Kauehi, the downstream flow covers products, prices, stock, images and customers; the upstream flow sends orders back. Four dedicated modules keep this sync running, without re-entry.
Catalogue, prices and stock: from the ERP.
Orders: to the ERP, automatically.
Customers: shared between both.
Check your ERP first
Project cost and timing depend mostly on the connector. Kauehi runs six adapters in production: TEM, Odoo, Micronix, Iabako, Lexi and WooCommerce. EBP connects through the ATOO gateway, via WooCommerce, and Sage is supported with a connector set up per project.
There is no native adapter yet for Vaka, SAP Business One or Microsoft Dynamics: Devlab can build the connector on quotation, with the same scope as the existing adapters.
Take payment in CFP francs
For customers in French Polynesia, the displayed price and the amount charged should be in XPF. Kauehi integrates PayZen (Lyra) card payment: charges in XPF, automatic confirmation and tracking of every transaction in the back office.
For business customers, the retailer approves trade accounts, and a trade customer's basket can become a quote request handled in the back office.
Install it yourself or use an operated service
Two models exist. With software you install, the retailer configures and develops the store itself or with a contractor. With an operated service, the store, the sync and payments are delivered, hosted and maintained by one team.
Kauehi follows the second model, from Tahiti: you install nothing and maintain no code. The domain name, the brand and the data (catalogue, customers, orders) stay with the retailer and are handed back if it leaves.
Build pages without touching code
Once the storefront is live, pages are built block by block, with a theme specific to each retailer. Depending on enabled modules and permissions, an AI assistant suggests pages or changes, and a connected agent can read, propose or apply changes within the authorised scope.