Recipes and ingredient consumption
Each item knows what goes into it. Production draws down flour, sugar, ghee and the rest, so cost per kilo comes from your own purchases instead of an estimate.
Sweets by the kilo, cakes ordered three days ahead, and a batch of ingredients that has to account for both. Codipy POS bills by weight, takes advance orders, and pulls the flour and sugar out of stock through the recipe.
A bakery runs two businesses at one counter. The front is fast retail — mithai by the kilo, biscuits by the piece, everything fresh and everything perishable. The back is production, where ingredients turn into stock overnight and nobody can quite say what a kilo of barfi actually cost to make.
Codipy POS connects the two. Recipes take the ingredients out of inventory when the item is made or sold, so your cost per kilo is a figure rather than a feeling. Weight billing handles the counter, expiry handles what does not survive the day, and advance orders make sure the cake ordered on Tuesday is made for Friday and paid for correctly.
Choose this business type during setup and these are the modules Codipy switches on for you.
Each item knows what goes into it. Production draws down flour, sugar, ghee and the rest, so cost per kilo comes from your own purchases instead of an estimate.
Sell by the kilo, the half or the pound. Scale labels scan straight onto the bill, and the price follows the weight without arithmetic at the counter.
Perishables carry dates and alerts, so what has to go today is discounted this morning rather than binned tonight.
A cake ordered for Friday is recorded with its date, its advance payment and the balance due on collection — not on a slip of paper by the till.
Orders carry their type, so the birthday cake delivered across town and the box bought at the counter can be told apart in the report.
Price a wedding order formally, hand it over, and convert it to a bill when it is accepted, without retyping a single line.

Make the day's batch. The recipe takes the ingredients out of stock, so the shelf and the store agree.
Weigh, scan the label, bill. Half a kilo of gulab jamun takes as long as a single biscuit.
Take the cake order with its collection date and advance. The balance is due when it is picked up, and the system remembers which is which.
Check the fresh-item list. What has to move today gets a discount while there are still customers.
Day Close with sales by item and by channel, ingredients consumed, and the day's profit against what production actually cost.
Yes, if the item has a recipe. Production consumes the listed ingredients at the price you actually paid for them, so cost per kilo is calculated from your own purchase records.
Yes — kilogram, pound, half and piece are all supported, and a scale that prints barcode labels can be scanned straight onto the bill.
As an order with a collection date and an advance payment. The balance is recorded as due on collection, so the amount taken up front is never double-counted as the sale.
They carry expiry dates and appear on the alert list, which is meant to be read in the afternoon while a discount can still shift them.
Yes. Raise it as a quotation, hand it over, and convert it into the invoice when accepted — the prices cannot drift between the two.
Same installer, a different set of modules.