A bill of materials maps the prepared item to tracked or intentionally untracked components.
Build the bill of materials behind the menu item
Map a prepared product to the components and quantities used to make it. The recipe turns a finished menu choice into a repeatable inventory instruction while letting non-stocked components remain untracked where that operating model is intentional.
Deplete configured ingredients when the item sells
Sale-time depletion applies the configured component quantities when the prepared item completes. Fractional quantities let the record represent partial units instead of rounding every ingredient into a whole retail item.
See which ingredient limits the next serving
At-risk and estimated-servings signals can surface the component creating the tightest bottleneck. That gives the operator a practical reason to count, receive, or purchase before the menu item becomes unexpectedly unavailable.
Connect ingredients to the broader stock workflow
Physical counts, adjustments, suppliers, purchase orders, partial receiving, low-stock visibility, and transfers provide the operating path around the recipe. The recipe and the ingredient record remain part of the same inventory system.
Prove the recipe with real yield and units
Build representative menu items, verify component units and quantities, complete sample sales, and compare expected sale-time depletion with a physical count. That acceptance work makes the recipe useful to the business instead of merely complete on screen.
Prove one recipe from configuration to physical count
Map a representative prepared item to measured components, complete sample sales, inspect sale-time depletion and the at-risk serving signal, then compare expected quantities with a physical count. Include one untracked component and one fractional unit so the team can explain both.
Inspect in the live demo
Build a representative recipe, complete a safe sale, and inspect the resulting component inventory. Availability can depend on enabled modules, hardware, payment setup, role, location, and rollout configuration.
Move from the feature to the operation
This capability shares customer, employee, product, location, transaction, and reporting context with the rest of LiftedPOS. The value is not a checked box. It is the handoff the operation no longer has to rebuild.