Your orders

3 in production · 1 shipment in transit · production photos are posted by the factory as your batches move through each stage.

Order	Product	Qty	Progress	Status	Est. delivery	Last update

YGMSB-260401 — production updates photos posted by CYTO-11 production team

Sachet packing started Production

Today 09:40 · posted by Sarah (Production)

FL-01 line running

sachet close-up

expiry print check

Blending complete — batch AMX-2604-01 Production

2026-07-05 16:05 · posted by Sarah (Production)

MX-01 blend

batch label

Materials received & verified

2026-07-01 11:20 · no photos

Order confirmed — 1,197 pcs

2026-04-01 · target delivery 2026-07-18

Order summary

Product: AlphaMax V+ 2024-04
Quantity: 1,197 pcs
Batch no.: AMX-2604-01
Est. delivery: 2026-07-18
Facility: CYTO-11 · GMP

Shipment (previous order)

YGMSB-260397 · GDEX GD8834712MY

In delivery — ETA 2026-07-08

Documents (CoA, halal cert, packing list with lot numbers) appear here on shipment — download, no email chasing.

Project Gaia — client portal mockup, Filament v3 idiom. No backend. Client sees status, photos, shipments and documents only — never costs, recipes, suppliers or other clients' orders.

Element	Implementation	Notes
Portal itself	Second Filament panel ('portal') with its own auth guard, tenant = Customer	complete isolation from the internal app panel; a client login can never reach internal routes
Client users	customer_users (customer_id FK, email, name)	invited from the internal Customer card; global scope customer_id on everything in the panel
Order progress	derived: simplified 6-step map of SO + MO + shipment states	Confirmed → Materials → Production → QC & packing → Shipped → Delivered; never exposes internal chips, costs or shortages
Production updates	production_updates (mo_id, stage, note, photos json, visible_to_client bool, posted_by, posted_at)	posted from the internal MO card (camera upload); only visible_to_client rows appear here; photos watermarked with timestamp + batch
Shipment tracking	reuses shipments + shipment_events	same data as internal Shipments screen, client-scoped
Documents	media attached to shipment/batch (CoA, halal cert, packing list)	download-only; lot numbers included — doubles as the client-facing GMP paper trail

Element

Implementation

Notes

Portal itself

Second Filament panel ('portal') with its own auth guard, tenant = Customer

complete isolation from the internal app panel; a client login can never reach internal routes

Client users

customer_users (customer_id FK, email, name)

invited from the internal Customer card; global scope customer_id on everything in the panel

Order progress

derived: simplified 6-step map of SO + MO + shipment states

Confirmed → Materials → Production → QC & packing → Shipped → Delivered; never exposes internal chips, costs or shortages

Production updates

production_updates (mo_id, stage, note, photos json, visible_to_client bool, posted_by, posted_at)

posted from the internal MO card (camera upload); only visible_to_client rows appear here; photos watermarked with timestamp + batch

Shipment tracking

reuses shipments + shipment_events

same data as internal Shipments screen, client-scoped

Documents

media attached to shipment/batch (CoA, halal cert, packing list)

download-only; lot numbers included — doubles as the client-facing GMP paper trail

Your orders

Order summary

Shipment (previous order)

Client portal — field manifest

Notes