Inventory Mapping

Inventory Mapping is the onboarding count workflow. It helps a team verify what exists physically, where it is stored, and what should be imported into the WMS or another system after review.

Supervisor view

The supervisor view is designed for desktop. It is used to:

• select the warehouse project,
• upload product or expected inventory data,
• monitor counters,
• track progress by worker and location,
• review exceptions,
• export mapping and count files.

Counter view

The counter view is designed for mobile and tablet. It should be simple enough for temporary floor staff.

The guided flow is:

1. Scan or enter the location.
2. Scan UPCs or SKUs found inside that location.
3. Enter or confirm quantity.
4. Save the row.
5. Confirm moving to the next location.

UPC matching

If the supervisor uploads a product list with SKU and UPC, counters can scan UPCs and the tool can match the UPC to the real SKU. Unknown UPCs should be flagged for review, not silently ignored.

Multiple counters

Multiple users can work on the same project. Each scan event should include:

• project,
• location,
• SKU,
• UPC,
• quantity,
• worker,
• timestamp,
• source device.

The supervisor should use this to identify progress, duplicate work, and locations that may need a recount.

Failsafes

To protect a long count:

• progress autosaves,
• each saved row is timestamped,
• the supervisor can export progress before the count is complete,
• counters explicitly confirm when leaving a location,
• unknown SKUs and UPCs are retained as exceptions,
• completed locations should be visible in the progress dashboard.

Exports

Expected exports include:

• SKU-location mapping CSV,
• count result CSV,
• exceptions CSV,
• data quality report,
• launch/import file for the target WMS.