← Inventory & exceptions

YUNXIU / OPERATIONS GUIDE

Multiple barcodes for one product: controlling warehouse master data

Manufacturer, marketplace and internal codes may coexist, along with old and new packaging. Mapping them all to one SKU can hide pack-size or version differences. Establish what each code identifies before treating it as an interchangeable alias.

Yunxiu · Operations planning reference · Updated 8 November 2026

Identify the barcode's level

Distinguish item, case, pallet, serial and shipment identifiers. Record owner, source, SKU, packaging unit and active status for each mapping. Verify equivalence against documents and physical goods; similar names are insufficient. Where a code embeds several values, define parsing rather than treating the entire string as a simple product ID.

Validate changes with real examples

Keep sample codes and packaging evidence, then test identity and unit results. A code assigned to two products is a conflict, not permission to select the first match. Preserve owner context for shared codes. Review stock and open orders before changes, including any relabelling or rechecking. Operators should not create aliases merely to bypass an unknown-code error.

Define exception paths

Unknown, retired, damaged and wrong-unit codes need distinguishable handling. Manual entry must verify identity and quantity rather than pick the closest SKU. Investigate repeated scans or existing serials to distinguish duplicate activity from duplicate identifiers. Any temporary exception needs a narrow scope and record, not an indefinite promise to fix data later.

Retain history and review conflicts

Retired codes may still be needed for returns or recalls. Disable new receipt where appropriate without erasing historical interpretation. Review one-to-many conflicts, unsupported mappings and missing units, testing actual flows. Version changes and assign ownership so sales, warehouse and interfaces do not maintain incompatible private lists.

Illustrative decision or record

Illustrative scan test: X identifies one unit and Y identifies a ten-unit case. Both can relate to one SKU without both posting one base unit. Test X, Y and an unknown code for identity, units, quantities and exception handling. If a new eight-unit case reuses Y, resolve the packaging-version conflict instead of relying on visual guesses.

Before you proceed

  • Code level, owner and units are defined
  • Conflicting codes do not select arbitrary SKUs
  • Changes are traceable and retired-code history remains

Related operations

Review the cargo and the work together

Share the product, packaging, batches and quantities, customs status, expected schedule and the special requirements discussed here. Confirm acceptance before arranging delivery.