Blog
Notes on running a business on one dataset.
Why overselling is an architecture problem, what FEFO actually saves you, and why your registered firms and your outlets are not the same tree.
Why your counter and your website should share one inventory
Overselling is not a website bug — it is an architecture decision. When the counter, the marketplace and the online store each keep their own stock, drift is guaranteed.
Read moreFEFO vs FIFO: the picking rule that pays for itself
First-expiry-first-out is how pharmacies, grocers and pet stores stop writing off stock they could have sold. Here is why FIFO quietly fails.
Read moreLegal entity vs outlet: the distinction most ERPs get wrong
Your registered firms and your physical outlets are different things. Software that forces them into one tree makes you choose which truth to break.
Read moreOne price per product is why your margin does not add up
A 500g pack and a 1kg pack carry different printed prices and different margins. Systems holding one price per product push the difference onto your counter staff.
Read moreOne database per business: what self-hosted actually buys you
Multi-tenant SaaS separates customers with a tenant-id column and code that must never be wrong. A database per business makes isolation a physical boundary.
Read moreGet started
See it shaped like your business.
Tell us what you sell, how many outlets and registered firms you run and where you sell. We will walk you through a real system set up like yours — not a generic demo.