Begin with the stock unit
A business may buy milk by the litre and use it by the millilitre, or buy a pack and sell individual pieces. Define stock units and pack quantities before entering recipes or relying on cost reports. CreekPOS supports explicit conversions for compatible units; a custom label does not automatically create a conversion. Test the smallest normal transaction and compare it with the physical quantity used.
Make recipe cost visible
For products made from ingredients, the recipe defines quantities and yield. The product’s recipe cost is calculated from those ingredients, and chosen modifiers can change the cost of a sale line. This gives a more useful margin picture than a single guessed cost for every size. Supplier cost data still needs to be maintained; the software cannot infer an unrecorded price change.
Separate preparation from sales
A prepared sauce kept in stock should be created through a preparation batch. Ingredients decrease, prepared stock increases, and later sales consume the prepared item. An unstocked recipe component can instead expand into its ingredients at sale time. Choose the model that matches what staff actually count. Do not enter both approaches for the same physical use or the stock picture becomes misleading.
Treat waste as its own workflow
Write-offs can record spoiled, dropped or expired items with quantities and notes. Reviewing waste by product and reason is more informative than watching a single stock adjustment total. Keep the workflow simple enough that staff will use it during a shift, and decide who may record and review changes through the available roles and permissions.
Close the loop with a stock-take
An ingredient-usage report explains theoretical consumption from recorded movements. A physical count helps reveal the difference between the theory and the shelf. Investigate units, recipe yields, preparation records and missing purchases before drawing conclusions. Food-cost and waste reports then help decide which recipes or working practices deserve attention.
Choose the edition by workflow
Online and Desktop are different products with their own plans, capabilities and checkout routes. These recipe and stock concepts are shared where the relevant features are supported, but not every workflow or integration belongs to every plan. Use the current edition’s feature list and test the actual devices you intend to use. For Online onboarding, start with Show me around and then the setup checklist; the tour does not create sales or modify stock.
Written by the product team from current product documentation. Features vary by edition, enabled modules and plan.