/lab/commerce-workbench
PRODUCT ARCHITECTURE
Commerce workbench
STATE incubatingUPDATED 09.2026
QUESTION
How should a workbench behave when operational speed and error recovery matter more than dashboard decoration?
CURRENT APPROACH
An interface language for dense Shopify operations where jobs, bulk actions, and recovery state must remain visible.
01Compact information hierarchy
02Explicit job state
03Keyboard-friendly bulk workflows
04Recovery designed with the primary path
ARCHITECTURE
INPUT
Iomniq
Iomniq
INTERFACE
STATE
RUNTIME
OBSERVATIONS
- Operational UI benefits from physical hierarchy and dense but stable placement.
- State must remain readable before, during, and after bulk work.
WHAT REMAINS UNRESOLVED
- Finding the right density across different merchant volumes.
- Validating workflow boundaries against broader operational use.
RELATED PROJECT
Iomniq ↗