Packing

Once garments are finished, someone has to put them in boxes, and someone has to know what went in which box. Packing is the last stage on the floor before dispatch.

Three pieces make it work: the Packing tab on a Production Order declares how the order should be boxed, the Packing App does the boxing, and the Packing Box rows record what actually happened.

Declaring how an order packs

Open a Production Order → Packing tab.

Pack Rule is the shape of a box:

Units per Box sets the count. Between the rule and the count, the app can work out — and show — exactly which boxes remain to be built.

Below sits Packed Boxes, the running record. You read it; the app writes it.

The Packing App

/garmentflow/packing, from the apps launcher. Four screens.

Packing (dashboard)

Every Production Order currently at the Packing operation, scoped to your unit, with four counters per order: Planned, At Packing, Packed, Remaining. Change unit from the header.

Close Session is here — see below.

Receive

Finished work doesn't appear at packing by itself. Receive lists batches waiting at the previous operation with the quantity available, and receiving posts a Handoff entry moving those pieces from wherever they are into Packing.

If nothing is listed, nothing has been handed off to you yet — the message says so plainly rather than showing an empty screen.

Order detail

Open an order and you get:

• The pack rule and units per box, editable here.
• Remaining by Variant × Size — a live matrix of what is planned, what is packed, and what is left.
• Plan Preview — the next boxes to build under the current rule, with the leftover that won't make a full box called out separately. That leftover is the number worth knowing before you start, not after.

Pack

The boxing screen. It proposes Next Box from the plan, you confirm or adjust the contents, and Close Box · Print Label commits it and prints.

A running Closed This Session counter sits alongside, so a packer can see their own shift's output. When the plan is exhausted the screen says Plan complete. No more full boxes to pack. rather than inviting another box.

The label is 100 × 75 mm and prints through the device's normal print dialog, so it works with an ordinary thermal printer driver — no special print server.

Closing the session

This is the part worth understanding, because it is where packing meets stock.

Closing a box does not post anything to the ledger. It writes a Packing Box row and nothing else. That is deliberate: a packer closes dozens of boxes an hour, and a ledger entry per box would bury the operation ledger in noise.

Close Session is what posts. It takes the day's boxes that haven't been synced yet, groups them per order and variant, and emits one End entry per variant — which in turn creates the stock entry for the Packing operation's materials.

So the rhythm is: pack all shift, close once at the end. If a session isn't closed, the boxes exist and the ledger doesn't know about them yet.

What a Packing Box records

Internal box number, external number, variant, total quantity, the size breakdown, who packed it and when, whether it has been synced to the ledger, and — once the goods ship — the Delivery Note and its sequence on that note.

Where packing shows up elsewhere

• Final quality checks happen before packing — see Final Quality Checks.
• Dispatch picks up from here — see Dispatch and Recovery.
• The Packing operation itself is an ordinary operation on the batch's route, so it appears in the Operation Ledger like any other.

What to do next

Read Dispatch and Recovery for what happens to a packed box, or Production reports for the counts.