BoxTrace Administration
System governance, product catalog, user permissions & audit logs
Database Persistence & Connection Mode
Database EngineOperating in self-contained offline memory store. Configured via .env.local.
LOCAL_STOREWarehouse Label Printing Specification
BoxTrace generates standard A4 vector printable PDF sheets designed for universal warehouse laser and thermal printers, specifically calibrated for Avery 3658 / Herma 4428 / 24-up label stock.
Sheet FormatA4 (210 × 297 mm)
Grid Layout3 cols × 8 rows (24/sheet)
Individual Label Size70 mm × 37 mm
Cutting Guidelines0.2pt Dashed Lines
QR Code Resolution & Numbering Rules
Identifier Format & Sequence
Every physical box is assigned a zero-padded 6-digit identifier: BOX-000001. In Supabase, sequential numbers are guaranteed gapless via atomic database sequence box_number_seq.
Direct QR Scan Destination
Scanning a QR code with any mobile camera, warehouse scanner, or the built-in scanner navigates directly to /box/BOX-XXXXXX without requiring intermediate manual lookups.
CommerceOps Migration Readiness
BoxTrace has been architected for instantaneous, zero-refactor migration as an internal module into the broader CommerceOps ecosystem:
Clean Domain Boundary
All business logic lives under src/lib/boxes, qr, permissions, and audit with zero circular dependencies.
Dual-Driver Persistence Layer
BoxService cleanly separates database calls from UI components, allowing drop-in connection to CommerceOps shared database.
Independent Schema & Sequence
The database migration creates self-contained tables and sequences that will not collide with CommerceOps core tables.
Role-Based Access Control State Machine
Pure TypeScript state machine (validateStatusTransition) maps cleanly onto CommerceOps unified IAM roles.