—
Shore Point Pilot Impact
Loading manager view…
0
Visited
0
Counts
0
Drafted
0
Approved
0
Exported
AI manager summary
rules-based · from your data
—
—
Parse quality
Demo parser mode · local0
Lines parsed
0
Matched
0
Ambiguous
0
Unmatched
0
Skipped
—
Order quality
—
Acceptance rate
—
0
Aliases to fix
Skipped + unmatched fragments
0
Missing VIP code
Export blocker until ops fixes
0
No par on file
Counts surface but no order drafts
Visit time
Measured count → order time
—
No completed visits yet — approve an order to start measuring.
Estimated time saved (heuristic)
0m
—
Real "time saved" needs Shore Point's manual-process baseline — a pilot week measures it.
Per-rep leaderboard
drafted · approved · exportedNo rep activity yet.
Per-account status
0Pilot dependency — real VIP import format needed
Exports are a labeled stub today. To ingest pilot orders into VIP cleanly, Shore Point ops provides the items below. When the real spec lands, only the export adapter changes.
- ▸VIP account codes — real codes for every pilot account (placeholders like SP-12001 today).
- ▸VIP product codes — a VIP SKU per product (missing ones fall back to the internal SKU).
- ▸Item file — catalog cut: SKU, name, brand, package size, case pack, VIP code.
- ▸Account list — pilot accounts with rep + route / day mapping.
- ▸Par / history — par levels per account / SKU, plus any rep-typed → SKU alias history.
- ▸Sample import / export format — column names, field order, delimiter, encoding, batch size, ingestion path (file drop / email / API).
All numbers above are derived from the in-browser demo store. Not a customer-facing KPI.