Packing a Flightcase

Fill a flightcase from its checklist, resolve pack conflicts, seal it, and rebuild it as returned assets arrive.

Pack the contents#

1. Open the flightcase and choose Pack items, or go to /flightcases/{flightcase}/pack.
2. Confirm Pack — {name}, the case, and the warehouse identify the case in front of you.
3. Scan or type an asset number into Scan asset into case, then press Enter.
4. Follow Template checklist when it is present. A scan can fill a matching later slot; it does not have to match Next expected.
5. For an empty checklist slot, choose Fill by pick and select one of the Available assets if scanning is not practical.
6. Use Remove to unpack a wrong item before sealing.

The pick list shows up to 25 serviceable, unpacked assets for that catalogue item at the case's warehouse. If the case has no template, the page shows Packed items and accepts scanned assets without a checklist.

Make the physical contents match the page before sealing. Sealing locks the pack and is a dispatch prerequisite; in strict mode, Seal flightcase is not offered until the compliance checklist passes.

Resolve a rejected pack#

1. If no barcoded asset matches, correct the value shown under Scan asset into case and scan again.
2. If a conflict panel opens, read its heading and details before choosing anything.
3. When the item is in another case, choose Move item from current flightcase to this flightcase only when the physical item is also being moved.
4. When an item is still checked out, use Return item from rental and pack into flightcase only if that resolution is offered and the return is real.
5. For a nested flightcase, use Confirm packing this flightcase inside the target flightcase only after checking the displayed nesting details.
6. Choose Set item aside when the conflict should not be resolved at the packing bench.

Only the resolutions available to you are rendered. A different warehouse, non-barcoded stock, an unavailable item, or excessive nesting depth can reject packing without an override action.

Seal the flightcase#

1. Check Pack progress and the count under Assets packed.
2. In a template case, confirm every required slot is filled and review any item marked Not on template.
3. Choose Seal flightcase from the Ready to seal panel.
4. Wait for the flightcase detail page to open.

The seal action is only shown when the case contains at least one active item, you can seal it, and any strict checklist is compliant.

Repack returned assets#

1. Open Repack on return for the flightcase and rental at /flightcases/{flightcase}/repack/{rental}.
2. Compare Outstanding on rental with Rebuilt flightcase.
3. Scan an Asset number, serial, or ID…, then choose Return & repack.
4. Leave Free scan (pack unexpected items) clear when only expected returned assets should be accepted. Select it only when the unexpected asset should genuinely join the case.
5. In strict mode, work through the required-versus-actual slot counts.
6. Choose Seal flightcase when it becomes available.

Return & repack performs both parts of the operation: it returns the asset from the selected rental and packs it into the case.

Understand dispatch and transfer effects#

Packing changes which assets belong to the case. Dispatching the case is a separate action and requires the case to be sealed.

The pack conflict action labelled Move item from current flightcase to this flightcase transfers membership between cases; it is not a warehouse transfer. If stock must move between warehouses, use a warehouse transfer instead. Transport flightcases configured to dissolve on dispatch release their contents into the dispatch workflow, while kit flightcases travel as a sealed unit.

Related#