




Problem statement
A traditional vegetable wholesaler needed to digitise ~600 daily orders with end-to-end flow: PO → confirm → pick/pack → DO → invoice → inventory transfers → reporting, while operating mainly offline with periodic sync.
In addition, the internet connectivity in that area was unstable as well.
Why others struggle
1) Most vendors build “online-first” ERPs that fail in warehouse/offline realities and operational peak loads.
2) Hard to model a real trading operation with credit control, SOA, audit trails, and document generation tightly linked to inventory and delivery ops.
How we solved it (platform strengths)
1) Built merchant ordering module + internal operations module with ACL/permissions and full action tracking.
2) Implemented offline-first design with 15-min sync; AWS used as backup/sync server.
3) Covered operational modules: customer/merchant profiles, pricing groups, picking list, DO/invoice workflows, inventory transfers, reporting (SOA, GST, etc.).
4) Deployed an on-premises server for local operations that syncs with AWS in real time, ensuring that incoming merchant orders are seamlessly synchronized.
Improvements & ROI (expected/typical impact)
1) Cycle time reduction: faster order processing + fewer rework loops during peak ordering windows.
2) Lower ops overhead: less manual admin for DO/invoices/SOA generation.
3) Risk control: audit logs + credit controls reduce disputes and leakage.
