Flightcases & Kits

Barcoded flightcase pack/seal/dispatch/return lifecycle and warehouse UI.

Overview#

Flightcases group barcoded assets into dispatchable units — lighting kits, road cases, hybrid kits, and transport boxes. The lifecycle covers configuration, pack/unpack, seal/unseal, dissolve, dispatch, return, and repack.

Warehouse UI routes:

CatalogueItem-level flightcase templates configure default pack lists and policies at /catalogue-items/{catalogue_item} (flightcase config tab) and via GET/PUT /api/v1/catalogue_items/{catalogue_item}/flightcase_template.

Flightcase modes#

Lifecycle#

open → sealed → dispatched → returned → (repack) → open

Temporary flightcases can be created ad hoc for one-off jobs (POST /api/v1/flightcases/temporary).

Compliance manifest#

Sealed flightcases carry a compliance manifest listing packed serial numbers. Retrieve via GET /api/v1/flightcases/{flightcase}/compliance.

Dissolve-on-dispatch#

Transport flightcases configured for dissolve-on-dispatch unpack their contents into the dispatch workflow automatically — the flightcase record completes while assets move to the rental.

Repack-on-return#

After kit return, repack-on-return lets operators scan items back into the flightcase (POST /api/v1/flightcases/repack/start and per-item repack). UI trigger at /flightcases/{flightcase}/repack/{rental}.

Plugin and webhook seams#

Flightcase pack, seal, dissolve, dispatch, return, and repack events appear in the webhook catalogue for integrations (barcode scanners, WMS, etc.).

Using it in the app#

Navigation#

CatalogueItem flightcase config tab#

Tab: Flightcase Config (barcoded catalogue items only)

Save Flightcase Config requires flightcases.manage_templates. Without it the form is view-only with a warning banner.

Flightcases index#

Scan barcode field resolves an existing flightcase or housing — may navigate to show, open pack, or start repack.

Filters: search, warehouse, mode chips (Transport / Kit / Hybrid), status chips (defaults to Active)

Table: Barcode, Name, Status, Mode, Warehouse, Type (Temporary / CatalogueItem-backed), Items

Scan-create and repack-from-return flows require flightcases.create and rentals.edit respectively.

Pack page#

Route: /flightcases/{flightcase}/pack

Scan-to-pack workflow while the flightcase is open:

• Strict checklist vs free list scan modes (configured on the flightcase)
• Inline conflict dialog when a scan hits an asset already elsewhere — options include transfer, auto-return, and nesting resolution
• Seal when packing is complete

Flightcase show#

Actions (each policy-gated): Pack items, Repack session, Seal, Dissolve, Unseal (requires reason), Dispatch (kit/transport), Return kit, Verify check-in, Flag damage on return, Transfer items, Save scan mode

Panels: barcode, status, mode, check-in mode, scan mode, warehouse, contents tree, audit timeline

Flag damage on return: after kit return, a Flag damage on return panel lists returned assets. Flagging an asset repairs it (reason: Damage) and holds it out of availability. Contents still packed in the kit remain reserved until unpacked; the conflict policy rejects flagging still-packed components.

Dissolve-on-dispatch: transport flightcases configured for this mode dissolve automatically when dispatched from a rental — contents move to the dispatch workflow; the flightcase record completes.

Seal / unseal: sealed flightcases carry a compliance manifest; unseal prompts for a reason.

Flightcase contents overrun scan#

The scheduled command signals:scan-flightcase-overruns (daily) detects still-packed sub-hired contents past their virtual-stock return deadline. It is notification-only — it fires a manager notification once per membership via the contents_overrun_notified_at marker and never mutates stock or raises repairs.

Repack-on-return#

Route: /flightcases/{flightcase}/repack/{rental}

Editable scan mode after kit return — scan items back into the flightcase with lineage preserved. Also reachable from the index scan box ("start repack from return" modal).

Rental Assets tab#

Route: /rentals/{id}/assets (visible for Order or Quote+Reserved)

Sub-tabs: Functions, Allocate, Prepare, Book out, Check in

Set flightcase (bulk Functions menu) assigns flightcases to rental lines. Dispatch and return reuse the same flightcase policies as standalone flightcase pages (flightcases.dispatch, flightcases.return, plus rentals.edit).

Permissions summary#

Related documentation#

• Flightcases API — full REST lifecycle
• Assets — barcoded asset inventory
• Rentals — dispatch and return on order lines