PAI SUPPLIER OPERATIONS • CONTROLLED REVIEW
Category Approval Workflow PHASE 9 • PROPOSALS ONLY
Persistent review queue, explicit human decisions, and a server-generated audit history.
STRICT PRODUCT SAFETY LOCK: Phase 9 can write only its two isolated review tables in Supabase. Approve proposal means approve a review proposal for later consideration only. It DOES NOT change
supplier_products.main_category, pricing, images, stock, DRAFT status, or publication. No bulk category application is enabled.Administrator sign in
Sign in once through the Supplier Command Center or use the existing administrator password here. Supabase administrator permission is checked before access.
PAI catalog products—
Uncategorized products—
Persistent review queue0
Proposal approvals only0
1. Find PAI products requiring review
Read live uncategorized records and queue candidates. Only review records are saved to Supabase.
| PAI SKU | Product | Current category | Rule suggestion | Confidence | Explanation | Add to review queue |
|---|
2. Persistent manual-review queue
Save proposed categories, notes and workflow decisions; the product catalog is never updated.
| PAI SKU & product | Suggested | Proposed category | Review status | Reviewer notes | Save / approve proposal only |
|---|
Manual approval process: First choose a category and save the review. Mark it Ready for approval. Then use Approve proposal only and type the exact SKU to confirm. This creates an audit event but never writes the approved category to a product.
3. Immutable audit history
New review and update events are recorded by a database trigger, with actor, timestamp and before/after values. Reviewers cannot edit or delete audit entries.
| Date & time | SKU | Event | Previous status | Next status | Proposed category | Actor ID |
|---|