Their paperwork in,our work order out.
Lacrosse Unlimited uploads a QuickBooks PO, the client proofs, the production art and, when there is one, a number list. Every file is read live in this page. Nothing reaches Printavo until they have answered every open question and signed off on the work order in our format.
Files
Four uploads: the PO, a zip of client proofs, a zip of production art, and the number list when the order is personalized.
What we read
Every field, what their paper actually says, and what we take it to mean. Anything we had to guess becomes a question in step 3.
| Field | Your paperwork says | We read it as | Status |
|---|
Answer before we build
Closed questions only. LAXU picks an answer; nobody types "looks good". Each answer is written onto the work order in step 4.
Work order
The order exactly as Compound will enter it in Printavo: every line, every size, the client proof for each item, every number on the list.
Approve
Approval locks a fingerprinted copy of this work order and its files. That copy is what production runs from and what any reprint is checked against.
LAXU dashboard
What Lacrosse Unlimited sees when they log in: every PO they've sent, where it stands, and the full history behind it. The first row is the order in the desk above and updates live; the other rows are examples. On the server every line of the history is a row in the database that can't be edited or deleted.
Orders
| PO | Team | Submitted | Status | Open | In hands | Printavo |
|---|
History
In production this page reads the order database, and Printavo status is read back every 15 minutes. Exports to CSV, search by PO, team or item number, filters by status and date. Compound staff get the same pages plus an exceptions queue.
What can go wrong
Every way bad information could get from their paperwork onto a garment, checked against the two real samples: Erik's PO 69740-01 with its number list, and the all-products test PO TEHau-TEST-01 with its client proofs.
Build plan
Runs on Compound's own server, not Netlify: a Bun container on the AWS host, PostgreSQL on RDS for every order, answer, approval and event, and S3 with versioning and Object Lock for every file. Nightly off-site database dumps, a nightly export to Drive, and a PDF of every work order emailed to both sides, so nothing depends on one machine. Full spec: LAXU_THRONE_HQ/order-desk/SPEC.md.
flowchart LR A[LAXU uploads
PO + proofs zip + production art zip + number list] --> B[Two readers
PO template parser + Claude] B -->|readers disagree| Q B --> C[Rule check
catalog, size runs, proofs, roster, dates] C --> Q[Closed questions
to LAXU] Q --> D[Work order proof
in Compound format] D -->|request change| A D --> E[Approval
typed name + fingerprinted snapshot] E --> F{Staff gates
rush approval, price set, item mapped} F -->|held| S[One task to Stephanie or Max] F --> G[Printavo API v2
quoteCreate, line items, imprint, files] G --> H[Read back and compare
to the snapshot] H -->|mismatch| S H --> I[Status LAXU APPROVED
art spot-check task to Jordan or Josh]