FranchiseOS · Inventory & Stock
Stock that stays true across every branch
Stock is where multi-branch businesses lose money quietly. One outlet over-orders, another runs out mid-service, and nobody finds out until the month-end count.
Raw materials are tracked separately from what you sell. Recipes link the two, so selling a dish consumes its ingredients automatically and food cost is a live number rather than a monthly estimate.
Branches request stock from each other rather than ordering more, and a transfer adjusts stock on both sides in one movement.
Batch and expiry tracking work on a first-expiry-first-out basis, so the stock closest to expiring is consumed first.
What's included
Recipe Management
Raw materials, recipes and food cost.
Raw-material Batches (FEFO)
Batch/lot and expiry tracking on raw materials, first-expired-first-out issue order, expiry alerts and one-tap write-off of expired stock.
Expiry Tracking
Batch expiry alerts and write-offs on the legacy product-keyed path. Superseded by raw_material_batches; retire with it.
Inter-branch Requests
Request stock from another branch.
Transfer Auto Stock Adjust
Stock moves automatically on transfer send/receive. Org-wide because both ends of a transfer must agree.
Predictive Inventory
Auto-indent from forecast, dynamic par levels, exception dashboard, anomaly detection and vendor scorecards. Needs about a month of real consumption before its output means anything.
Ingredients and menu items are deliberately different things
Systems that treat a dish and its raw materials as one list break the moment a tomato is used in four dishes and also sold by weight. Keeping them separate — and linking them through recipes — is what makes accurate food costing possible at all.
In the product
Pending the theme redesign and a screenshot-safe demo org.
Questions
Does stock reduce automatically when we sell?
Yes, where a recipe exists. Selling the dish consumes the mapped ingredients at the mapped quantities.
Can one branch send stock to another?
Yes. A branch raises a request, the sending branch dispatches, and stock adjusts on both sides.
Does it handle expiry?
Yes — batch tracking with first-expiry-first-out consumption and expiry alerts.