Krushnay ERP
We start with how you order today
Whatever it is — WhatsApp groups, a notebook, a spreadsheet — that is the process we have to fit, not replace on day one.
About us
We built this because the numbers never added up
Not because they were wrong, but because nobody could say why. That gap — between a food cost everyone agrees is too high and any evidence of where it goes — is the whole reason Krushnay ERP exists.
Where it started
Every kitchen we looked at had the same hole in it
Orders placed on WhatsApp. Rates agreed on a phone call and remembered differently by two people. Deliveries signed for on a scrap of paper that never reached the office. Stock moved between branches on a Friday evening and recorded by nobody.
None of it is theft, and most of it is not even carelessness — it is what happens when busy people are asked to keep records with tools that were never meant for the job. But the effect is the same: at the end of the month there is a number, and no way to take it apart.
We started building for one restaurant group with exactly that problem. The rule we set ourselves was simple and has not changed: if a figure appears on a screen, you must be able to click through to the person, the document and the moment it came from.
What we believe
- Transparency beats control. The aim is not to catch staff out. It is to make the honest version of the work the easiest version to do.
- Software must survive the floor. Cold rooms have no signal, hands are wet, and nobody reads a manual at a delivery door.
- A number with no trail is an opinion. Every figure here carries who, when and against what.
- If a screen needs training, that is our mistake. Not the user's.
How we work
We set the system up with you, not for you
An empty ERP handed over with a login is how most of these projects quietly die. Your catalogue, your units, your vendors and their rates are the work — so we do that part together before anybody is asked to use it.
One branch first
A single kitchen running properly teaches us more than five running badly. The rest follow once the first one is boring.
You reach a person
Support is a phone number and an email address that a human being answers, not a ticket queue.
Where we work
The UAE and India, properly rather than nominally
Most software claims to support both by putting a currency symbol behind a setting. The differences that actually matter are elsewhere: a UAE business holds a trade licence and a TRN, an Indian one a GSTIN and an FSSAI licence, and neither list means anything in the other country.
So the forms ask for the registrations you actually hold. Phone numbers validate against the length your country really uses. The working day for daily closing follows your local midnight, not a server's. It is unglamorous work, and it is the difference between software that fits and software you fight.
Built for groups from the start
Branch-to-branch requests, transfers signed at both ends, permissions scoped per branch, and figures that roll up to the group and drill down to one kitchen.
Made for phones, not just desks
Receiving, counting, transferring and approving all work on an Android or iOS phone — and keep working when the signal does not.
Who it is for
Owners and operators who are tired of guessing
Restaurant groups
Two branches or twenty, where stock moves between them and nobody is certain what arrived where.
Hotels with kitchens
Several outlets under one roof, one store, and a food cost that has to be defended to a head office.
Cloud kitchens
High volume, thin margins, and no room for a rate that drifted upwards three months ago.
Come and argue with us about your numbers
Bring one branch's purchase figures to a half-hour call. If we cannot show you something you did not already know, we will say so.