Goods and ledgers across wholesale, chains, and online
Trade systems get hard because one batch of goods moves through wholesale, stores, and online at once. Stock and pricing have to line up in one place, or overselling and channel conflict show up together.
Wholesale ledgers are hard because of customer tiers, layered pricing, and payment terms. The same SKU carries different prices for different buyers, and goods often ship before the order is entered—the system has to tolerate that reality.
The hard part of a chain is not how one store sells—it is how head office and stores divide authority. Products, prices, and promotions must stay under head office control while replenishment and rosters stay editable in the store.
Online business puts pressure on both ends: the storefront must be fast and campaign-ready, the back office must reconcile and fulfil. Stock and order status in between are the shared truth.
Start from how the work happens today, what must change, and what stays—written as a checkable scope list.
Fix data definitions, interfaces, and the permission model, and confirm how we connect to existing ERP, finance, and hardware.
Ship module by module, integrate key flows against real data, with acceptance criteria written before work starts.
Roll out in phases, train the frontline, hand over deployment and runbooks, and keep iterating afterwards.
Tell us how the work happens today, where it breaks, and when you need it live. We will come back with a scope you can check and a phasing plan.