Getting Started
Your first batch
Producing your first batch end to end: starting it, working the floor, recording output, and releasing finished goods.
A batch is one production run of a product, recorded against an approved recipe. Producing your first batch is where Crown's pieces come together: the recipe you built drives the run, the ingredient lots you received get consumed, and the finished goods you make come out the other end with a complete traceability record. This article walks the whole loop at a high level and points you to the detailed article for each step.
Before you start
Approve a recipe. You can only start a batch against a product that has an approved recipe version. If yours is still a draft, approve it first. See Your first recipe.
The production loop
- Start the batch
Open Batches, select New batch, and pick your product. Crown uses the product's latest approved recipe and opens the batch in progress. Full details in Starting a batch.
- Work the production floor
Complete each stage's items in order: select the ingredient lots you use, record measurements, mark tasks done. Crown stamps who recorded each step and when. See Recording production steps.
- Record your output
When every stage is done, select Enter yield & complete to record how much you produced and how many of each SKU you filled. Crown turns those counts into finished-good lots.
- Release the finished goods
Pass quality review and release the batch. Until you release, the finished goods are held back from inventory. See Releasing a batch.
A lighter option: quick batch
If you're logging a run that already happened, doing R&D, or reworking product, you can start a quick batch instead. It skips the stage-by-stage floor and captures the essentials (lots, any critical control point readings, packaging, and yield) on a single form. Full batches build the complete monitoring record and are the normal choice for routine production.
What's next
Start with Starting a batch, then follow the production loop through to Releasing a batch. If something goes off-spec along the way, see Logging a deviation.