Les détails du produit sont affichés en anglais. Traductions à venir.
Faits en bref
- Prix
- $349.00 USD
- Versions ERPNext
- —
- Temps d'installation
- 30 minutes
- Licence
- Perpétuel unique
- Langues
- 11 langues
Achat unique
Cafe / Bakery & Recipe POS for ERPNext
A build-to-order bakery and cafe POS for ERPNext that ties recipe-based BOM costing and daily production planning directly to fast counter billing. ECOSIRE scopes, builds, installs and supports it on your Frappe v15/v16 site.
$349.00USD
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Fonctionnalités clés
`Recipe` DocType linking each menu item to a costed ERPNext `BOM` with yield factor, portion size and sub-recipe support (e.g. a base dough used across products)
Recipe cost auto-recomputes via `hooks.py` doc events when an ingredient's valuation rate changes on `Purchase Receipt` or `Stock Reconciliation`
Fast counter quick-sale POS built on the Frappe REST API and whitelisted methods — keyboard/touch item grid, held orders, and sub-second invoice submission
Modifier support (extra shot, oat milk, syrup, size up) that resolves each modifier into the correct item price delta and ingredient consumption at sale time
Combo and meal-deal logic implemented as server scripts on Pricing Rule, so a bundle discount and its component stock movement are both correct
Daily `Production Plan Entry` DocType for batch baking — plan quantities, explode BOMs into a picking list, and post `Work Order` / `Manufacture` stock entries
`Wastage Entry` DocType for spoilage, trim and end-of-day write-offs, posting stock adjustments and feeding a wastage-cost report
Scheduler event runs a nightly close that reconciles produced vs. sold vs. wasted quantities and writes a per-batch yield variance summary
Real yield tracking — expected vs. actual output per batch, so a 5% dough loss shows up in unit cost instead of hiding in inventory shrinkage
Role profiles and permission rules separating cashier, production baker and store manager (ring sales vs. edit recipes vs. approve write-offs)
POS session close that ties out cash/card tenders to submitted invoices and flags variance before the session is closed
Ingredient-level stock deduction on every sale via `on_submit`, keeping ERPNext inventory live for reorder-level and low-stock alerts
Menu and price maintenance kept in ERPNext master data (Item, Item Price, Recipe) rather than a disconnected POS device, with client scripts for validation
Reports for recipe margin, best/worst-selling items by contribution, and daily production-to-sales reconciliation, buildable in the ERPNext Report Builder / Query Report
À propos de ce produit
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.
Pourquoi choisir Cafe / Bakery & Recipe POS for ERPNext
`Recipe` DocType linking each menu item to a costed ERPNext `BOM` with yield factor, portion size and sub-recipe support (e.g. a base dough used across products)
Recipe cost auto-recomputes via `hooks.py` doc events when an ingredient's valuation rate changes on `Purchase Receipt` or `Stock Reconciliation`
Fast counter quick-sale POS built on the Frappe REST API and whitelisted methods — keyboard/touch item grid, held orders, and sub-second invoice submission
Modifier support (extra shot, oat milk, syrup, size up) that resolves each modifier into the correct item price delta and ingredient consumption at sale time
Combo and meal-deal logic implemented as server scripts on Pricing Rule, so a bundle discount and its component stock movement are both correct
Daily `Production Plan Entry` DocType for batch baking — plan quantities, explode BOMs into a picking list, and post `Work Order` / `Manufacture` stock entries
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 2-4 weeks 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.
Ce que vous obtenez
- Installable source code for your version of the app, packaged as a proper Frappe app installable into your bench
- Installation and configuration on your ERPNext site, including DocTypes, role profiles, scheduler events and hooks wiring
- Technical documentation covering the DocType model, server/client scripts, whitelisted methods and hooks.py doc events
- End-user guide plus a live training session for cashiers, production staff and managers
- UAT on a staging site with your real menu and recipe data, sign-off, and a documented rollback plan before production cutover
- Post-go-live support window for bug fixes and configuration adjustments after launch
- Handover of the complete git repository with commit history so you (or any Frappe developer) can maintain and extend it
- Version compatibility validated against your Frappe/ERPNext release (v15 or v16)
Pour qui c'est
Multi-outlet cafe owner
Runs two or three cafes on ERPNext and needs recipe costing tied to counter sales so gross margin per drink is visible across outlets, not reconstructed in spreadsheets each month.
Production bakery manager
Plans daily batch baking and wants BOM-driven production plans, yield tracking and wastage write-offs that flow straight into ERPNext stock and costing instead of a separate production log.
Patisserie founder scaling operations
Already on ERPNext for accounting and inventory but stuck with generic POS; needs modifier and combo handling plus a fast counter screen that keeps ingredient stock and COGS accurate.
Finance lead / controller
Owns margin reporting and wants trustworthy recipe cost, wastage cost and production-to-sales reconciliation surfaced through ERPNext reports for real profitability analysis.
Aperçu de l'installation
Télécharger depuis ECOSIRE
Achetez la licence sur ecosire.com et téléchargez le ZIP de l'application Cafe / Bakery & Recipe POS for ERPNext depuis le tableau de bord de votre compte.
Ajoutez l'application à votre banc
Extrayez le ZIP dans le dossier d'applications de votre banc ou exécutez « bench get-app » avec le chemin d'accès à l'application extraite.
Installer sur votre site
Exécutez `bench --site SITE_NAME install-app APP_NAME` suivi de `bench migrate` pour installer Cafe / Bakery & Recipe POS for ERPNext et appliquer son schéma.
Activez votre licence
Ouvrez les paramètres de licence ECOSIRE sur votre site et activez votre clé de licence. Nécessite les applications gratuites ecosire_connect et ecosire_license_client.
Comment Cafe / Bakery & Recipe POS for ERPNext se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Recipe / menu costing | `Recipe` DocType linked to native BOM with yield and portion factors | Possible but you design the whole data model yourself | Often a fixed cost field, not true BOM roll-up | |
| Counter POS speed | Quick-sale screen tuned for rush hour via whitelisted methods | Depends entirely on your build effort | Generic POS, rarely tuned for cafe modifiers | |
| Modifiers & combos | Modifiers and combos resolve to items, prices and ingredient use | Buildable, significant scripting effort | Partial; combos often manual | |
| Production & yield tracking | Daily production plan + expected vs. actual yield reconciliation | You build the reconciliation logic | Usually absent in POS-only apps | |
| Wastage tracking | `Wastage Entry` DocType posting stock and cost | Custom DocType and scripts required | Rarely included | |
| Fit to your menu | Built to your exact recipes, modifiers and workflow | Fully bespoke but you own all decisions and risk | Fit to the app's assumptions, not yours | |
| Support & handover | Install, training, post-go-live support, full git handover | In-house or contractor; you carry maintenance | Vendor support tiers, limited customization | |
| Upgrade safety | Proper Frappe app in git, validated on v15/v16 | Risk depends on your engineering discipline | Depends on vendor's upgrade cadence |
Foire aux questions sur Cafe / Bakery & Recipe POS for ERPNext
+How long does delivery take?
This is build-to-order, not an instant download. After a scoping call to confirm your menu, modifier rules, production flow and reporting needs, typical delivery is 2-4 weeks from confirmed scope. We build on staging, run UAT with your data, then cut over to production with a rollback plan.
+Is this a ready-made Frappe Cloud Marketplace app I can install myself?
No. ECOSIRE builds it for you as a proper Frappe app tailored to your exact recipes and workflow, then installs it on your bench, configures it, trains your team, and supports it. You receive the full git repository at handover so any Frappe developer can maintain it.
+Which ERPNext versions are supported?
We build and validate against Frappe/ERPNext v15 and v16. We confirm your exact release during scoping and target the build to it so DocTypes, hooks, server scripts and the POS interface all work against your version.
+How does recipe costing stay accurate over time?
Each recipe links to a native ERPNext `BOM`, so costs roll up through standard valuation. `hooks.py` doc events recompute recipe cost when an ingredient's valuation rate changes (for example on a `Purchase Receipt`), and a scheduled nightly close reconciles produced vs. sold vs. wasted quantities so unit cost reflects real yield loss.
+How are ongoing support and updates handled?
Every build includes a post-go-live support window for bug fixes and configuration adjustments. Because the app is versioned in git and installed as a standard Frappe app, it upgrades cleanly with your bench; beyond the included window we offer ongoing support and enhancement retainers on request.
+Can it handle modifiers, combos and different portion sizes?
Yes. Modifiers (extra shot, milk swap, syrup, size up) resolve into the correct price delta and ingredient consumption at the moment of sale, and combos/meal deals are handled through server scripts on Pricing Rule so both the bundle discount and the component stock movements post correctly. Portion and yield factors are part of the `Recipe` DocType.
+Will it keep my inventory and accounting in sync?
Yes. Every counter sale deducts ingredient-level stock on invoice submit via `on_submit`, so ERPNext inventory, reorder-level alerts and COGS stay live. Wastage entries post stock adjustments, and the whole flow uses native ERPNext documents so your financial reports remain the single source of truth.
Demander un devis
Cafe / Bakery & Recipe POS for ERPNext
A build-to-order bakery and cafe POS for ERPNext that ties recipe-based BOM costing and daily production planning directly to fast counter billing. ECOSIRE scopes, builds, installs and supports it on your Frappe v15/v16 site.
- `Recipe` DocType linking each menu item to a costed ERPNext `BOM` with yield factor, portion size and sub-recipe support (e.g. a base dough used across products)
- Recipe cost auto-recomputes via `hooks.py` doc events when an ingredient's valuation rate changes on `Purchase Receipt` or `Stock Reconciliation`
- Fast counter quick-sale POS built on the Frappe REST API and whitelisted methods — keyboard/touch item grid, held orders, and sub-second invoice submission
- Modifier support (extra shot, oat milk, syrup, size up) that resolves each modifier into the correct item price delta and ingredient consumption at sale time