Four storefronts, four entities, one ledger
A cosmetics brand selling online across several markets was connected so that each storefront lands in the right legal entity — without swallowing the logistics system that already worked.
- Integrations
- Priority ERP
- E-commerce
- Multi-company
- Sector
- Cosmetics and online retail
- Status
- Running in production.
The challenge
An order captured in a storefront is not simply an order. It is an event that has to land in the right company, in the right currency, with revenue recognised in the right entity — and at the same time become a picking instruction in an entirely different system.
Why a standard implementation was not enough
With several storefronts and several entities, the failure mode is not an order that was not captured but an order captured in the wrong company — an error that surfaces in the financial statements, late. The temptation is to centralise everything and retire the warehouse system; that decision sounds clean, multiplies the cost of the project and puts a working operation at risk.
Architectural approach
Each storefront connects to one defined company — an explicit mapping, not logic that infers the entity from currency or address. Shipping samples without charge is handled in a separate entity, because it is a real inventory movement with cost consequences even when there is no invoice. The warehouse system boundary is preserved deliberately: the ERP holds the finance, the warehouse system holds the warehouse, and the integration connects them rather than replacing either.
What was delivered
- An order interface between the commerce platform and the ERP
- Explicit mapping of each storefront to its legal entity
- Handling of multi-currency activity
- A dedicated entity for free-of-charge sample shipments
- Preservation of the warehouse management system boundary