Manufacturing orders

+ Manufacturing order

Open 4 Done

	Rank	Order #	Customer	Product	Category	Completed	Quantity	Planned time	Prod. deadline	Del. deadline	Ingredients	Production
	⠿					pcs	pcs	—
						0 pcs	24,720 pcs	Totals: completed / planned quantity (Sum summarizers)

Showing 1–4 of 4 open manufacturing orders

Per page

Project Gaia — static mockup in Filament v3 table idiom. No backend. Sample data: Katana tenant snapshot 2026-04-12, location 11, Balakong Jaya.

Manufacturing orders (Open) — field manifest

Field	Filament component	Type	Source	FK target
Rank	table()->reorderable('rank') + TextColumn (drag handle is Filament's)	integer	stored: manufacturing_orders.rank — manual scheduling priority, drag-to-reorder persists	—
ⓘ info icon column	— (dropped: unlabeled UI-only alert slot, empty in capture)	icon	derived: row-level alert badges	—
Checkbox	automatic with BulkActions (export / print / delete)	ui	UI-only bulk select	—
Order #	TextColumn::searchable(isIndividual: true)->url()	string	stored: MO number '<SO #> / <line>' — auto-generated per sales-order line	manufacturing_orders.id
Customer	TextColumn::searchable(isIndividual: true)->url()	string, nullable	derived: linked sales order → customer, rendered 'Name (SO #)'	sales_orders.id / contacts.id
Product	TextColumn::searchable(isIndividual: true)	string	derived: FK product variant, display 'name / variant'	variants.id
Category	TextColumn (badge-style) + SelectFilter	string	derived: item master category of the product	categories.id
Completed	TextColumn::numeric()->summarize(Sum)	qty + UoM	derived: Σ quantity actually produced on the MO so far	—
Quantity	TextColumn::numeric()->summarize(Sum)	qty + UoM	stored: planned MO quantity	—
Planned time	TextColumn::placeholder('—')	duration, nullable	derived: Σ planned routing-operation time; blank in all 4 captured rows	—
Prod. deadline	TextColumn::date()->color(fn red when at risk)	date	stored/derived per 'Configure deadlines' rule; red on 2026-03-26 / 04-06 / 04-08, black on 04-14	—
Del. deadline	TextColumn::date()->color(fn red when unmeetable)	date	derived: linked SO delivery deadline; red exactly when Ingredients Expected date falls after it	sales_orders.id
Ingredients	TextColumn::badge()->color(green \| amber)	status chip	derived: BOM availability rollup — 'In stock' or 'Expected <date>' from open supply	—
Production	SelectColumn (inline-editable badge)	enum	stored: MO status; Open tab shows 'Work in progress', Done lives under the Done tab	—

Engine notes

Totals: Completed = 0 pcs and Quantity = 24720 pcs — 24720 = 1197 + 16800 + 5917 + 806, live sum over filtered rows (Katana pins it on top; Filament uses a tfoot summarizer).
MO numbering is sales-order-driven: 'YGMSB-260401 / 1' and '/ 7' share the SO prefix — one MO per make-to-order SO line, suffix is the line number.
Ingredients chip is a BOM availability computation: green 'In stock' when all components allocatable now; otherwise 'Expected <date>' = date missing components arrive from open purchase/manufacturing supply (rows 2 and 3 share Expected 2026-05-09).
Del. deadline turns red exactly when the Ingredients Expected date (2026-05-09) is after the delivery deadline (2026-05-08); Prod. deadline reds follow the same risk logic.
Rank is a persisted manual priority used by the scheduling engine — drag handles reorder rows; material allocation is rank-ordered (rank 1 and 4 'In stock', rank 2 and 3 'Expected').
Completed vs Quantity is a progress pair: Completed accrues as production is recorded; the MO moves to the Done tab when finished.
List is location-scoped by the site dropdown — availability and schedule are computed per location.
'Configure deadlines' implies deadline fields come from a configurable rule (e.g. offset from delivery date).
Katana also offers this list as a calendar/timeline view (NEW toggle) — out of scope for the mockup.

Manufacturing orders

Deadline rules

Manufacturing orders (Open) — field manifest

Engine notes