At a glance
| Code | WI-023 |
|---|
| Phase | Positioning / Go-To-Market, Operational Floor POC |
|---|
| Order | 53 of 93 |
|---|
| Story points | 3 |
|---|
| Primary surface | Plan docs (docs/strategy) |
|---|
| Retires | — |
|---|
| Depends on | — |
|---|
| Blocks | — |
|---|
- Evidence
- docs/strategy/TROVESNAP-PRODUCT-MEMORY-AND-PHASED-PLAN.md
Goals
Rewrite phased plan around operational wedge and POS interop — advances G2, C1, C2, C3, C4 toward its gate(s).
Implementation — what to build
What to do (doc deliverable)
- Rewrite docs/strategy/TROVESNAP-PRODUCT-MEMORY-AND-PHASED-PLAN.md around the operational wedge and POS interop.
- Map each phase to its gates + the operational primitives (rooms/zones, labels, bulk, reports).
- Done when: the phased plan reads consistently with the roadmap + decision log.
Checklist
- ○
G2 POS interop is framed as adoption bridge, not core dependency. - ○
C1 Rooms, zones, and pickup areas exist in the tracking model. - ○
C2 Label batch workflow is first-class and QR print/pack path is demoable. - ○
C3 Bulk edit, mass label, and batch discount path is validated. - ○
C4 Client report skeleton is generated from sale/reconciliation state.
Gates & testing
- ○ G2 POS interop is framed as adoption bridge, not core dependency.
HITL QA
- ○ C1 Rooms, zones, and pickup areas exist in the tracking model.
CODE TEST
- ○ C2 Label batch workflow is first-class and QR print/pack path is demoable.
CODE TEST
- ○ C3 Bulk edit, mass label, and batch discount path is validated.
CODE TEST
- ○ C4 Client report skeleton is generated from sale/reconciliation state.
CODE TEST
Requirements
REQ-GTM-002 accepted POS is interop-first and replacement-later. Done when: Plan + product copy describe POS as an adoption bridge; TroveSnap reconciles around Square/EstateSail/PROSALE/Shopify rather than replacing them.
REQ-OPS-001 accepted Rooms, zones, and pickup areas need to be first-class tracking fields across setup, capture, labels, checkout, pickup, and reports. Done when: Items can be grouped and filtered by room/zone/pickup area, and those carry through to labels and client reports.
REQ-OPS-002 accepted Label batches need a first-class print/pack workflow synchronized through the binding model. Done when: Mass label printing, reprints, skipped labels, room/zone grouping, preprinted sticker-pack codes, and a list of unlabelled high-value items all bind through the same model.
REQ-OPS-003 accepted Bulk operations need early operational support with a conflict preview before applying. Done when: Bulk price/category/room edits, mass label generation, batch discount changes, and duplicate-room setup between sales all show a reviewable conflict preview before applying.
REQ-OPS-004 accepted Client reports need to summarize sale/reconciliation outcomes with audit links. Done when: A report package generates sold/pending/unsold/donated/removed lines, totals by room/zone/consignor/category/day, gross/fees/net/recovered, and an exception list, each linked to status events.
Verify (done when)
the phased plan describes the operational wedge + POS interop bridge.
Cost triggers
No paid API / infra spend triggered by this item.
Status & editing
queued Sprint: Parallel Positioning
Edit status / sprint on the ★ Live Board → — changes are logged live with who / when / why.
Human-in-the-loop
No human tasks linked.
Findings
None recorded yet.
Concerns
None recorded yet.
Tech debt
None recorded yet.
Tools used
No tool calls recorded.
Files & artifacts
No files / artifacts recorded.
Update log
No log entries yet.