creekpos · SaaS / Online
Recipe ingredients and prepared stock · SaaS / Online
This guide uses fictional training data. Available controls depend on your enabled features, plan and permissions.
Prepared against the tested 13 October 2026 build; check your deployed build before following a new control.
Who can use this
Stock manager / cashier
Required tools
Recipes, preparation and stock. Requires the appropriate enabled features and entitlement; this guide does not add plan inclusions.
Before you begin
If a control is absent, check role, branch, enabled features and entitlement. If an order or price changed, refresh and review again. Do not repeat an uncertain financial action with a new request.
Steps
- 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.
Check the result
Review the saved record and its audit/stock/payment state before continuing. A preview, queued request or accepted send is not proof of completed delivery or settlement.
Edition differences and limits
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.