Verification
Scan DN → PO → Haier SN → AEON Price Tag. A product is not verified unless it matches a VERIFIED mapping.
This Session
DN Progress
Every active DN with ordered, verified, remaining quantity and failed attempts by model.
Verification History
Every scan attempt, pass or fail, is kept — nothing is overwritten.
| Time | User | AEON Batch | DN | PO | Haier SN | Haier Code | Model | Raw Barcode | AEON Code | Expected | Result | Recheck | Note |
|---|
Product Mapping Master
Permanent AEON Product Code ↔ WMS Product Code relationship. PO is never part of this identity. Only VERIFIED mappings are used for PASS/FAIL.
| AEON Code | AEON Description | Detected Model | WMS Product Code | WMS Model | Status | Source | Confirmed By | Last Seen |
|---|
WMS Product Master
DATA SOURCE A — WMS Product Code ↔ Haier Model, persistent. Used to detect models in AEON descriptions.
WMS Master Conflicts — Review Required
Same WMS Product Code seen with a different Model. The original is kept until resolved.
| WMS Product Code | Model | Source File | Imported | Last Updated |
|---|
AEON PO Batches
Each AEON order-file upload opens a 48-hour temporary verification window per PO. Repeated POs get a new batch and window; nothing is overwritten.
| Batch ID | PO | Source File | Uploaded | Expires | Status | Completion | Product Lines | Verified (PO total) |
|---|
Mapping Review
Confirm candidate mappings, resolve conflicts, and see what's still unmapped.
0
Waiting verification
0
Conflicts
0
No WMS match
0
Ambiguous model matches
0
Missing WMS data
0
Missing AEON data
Product Mappings
AEON Product Code ↔ WMS Product Code. PO is not part of this identity. All actions require supervisor authorization and are audited.
| AEON Code | AEON Description | Detected Model | WMS Product Code | WMS Model | Status | Evidence | Actions |
|---|
WMS Model Mismatches — Review Required
A manually imported mapping's WMS Product Code exists in the WMS Product Master, but the uploaded Model text differs. The mapping still works normally — this is informational only.
Ambiguous Model Matches — Review Required
AEON descriptions where more than one known Haier model string was found. No candidate mapping is created automatically for these.
Missing WMS Data
AEON products seen in order files with no matching model in the WMS Product Code Master or Haier Order File yet.
Missing AEON Data
Haier order lines with no matching AEON product seen yet.
Recent Mapping Activity
Data Upload Centre
Three data sources. Nothing historical is deleted; duplicate files/rows are detected automatically.
A — WMS Product Code Master
Persistent: WMS Product Code ↔ Haier Model. Column names vary by export, so confirm which column is which before importing.
Drop file here, or
B — AEON Order File
Pipe (|) delimited .csv. HEADER| and TRAILER| control rows are ignored automatically. Field 9 = AEON Product Code, Field 10 = Description. Discovers product mapping evidence and opens a 48-hour PO verification batch per PO in the file.
Drop file here, or
C — Haier Order File
Operational data: DN ↔ PO ↔ WMS Product Code ↔ Model ↔ Ordered Qty. Auto-detects the real SAP Download format (e.g. worksheet "1. SAP Download", headers on row 5) — falls back to a manual column-mapping step if the layout can't be confidently identified.
Drop file here, or
D — Manual Product Mapping
Upload manually prepared AEON Product Code ↔ WMS Product Code mappings. This updates the permanent Product Mapping Master only and does not create AEON PO verification batches, does not affect DN Progress, and does not alter Haier Order File data.
Drop file here, or
Upload History
| Time | Type | Filename | User | Records | Added | Updated | Duplicate | Rejected |
|---|
Supervisor Authorization
Confirming mappings, resolving conflicts, retiring mappings, quantity overrides, duplicate-serial overrides and WMS master conflict resolution all require supervisor PIN sign-off. Supervisor authorization is enabled. Change the prototype PIN before operational use.
Backup & Restore
Export all local data as a single JSON backup, or restore from one.
User Management
Create, deactivate, and manage named accounts. Every action here requires supervisor authorization and is recorded in Audit History.
Add User
| Username | Role | Status | Created | Last Login | Actions |
|---|