--- title: Record production output summary: > Recording output books a finished batch in against its production run. Open the run, enter the date and how many units arrived in this delivery, then confirm the material that batch consumed. Finished units go on stock, and the inputs come off where they physically sit — at the partner for an outsourced run. Partial deliveries are normal; record each one as it lands. type: task group: make step: 4 permission: production.labour prerequisites: [] related: - /help/store/what-each-location-type-can-do - /help/receive/receive-a-delivery - /help/receive/cost-a-receiving last_updated: 2026-08-07 --- **A production run is an order you place on a factory floor instead of a supplier.** Raw material goes in at one end and a different product comes out at the other. Recording output is the moment you tell Mossery that some of that finished product actually exists. Until you do, the run says goods are being made and your stock says nothing has been made. Both are true, and recording the batch closes the gap. This page covers: - [Where the material actually sits](#where-the-material-actually-sits) - [Before you start](#before-you-start) - [Book the batch in](#book-the-batch-in) - [Book it in from your phone](#book-it-in-from-your-phone) - [Short over and mis-keyed deliveries](#short-over-and-mis-keyed-deliveries) ## Where the material actually sits This is the part that surprises people, so it comes first. A **production partner** — an outside press, printer or converter — is a location, exactly like a warehouse is a location. It holds stock. Your stock. So when you send 500 sheets out to be printed, nothing is consumed. The sheets **move**. They leave your warehouse and arrive at the partner, as an ordinary transfer with two ledger entries, and they sit on the partner's shelf on your books where you can count them, value them and reconcile them. The material is consumed later, when the finished goods come back. That timing is not an accident: - The material does not come back as itself. Sheets go out; printed covers come in. There is no return delivery to cancel the outbound one against, so the balance at the partner has to be cleared by something. - Consuming at dispatch would claim the sheets ceased to exist the moment they left your loading bay, while they were sitting on somebody's floor a few kilometres away. - Suppliers often deliver raw material **straight to the partner**, never touching your warehouse at all. That delivery is received at the partner, and the same rule then applies. Two consequences follow. A run cannot dispatch material until it knows which partner it is going to, because a transfer needs a destination. And the moment you record output is also the moment the partner's material balance comes down. A run made in-house works the same way, minus the transfer. The material is consumed at your own location, when the output is recorded. ## Before you start Recording output posts real stock, so bring real numbers. You need: - The run, findable by its reference on the **Production orders** list. - The date the goods landed. - A physical count of the finished units in **this** delivery. Not the run total, and not what was ordered. - Roughly what the batch consumed, if you want to override the suggestion. The run also has to be at a stage where a receipt makes sense. A draft has to be confirmed first. A run already in costing or closed has its quantities locked — reopen it if goods still need booking in. A run typically moves: draft, confirmed, in production, goods ready, received, costing, closed. Goods ready is a signal, not a gate. Batches land whenever the manufacturer ships, so you can record output before anyone marks the run ready. ## Book the batch in On a computer, on the run's own page: 1. Click **Receive batch**. On a run that already has a delivery against it, the panel opens as **Receive another batch** and tells you how many units are already booked in. 2. Set the **received date**. It defaults to today and cannot be in the future. 3. Enter the **quantity in this delivery**. It pre-fills with what is still outstanding, which is usually right, but count first and trust the count. The variance against what was outstanding is shown as you type. 4. Read the **material consumed** panel. It names the location the material is coming off — the partner for an outsourced run — and lists each input with a suggested quantity. 5. Adjust any line that is wrong, then submit. The suggested quantities come from the product's production recipe, scaled by the quantity you actually received rather than the quantity that was planned. Yields miss their target all the time, and consuming against a plan the floor never hit would quietly overstate what the batch used. Each suggestion is also capped at what is physically at that location, so it never proposes consuming material that is not there. Two lines behave differently on purpose: - **Services** never appear. A service holds no stock, so there is no balance to draw down. - **A line with nothing behind it** suggests zero rather than a negative. If material was already consumed some other way, the panel shows that honestly instead of pushing a location below zero. The moment you submit: - A permanent ledger entry adds the finished units at the run's own location, and the stock snapshot follows. - One ledger entry per input takes the material off at the consuming location. - The delivery is recorded as its own batch, and the run's received total is recalculated from every live batch rather than nudged upward. - The run becomes **received**, or **partially received** if the target has not been met yet. Costing is deliberately not part of this. What the batch cost in MYR is reviewed in a separate step afterwards, so a delivery is never held up waiting on an invoice. ## Book it in from your phone Warehouse staff can book a run in from the floor. It is one screen. Open **Receive**. Runs with goods still to come sit in the **To receive** list, alongside purchase orders — from the floor, a pallet is a pallet, and an outsourced run's finished goods are on no purchase order at all. Tap the run. Then: 1. Check the header: the product, the partner, and how many units are still outstanding. 2. Set the quantity that arrived. It pre-fills with what is outstanding. 3. Check the date. Add a note if something needs saying. 4. Submit. The phone screen never asks about material consumption, and that is on purpose. How much paper a batch ate is a judgement made against the recipe, and guessing it at the door would deduct real stock on a guess. Booking the goods in is the urgent half; the material side is picked up on a computer afterwards. Submit once. If it feels slow, wait rather than tapping again. ## Short over and mis-keyed deliveries Record what arrived. Never round to what was ordered. - **Short.** Enter the smaller number. The run goes to partially received and keeps the balance outstanding. It does not close itself — someone ends the run explicitly when nothing more is coming. - **Over.** Enter the larger number. Over-delivery is allowed, because refusing it would leave real units off the books. - **Another batch later.** Just record it. Each batch consumes its own share of material and adds to the run's totals rather than replacing them. - **Mis-keyed.** Do not book a correcting delivery on top, and do not adjust stock to compensate. Reverse the receipt and record it again. Both entries stay in the ledger and the story stays readable. If the material panel offered less than you know the batch used, the difference is recorded in the ledger note rather than silently swallowed. That is worth following up: it usually means the partner's balance is out of date, and a stock count at that location is the fix. ## Explore **What each kind of location can do.** A production partner holds your stock but is never sold from and never synced to a storefront. [Learn more →](/help/store/what-each-location-type-can-do) **Recording a supplier delivery.** The same posture, for goods arriving against a purchase order rather than a run. [Learn more →](/help/receive/receive-a-delivery) **Costing what arrived.** The separate step that turns a booked-in batch into a unit cost. [Learn more →](/help/receive/cost-a-receiving)