OMX Innovation · Direct Ship Supplier Visibility · Feed + QR Device
We sell what the supplier never confirmed.
9 tickets in 14 days traced to one root cause: no daily stock-availability signal from the direct-ship supplier. Only 3 of OMX's DS suppliers run a feed today — and the cluster of failures in this brief simply does not occur on their orders. Two paths to close the gap: cheap FTP feed for the top 15 (weeks), QR-sticker + pack-slip photo device for the long tail (Innovation Garage Oct 2026).
01 / 06
The 9 tickets

One cluster, one root cause.

"Daily supplier stock-availability feed → we only sell what the supplier confirms is in stock. Three suppliers run this today and the cluster of failures we see in this brief does not occur on their orders." — Jeff Sutton, CTO · 22 June 2026
INC-557564
P2 · OPEN · 22 Jun
Midcentral DHB — split orders lose delivery instructions. CC'd 3 managers, "loose this customer" tone.
INC-556959
P1 · OPEN · 17 Jun
MSD / Ingram Micro — address-line truncation, Pronto PO template re-design ask.
INC-555413 / 555021 / 554545 / 554054 / 554045 / 553631
P1 · CLOSED ×6
SO ↔ PO relink pattern. Arlene Nix ×3 (template-quality every time), Tiara ×2, Marie ×1. Same defect, manually patched.
INC-553385
P1 · CLOSED · 27 May
Account creation — tangential to cluster, same sub-category.
Source: Freshservice REST API · category 'Pronto / Operational support' · 27 May – 22 Jun 2026. 9 in-cluster · 8 P1 · 7 closed-by-IT · 2 open and customer-facing. Resolver concentration: Subhashis Chatterjee (FDL Applications) closed 7 of 9 — structural fix never landed.
02 / 06
Two options — same outcome

A is the cheap one. B is the platform.

Option A · The easy one
Daily Supplier Inventory Feed (FTP)
Supplier drops a CSV every morning: SKU, sellable-today Y/N. OMX ingests at 06:00, suppresses non-sellable lines in Pronto by 06:30. We do not sell what the supplier did not confirm.
  • Cost: low — CSV spec + SFTP creds + ingestion job + Pronto integration. Supplier-side ETL is their cost.
  • Time to first supplier: weeks, not months. Onboarding kit + 1st supplier in 4 weeks.
  • Scales to: top 15 DS suppliers ≈ 80% of DS volume. Long tail won't invest in ETL.
  • Pilot: furniture — long lead times, bulky SKUs, customer expectation lower; pain of sell-then-cancel is highest.
Option B · The strategic one
QR Sticker + Pack-Slip Photo Device
OMX prints unique-QR sticker sheets, posts to every DS supplier monthly. Supplier picks order, sticks QR on pack slip, photos pack slip + courier ticket via mobile (WhatsApp / Teams / OMX PWA). CV pipeline links QR ↔ OMX PO ↔ Customer PO ↔ courier tracking. Customer scans QR → sees recipient + delivery instructions queried, never printed.
  • Cost: higher — sticker production + capture flow + OCR + linking service + scan page. All OMX-side; supplier needs only a smartphone.
  • Time: MVP in 8–12 weeks. Per-supplier onboarding then = send stickers.
  • Scales to: every supplier — long tail, international, anyone with a phone.
  • Solves: stock signal + address-line truncation + split-order instruction loss + tracking + customer comms loop, in one device.
Run both, in sequence. Option A is immediate relief for the top 15. Option B is the platform that scales to everyone and unlocks the customer-facing scan. Both feed the same supplier-availability table — A's feed becomes a redundant cross-check against B's photo signal.
03 / 06
The device — how the QR loop works

From supplier despatch to customer scan.

01
OMX prints + posts
Unique-QR sticker sheets (omx.nz/dsqr/<code>). Paper + permanent adhesive. Monthly drop per supplier.
02
Supplier picks + sticks
Supplier receives DS PO (unchanged), prints pack slip (unchanged), peels one QR and sticks it on the slip.
03
One-tap photo capture
Pack slip + courier ticket — both photos via WhatsApp / Teams / OMX PWA. The whole device on the supplier side is a phone.
04
OMX links it all
CV extracts pack-slip #, supplier PO ref, OMX PO #, QR, courier tracking #. System writes QR ↔ OMX PO ↔ Customer PO ↔ courier.
05
Customer scans on receipt
Recipient + department + internal delivery instructions queried (not pre-printed). Privacy-safe. Re-route friendly. Plus live courier tracking.
Why the customer-scan model matters
Today, supplier labels truncate the customer's ship-to lines 4-5 (where the recipient + department actually lives). Robin Kennedy-Moffat's INC-556959 lays this out with screenshots. With QR-scan, the recipient information is looked up at scan time, so a 2.5-line supplier label is no longer the bottleneck — and we never print recipient names on a sticker that might be re-used or photographed in transit.
04 / 06
Roadmap

Both tracks. Both visible. October demo.

Week 1-2
A1-A2 · B1-B2
Confirm the 3 feed-suppliers' format. Pick furniture pilot + top-3 furniture suppliers. Design spike: sticker, capture UX, OCR pipeline, scan page. Tech alignment with Matariki Stars (shared CloudFront + HMAC short-codes).
Week 3-4
A3-A4 · B3
Build supplier onboarding kit (CSV spec, SFTP, validation, fail-safe). Stand up supplier-availability table in Pronto. Procure sticker rolls (~10K-roll order).
Week 5-8
A5 · B4-B5
First pilot supplier onboards on the feed (2-week shadow mode then live). MVP build: capture-app + ingestion + linking. Customer scan page minimal, mobile-first, single page no login.
Week 9-12
B5 pilot
Closed-loop test with 1 willing supplier and 3 willing customers. Pronto integration deferred to phase 2 — phase 1 writes direct into the supplier-availability table.
October
Innovation Garage demo
Live QR scan + customer reveal in a 5-min booth slot. Marketing co-owns the narrative. Lands well: tactile, visual, customer-facing.
05 / 06
The ask

What we need.

Audience
Primary: Chief Operating Officer + Customer Service Director + CFO — visibility = lower CS cost, lower write-off, retention. Secondary: Commercial — DS customers are often K3+ where margin matters most. Tertiary: Supplier relationships — sticker model gives the long tail a cheap way in.
References
  • Primary source: D:\00-INBOX\2026-06-25\dglr-trace\plexconz__2026-06-22__Pronto_Direct_Ship___Cluster_Findings_v2__solution_options___both-parties_tone___DS-Cluster-Findings-22Jun2026-v2.pdf (18pp, JARVIS for Jeff Sutton CTO, 22 Jun 2026). Every figure on this deck cited from this brief.
  • Memory: OMX Direct Ship Supplier Visibility two-option program (project_omx_ds_supplier_visibility) — Option A FTP / Option B QR + customer-scan = recipient info queried not printed / shares Matariki Stars stack / Oct Innovation Garage target.
  • Memory: OMX Matariki Stars (project_omx_matariki_stars) — same physical-QR → web-app pattern, dynamic QR + HMAC short-codes at CloudFront edge.
  • Memory: OMX Freshservice direct REST API pattern (reference_omx_freshservice_api_pattern) — how the 9 tickets were pulled (category 4000269173 BI / Pronto Operational Support).
  • Memory: DIFOT canonical definitions (reference_omx_difot_canonical_definitions) — Direct ship = Z-warehouse, +7wd target.
  • Sibling decks: Deck 11 (DS Supplier Visibility seed) · conference-activation program · Matariki Stars program.
06 / 06
← All decks