Map barcodes and SKUs explicitly
Connect the internal item number, variant SKU and existing barcodes in an approved mapping register. Include pack units: carton and unit codes may represent different quantities. Create an exception case for unknown codes or codes mapped to more than one item.
Connect counts with movement records
Record the count time and last confirmed movement for each SKU and location. Reconcile receipts, dispatches, reservations and blocks between export and count individually. Give each difference a cause, evidence and approval before transmitting a corrected value.
Track exceptions deliberately
Assign each open discrepancy a reference, owner and next review date. Separate a confirmed physical shortage from an unresolved transmission error. This makes it clear whether a count, mapping review or data retransmission is required.
Plan step by step
- Maintain one unique SKU per product variant and one clear mapping per physical warehouse. Resolve reused barcodes and different pack units first.
- Compare store and warehouse exports at the same cutoff. Record timezone, update time and pending data transfers; reports taken at different times are not a reliable basis for correction.
- Map physical, reserved, blocked and saleable quantities separately. Add expected deliveries to released stock after the agreed receiving checks.
- For discrepancies, review the last confirmed movement: order, cancellation, shipment, return, transfer or count adjustment. Record the cause and owning system before overwriting quantities.
- Test the last available item, a cancellation and a return still blocked from sale. Agree sync frequency, warning thresholds and escalation for each channel.
Illustrative internal mapping: 50 physical units, with 8 reserved and 2 blocked, leave 40 released units. Keep 20 expected inbound units separate. This example does not establish that a particular system connection is available.
Confirm before release
- Which system owns inventory and which only relays it?
- How are failed updates detected and retried?
- Who approves corrections and where is the change recorded?
Next step
Bring your product profile and the open questions from this guide to the conversation. Our team will agree services and handling with you.