Recipe stock versus prepared stock without double deduction

An ingredient recipe and a prepared product describe different inventory moments. A preparation batch consumes materials and creates prepared stock; selling that stock must not consume the same materials again. A small reconciled example is more useful than an attractive dashboard whose quantities cannot be explained.

Before using this with live customers

Start in a fictional training workspace with a small catalogue, named staff and known opening quantities. Decide what the operator should be able to do, which branch owns the work and which evidence will show that it succeeded. Check the installed edition and build before following a new control. A plan entitlement, a workspace switch and a staff permission are separate checks. Hiding a menu simplifies the view; it never grants permission to the underlying operation. Keep administrator credentials private and give each employee an account that matches their responsibilities.

A short, repeatable acceptance exercise

Write down the starting record and the expected result before making the change. Use one ordinary item and one edge case: a decimal quantity, a modifier, a discount, a missing cost or a long Arabic product name, depending on the task. Perform the action once, inspect its saved record, then reopen the screen in a separate session. Verify that the original identity and totals survived. If a button disappears, examine role, feature switches and branch scope before assuming that data has been lost. A fictional demonstration is evidence of that tested workflow, not of every possible customer configuration.

Online / SaaS

Recipe ingredients and prepared stock

Choose one fulfilment mode for each finished product: made to order or prepared stock. Do not configure the same sale to consume both finished stock and recipe ingredients.
For made-to-order products, enter ingredient quantities and compatible units. Selling the finished item deducts its configured ingredients; use the intended return/restock option when reversing a sale.
For prepared stock, record preparation first. The batch consumes raw ingredients and creates finished inventory. Selling then consumes the finished inventory, without another raw-material deduction.
Verify a demo example: prepare 10 kg, sell 2 kg and record 1 kg waste; 7 kg remains. Inspect the ingredient movements separately, then test a return and a recipe edit without rewriting historical consumption.

Open the edition manual

Products, variants, units and modifiers

Open Products with catalogue-management rights. Enter the complete product name and alternative-language name where needed.
Set barcode, category, selling price, cost where authorized, unit and stock-tracking behavior. A barcode must identify the intended sellable product.
For size/color products, configure variants and verify the exact sellable SKU. For food products, configure modifiers and distinguish ingredient-only products from products sold to customers.
Save and test a small sale in a demo. Confirm the displayed name, price, modifier text and stock effect. A weighing product requires the supported till/device path or explicit manual weight entry.

Open the edition manual

Classic Desktop / Windows

Recipe ingredients and prepared stock

Open the product and recipe/preparation settings actually available in your installation. Review ingredient quantities, units and the prepared-product setting.
Post a preparation batch once and verify the input and prepared-stock movements. Keep preparation separate from selling the prepared item.
Sell a small test quantity and inspect the resulting stock record. Do not deduct the same ingredients both at preparation and again at sale.
Use the online recipe guide for cloud recipe and production routes. Browser batch/audit screens are not native screens.

Open the edition manual

Classic Desktop exposes its native recipe and stock-preparation controls when enabled. Verify the fulfilment mode in that product’s editor. Online production add-ons and their browser order/quality screens are separate capabilities.

Products, variants, units and modifiers

Open Products and add or edit a product. Review its name, barcode, category, selling price, cost and unit.
For a weighed product, use the appropriate weight/unit settings and verify decimal quantities with a test sale.
Save and reopen the record, then verify the name and price shown by the sales screen.
Use the Products export action for CSV, Excel or JSON. Keep the original import template for imports; a display export is not a new import contract.

Open the edition manual

Classic Desktop has native product editors, import tools, variants and optional weighing controls. Use the local catalogue and verify a real sample barcode. A browser product screenshot is not the native product editor.

Review the evidence rather than the animation

A preview is not a posted movement, an accepted request is not provider settlement, and a queued message is not verified delivery. After a financial or inventory action, inspect the original receipt or movement before retrying. Keep the original request identity for an uncertain replay. Do not create a new sale merely because the first response was slow. For exports, compare the selected range and totals with the source report. For staff reports, distinguish an actual event from a missing timestamp. Do not turn missing data into zero seconds or a claim that an employee did no work.

Keep edition and external-service limits explicit

Classic Desktop, a cloud-connected till and the SaaS browser share concepts but do not expose every control in the same place. The sections below give separate procedures and explain real alternatives. Follow the manual for the edition you are actually using. Device compatibility still requires the exact model and protocol to be tested. External payment, accounting and dashboard services require their own account, authorization and configuration. This article does not promise a live delivery-platform integration, a new paid-plan inclusion, a hardware supply service or an approved wallet pass. Confirm those conditions separately before a customer commitment.