# Yield Production
Yield Production is used when you produce items in **batches** (e.g., baking, commissary, central kitchen).
Clibase helps you:
* **Deduct ingredients automatically** (based on your recipe)
* **Add finished products to inventory** (based on actual output)
* **Compute Yield % and Variance** (shortage/excess vs expected)
{% stepper %}
{% step %}
### Step 1: One-time Setup (Create your Batch Production Template)
You only do this once per batch recipe (and update only when your recipe changes).
#### A) Add Ingredients (Recipe Components)
Go to your **Batch Production Item** (example: *Bread Production Set 1*) and add all ingredients used per batch.
For each ingredient, you will set:
* **Recipe Unit** (the unit you measure with)
* **Usage per 1 Production** (how much is used per batch)
Example ingredients in Bread Production Set 1:
* Blend – Pan De Sal (1 pack)
* Palm Oil (0.75 liter)
* Flour (0.625 kilogram)
* Water (250 milliliter)
Important note (to keep costing accurate)
Make sure your ingredient’s **Purchase Unit / Pack Size** and **Price** are correct.\
If units are wrong (ex: “1 milliliter” pack) your cost will also be wrong.
#### B) Set Expected Outputs (Standard Yield Output Items)
In the same Batch Production Item, add the products that should come out from this batch.
For each output item, set:
* **Item Unit** (ex: Piece)
* **Quantity per 1 Production** (expected output per batch)
Example outputs in Bread Production Set 1:
* Pan De Sal = **100 pcs**
* Choco Lanay = **200 pcs**
So, your **Expected Yield per batch** is:\
100 + 200 = **300 pcs**
{% endstep %}
{% step %}
### Step 2: Daily Encoding (Record Actual Production)
Do this every time you produce the batch.
#### A) Create a Production Entry
Go to **Yield Production** (Daily Encoding screen), then fill in:
* Production Date / Time
* Select your production template: **Bread Production Set 1**
* Set **Production Count**
Production Count = how many times you ran the batch
* If you baked it once: **1**
* If you baked it twice: **2** (expected outputs double)
#### B) Enter Actual Yield per Item
Under the output items, encode the **Actual Yield Qty**.
Example (Actual output today):
* Pan De Sal = 100
* Choco Lanay = 150
Clibase will automatically compute:
* **Expected Yield**
* **Actual Yield**
* **Yield %**
* **Variance Qty and Variance %**
{% endstep %}
{% endstepper %}
**How Clibase Computes Yield and Variance (Simple)**
Using the example above:
* Expected Yield = 300 pcs
* Actual Yield = 100 + 150 = 250 pcs
Yield % = 250 ÷ 300 = **83.33%**\
Variance Qty = 250 − 300 = **−50 pcs**\
Variance % = 50 ÷ 300 = **16.67%**
Meaning: you were short by **50 pcs** compared to the standard batch output.
**What happens to Inventory?**
When you save a Yield Production entry:
1. **Ingredients are deducted** based on your recipe × production count
2. **Finished products are added** based on the actual yields you entered
3. **Variance is recorded** to help you track loss/wastage differences
**Common Questions**
Q1: “What is Production Count?”
A: Production Count is how many times you ran the standard batch. If your template is for 1 batch, and you baked it twice, set Production Count = 2.
Q2: “Why is Expected Yield auto-filled?”
A: Expected Yield comes from your “Standard Yield Output Items.” The system uses it as the benchmark to compute yield % and variance.
Q3: “Do we need to encode all output items?”
A: Yes. If you leave an item blank/zero, it will reduce Actual Yield and increase negative variance—meaning the report will reflect shortage.
Q4: “Our costs are wrong—why is ingredient cost too high?”
A: Most of the time it’s a **unit/pack setup issue**:
* Purchase Pack set incorrectly (e.g., 1 ml instead of 1 gallon/1 container)
* Recipe Unit mismatch (liter vs ml, kg vs grams)
* Purchase price not updated (still 0 or outdated)
Q5: “If actual production uses more/less ingredients than standard, what should we do?”
A: Update the recipe components to match real-life usage as your “standard,” so future deductions and costing are closer to reality. Variance should represent exceptions, not normal behavior.
Q6: “What if my batch recipe changes?”
A: Update your **ingredients usage** or **expected outputs** inside the Batch Production Item so future records remain accurate.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://ems-admin-portal.clibase.tech/inventory-management/yield-production.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.