PO system — Ledger light · all 7 screens (final package)
sticky PO system · Ledger · light Hard Stop · all 7 screens Direction 2 base · no dark strip · supplier-batch operating model · round 3 · Sep 11 · design only, no production code
Global queue → supplier order batches. Wanda headline: when the PO is needed, products, units, cash, revenue at risk. “Draft Wanda PO” pulls all 6 eligible lines. Next-due supplier (Meilin, Sep 18) sits quiet below.
One line’s why: p10–p90 band drawn, stockout window shaded, committed vs inbound split, cost of one week’s delay. Actions: keep in batch / override / remove — all with reasons.
Supplier-level order. Per-line remove/adjust with reason (one line dropped, restorable). Send-ready block: contact, payment terms, FOB, destination, attachments — missing fields block submit.
Independent approver, $3,744 commitment point (amber = real approval state). Payload hash, budget check, MOQ exception surfaced. Approval starts supply counting.
One PO, one clock. Square lifecycle markers — lime = verified milestones. Missed milestone shifts every downstream ETA.
3,596 of 3,848 received. The 252-unit shortage takes an explicit disposition: back-order / cancel remainder / dispute. Nothing written off silently.
One PO, one set of numbers: 3,596 + 240 = 3,836 received, −12 damaged credited $15.00, Amazon ledger check-in matches (lime = verified endpoint). Close locks the record.
Specimen: Wanda - RAVE, run #244 (Sep 8). Every number reconciles across screens: worklist 6 lines · 4,104 u · $3,936 · $2,266/wk → draft drops 1 line with reason → 5 lines · 3,848 u · $3,744 → received 3,596 + 240 = 3,836 · 12 damaged = $15.00 credit · ledger verified 3,836. Meilin - CHARMS (Sep 18) is specimen data demonstrating the cross-supplier queue. Repo record: docs/design/po/round3/.