Cafes, bakeries and patisseries live and die by two numbers that stock ERPNext never quite connects: the true cost of a croissant once you account for flour, butter, labour and yield loss, and the speed of the person at the counter during the morning rush. Out of the box, ERPNext gives you a BOM engine built for discrete manufacturing and a generic Point of Sale profile, but nothing that treats a recipe as a sellable menu item, expands a modifier into ingredient consumption, or reconciles the day's production against actual counter sales and wastage. Teams end up costing recipes in spreadsheets and re-keying sales, which is exactly where margin visibility disappears.

We build a proper Frappe app — installed into your bench as its own module, versioned in git, never a pile of manual customizations in the Customize Form UI. At its core are new DocTypes for Recipe (linking a menu item to a costed BOM with yield and portion factors), Production Plan Entry for daily batch baking, and Wastage Entry for spoilage and trim. A whitelisted server-side method drives the counter screen: a fast quick-sale POS built on the Frappe REST API that resolves modifiers and combos (extra shot, oat milk, meal deal) into the correct item and ingredient consumption at the moment of sale. hooks.py doc events keep costing honest — when a Purchase Receipt updates an ingredient's valuation rate, the linked recipe costs recompute; when a POS invoice is submitted, on_submit posts the stock movement and flags variance against the day's production plan.

Technically it stays inside ERPNext's grain rather than fighting it. Recipe costs roll up through native BOM valuation so your COGS and gross-margin reports stay accurate. Modifier and combo logic is implemented as client scripts on the POS interface plus server scripts for the pricing rules, so it survives upgrades. A scheduler event runs the nightly close — reconciling produced vs. sold vs. wasted quantities and writing a batch yield summary you can report on. Role profiles and permission rules separate the counter cashier, the production baker and the store manager, so a barista can ring a sale but only a manager can adjust a recipe or write off wastage. Everything targets Frappe/ERPNext v15 and v16.

Because this is build-to-order, you are not downloading a frozen marketplace app and hoping it fits. We start with a short scoping call, confirm your menu structure, modifier rules and reporting needs, then build against your exact requirements. Typical delivery is one working week from confirmed scope. We install and configure it on a staging site first, run UAT with your data, then deploy to production with a rollback plan, hand over the git repository, and stay with you through a post-go-live support window.