G
Go Boy
FY2026/27
Financial year
Data will be compartmentalised by financial year (1 Jul – 30 Jun).
Notifications
Signed in
SKU is generated automatically. Lifetime quantity and last purchased date are calculated from the Raw Materials purchase log.
Code is generated automatically. Cost and stock come from the Packaging Purchase Log (or the Opening stock form for items you already hold) — the catalogue never asks for pricing.
A code is generated automatically. Currency, order quantities and exact prices are asked for later, when you log an actual order.
This logs to System Health so it isn't forgotten. Use it for things that look wrong but don't crash (e.g. a figure that seems off).
A pack code is generated automatically. After creating it, add the packaging assets (box, film, label, carton…) that make up one ${''}sale-format unit, each with a quantity. The total packaging cost is summed live from the packaging log.
Enter how many of this asset go into ONE single of the chosen level. The app multiplies up the hierarchy for you — so a component used once per pack automatically becomes packs-per-box × that for a box. You never type the box total yourself.
Packaging cost comes from the linked BOM pack code (shown above). Raw cost can be entered manually or pulled from a linked recipe.
Select the cook dates to compile. All cooks on those dates will print as A4 chef sheets in one document.
Labour splits across the batch's cooks by grams produced. "General" hours spread across all cooks that date.
| Employee | Hours | Rate ($/hr) | Cost |
|---|
This is the cost of one batch (tray). It applies to new production from today; past cooks keep their original cost.
Linking to a product type lets the Production Log auto-calculate raw cost for that product. Add ingredients after saving.
Cost pulls from the ingredient's latest price. Percentages are calculated automatically from quantities.
| Ingredient | Purchase format | Qty | Units inside each | Pack size | Metric | Total price (AUD) | Cost / unit | Stock units |
|---|
No production details yet — set up your first one to unlock product types.
No unit size for this type yet.
SKU is generated automatically. Product type and unit size come from Production Details. Use one SKU per sale format (e.g. a separate SKU for the wholesale carton vs the retail pack).
Add the same product type at different sizes as separate entries (e.g. Mud Cake Protein 15g and 30g). The Products page lets you pick the type, then the size.
These ingredients are at or below their reorder level. Arrange new stock before your next production run.
Quick count of what’s on hand — live lots only. Changed rows highlight yellow. For the full archive including exhausted lots, show all →
These appear as quick-pick chips when logging a rejection. Keep them short — 2 to 4 words.