Grokart.
Grocery has the widest catalogue and the least tolerance for a substitution.
- Client
- Grokart
- Sector
- Grocery, quick commerce
- Scope
- App + web + admin
- Stack
- React Native, Node.js, PostgreSQL
A grocery commerce build across app, web and admin, covering catalogue, ordering, picking and fulfilment.
What made it hard.
Stock accuracy per store decides whether the delivery promise is deliverable or a cancellation.
Rider supply
Demand spikes in twenty-minute windows. Supply has to be forecast, not reacted to.
Slot honesty
Showing a delivery window you cannot meet costs more than showing a longer one.
Unit economics
Every extra minute and every failed drop is measurable margin.
What we shipped.
A grocery commerce build across app, web and admin, covering catalogue, ordering, picking and fulfilment.
How it holds up.
Dispatch is built as its own service with replay tooling, and rider apps are engineered for low-end handsets and intermittent connectivity from the start.
The systemAvailability is computed per store rather than centrally, because a national stock figure is meaningless to a shopper.
Theirs, from day one.
Repositories, cloud accounts and documentation sat with the client throughout. Senior engineers wrote the production code rather than specifying it.
Ask for the full metrics on a call →More grocery, quick commerce work.
All 42 case studies →Building something like Grokart?
Tell us what you are building. A senior engineer replies within one business day. NDA on request.