🟡 The big wiring job for this form: the Coach Hub is read-only today — this would be its FIRST coach-side write. The pattern already exists on the OS (save-edit.js + append-only changelog); it needs an orders table + a save-order function + this page added to the Coach Hub template.

🟡 Setup mostly rides existing rails: config tables (catalog, prices, windows, medal decision) are the same RLS-locked-table + gated-function pattern as os_coaches_data — small builds. Publishing config = the same Supabase-push shape the Coach Hub already reads at login; only the form page needs a template edit + rainbow-trifle deploy.

⛔ Inventory is a new build — and the code is the easy half. The tables and ledger reuse existing patterns, but stock numbers are only as true as the counts: it needs Affinity 262 to confirm receipts and do periodic counts, or the shelf lies. Recommendation: launch ordering WITHOUT live inventory (orders flow anyway), add the shelf once Affinity agrees to the counting process.

🟡 Mostly wiring: the orders table is new but simple; the email to Affinity rides the accounting-submission Resend rail (built, not yet deployed). ⛔ The automatic status-back (reviewing → packing → shipped + tracking) needs the partner portal — interim: Affinity replies to the email and staff click the status forward.

🟡 Free ride: this whole view is a read over the orders table — it renders the moment the first order lands. Nothing else to build.

⛔ Doesn't exist today: OS auth is a staff-only allowlist (dashboard_users) — there's no partner role, and giving an outside company a login is a real security decision (scoping, what they can see, audit). Day-one alternative that works now: Affinity gets the order email and replies; staff advance the status. Build the portal only if volume justifies it.