Add: Wanda Plaza, Fuqiao Street, Rencheng District, Jining City, Shandong Province, China
+86-18206519878
   Home > News > DWS Parcel Data Matching: Prevent Barcod…

DWS Parcel Data Matching: Prevent Barcode, Weight and Dimension Mix-Ups

DWS Parcel Data Matching: Prevent Barcode, Weight and Dimension Mix-Ups

A barcode, weight and dimension mismatch can hide inside a complete-looking parcel record: all fields are populated, but the values belong to different parcels. Before choosing a dimensioning, weighing and scanning workflow, ask how the supplier will demonstrate that each accepted record belongs to the physical item being handled.

This guide focuses on that association, not on general ERP integration. The examples are buyer review questions, not a specification of Keepway software or a promise of automatic exception handling.

Choose the parcel identity before comparing measurements

A package may carry a carrier label, a product barcode and an internal warehouse label. Agree which identifier the process should use, how obsolete labels are handled and what happens when more than one candidate is readable. A successful scan alone does not establish that the intended identifier was selected.

For a workflow using GS1 identification, an SSCC identifies a logistics unit, as explained in GS1's logistics-unit identification guidance. That does not mean every courier parcel must use an SSCC, or that a particular machine supports every barcode format. Confirm the identification scheme for your own operation.

Follow Parcel A and Parcel B, not just two complete rows

Illustrative example only: Parcel A carries ID-A; its measurements are weight-A and size-A. Parcel B carries ID-B; its measurements are weight-B and size-B. These symbols are not actual test results.

The intended association is ID-A + weight-A + size-A. A row containing ID-A + weight-B + size-B is unacceptable even if every field is populated and both sets of values look plausible.

Ask the supplier to show how the physical item, the measurement event and the accepted record can be compared. Do not accept “the most recent scan” or an unchanged row count as sufficient evidence of correct matching. The agreed evidence must distinguish A from B without relying on memory.

For a practical review, use clearly distinguishable, approved sample parcels under the supplier's safe operating procedure. Keep the spacing and loading rules required by the selected configuration. Do not deliberately send two items into a single-item measuring area or interfere with sensors to provoke a fault.

Recognize four different ambiguities

A manufacturer example illustrates why these questions matter: the METTLER TOLEDO CSN950 MultiHead Quick Guide, printed page 12 distinguishes multiple valid barcodes, a barcode potentially belonging to multiple packages, missing measurements and multiple measurement results. Those are examples from that manufacturer's system, not Keepway error codes or included functions.

  • Multiple barcodes on one parcel: which code is accepted as its identity, and how is an unresolved choice made visible to the operator?
  • One code associated with more than one item: what evidence establishes which physical parcel owns the measurements? An ambiguous association should not be treated as a confirmed match.
  • An identifier without a complete measurement: how can the reviewer distinguish a missing weight or dimension from a valid result? A blank or unknown value must not silently become an accepted zero.
  • Several measurements for the same parcel: after a remeasurement, which result is accepted, and how is the earlier result distinguished from it?

Ask for paired evidence, not a polished summary screen

Use a short evidence sheet to compare physical identity with the record selected for use. Request anonymized examples where customer or shipment information is involved. If a function is not included in the proposed configuration, record that limitation instead of assuming it can be added through a setting.

Evidence to compareQuestion to resolve
Physical sample and intended labelWhich parcel and which identifier should this record represent?
Accepted weight and dimensionsCan all measurements be traced to that same parcel, with units stated?
Ambiguity or remeasurement recordWhich result remains unresolved, and which result was approved for use?
Destination-system display, if includedDoes the displayed association still match the approved parcel record?
Open discrepancy and decision ownerWho resolves the mismatch before the record is used?

Agree the expected outcome before the demonstration. Review ordinary single-parcel records first, then discuss ambiguity using anonymized exception records or a supplier-approved demonstration. Record whether each association was demonstrated, remained unresolved or fell outside the quoted scope. A screen that shows all fields is not, by itself, an acceptance result.

Resolve association before relying on the result

If the measurement record will inform routing or another downstream decision, agree who decides whether it is usable. The handling of an unresolved parcel may involve operator review or another project-specific process; the method and included equipment must be confirmed. A DWS station should not be assumed to include an automatic reject lane, a sorting mechanism or universal system compatibility.

For flexible parcels, review the poly mailer sample-test guide separately to plan representative samples and dimension-measurement checks. Confirm parcel suitability as well as record association; one review does not replace the other.

Planning a parcel measurement station? Review the Keepway DWS parcel dimensioning and weighing system, then describe your intended parcel identifier, label examples, handling sequence and required measurement-record checks. Ask which association checks, software functions and downstream handling arrangements are included in the proposed configuration.

Discuss your DWS parcel-record requirements with Keepway