Clean logistics masters before automating rates and shipment status

Two customer site codes share the same street address. A cleanup tool marks one as a duplicate and merges them. The next load is rated to the wrong service zone and arrives during the wrong receiving window because the codes represented different docks.

Logistics master data management needs business meaning before deduplication. Establish the identity and scope of sites, carriers, items, units, equipment and services, then assign an owner to the mappings that automation will use. A clean spelling is useful; a correct operating decision is the acceptance test.

Examine what the two site codes mean

Consider an illustrative customer campus, physical location P-7. The customer sends two service-point codes.

The address is shared, but the service point, handling process and commercial zone differ. A useful model can link both service points to P-7 while preserving their separate operating attributes.

Suppose a shipment references CUST-S and the merge substitutes CUST-N. The resulting 10:00 appointment may be valid for the north dock but invalid for the intended south-dock operation. Address similarity cannot settle the mapping.

The master owner should consult the customer's approved site instructions and the operational records. If the codes truly are aliases for the same service point, retain both source aliases against one controlled identity. If they represent distinct operations, preserve the distinction.

Define the scope of uniqueness

A code can be unique within a customer or source system while appearing elsewhere with another meaning. Use the appropriate namespace: source, customer or legal entity, object type and effective period.

A carrier's internal depot code is not automatically a global location identifier. A customer item code may differ from the warehouse's item identity. Do not remove the source code after mapping it; it is often needed to explain an exception or send a response back.

GS1 EPCIS provides a framework for visibility-event information, including the context of what happened and where. Reliable event mapping still depends on the parties agreeing what their identifiers denote. GS1 — EPCIS and CBV artefacts

Maintain separate object types. A transport order, consignment, carton, handling unit and product are not interchangeable identifiers merely because their barcodes can all be scanned. GS1's Logistic Label Guideline addresses identification of logistic units; that identity serves a different purpose from a product or order reference. GS1 Logistic Label Guideline — release 1.3, July 2019

Resolve units before calculating quantities

Consider another illustrative conflict. Customer system A defines one case of item X as 12 units. A legacy warehouse mapping still uses ten units per case. A ten-case receipt therefore becomes 120 units in one system and 100 in the other, a difference of 20 units.

The correction needs the approved item and pack definition, not a global replacement of every occurrence of “case.” Another item or an earlier pack version may legitimately contain ten units.

Record the conversion, applicable item, owner, effective dates and permitted precision. Preserve original quantity and unit alongside the normalised value. A conversion should be reproducible after the master changes.

Distinguish physical pack quantities from billing units. A carrier may price a shipment by chargeable weight while the warehouse counts cartons. Converting both into one unlabeled number makes reconciliation harder rather than easier.

Give changes an effective boundary

A site can change its receiving hours or commercial zone without becoming a different physical location. Keep attribute history and identify which transactions use the old or new definition.

Oracle's rate-record documentation illustrates the role of rate data and validity in transport pricing. A master correction must preserve the version that supported a past rating decision instead of silently rerating history through today's mapping. Oracle Transportation Management 26C — Rate Record

For example, if Zone S changes on 1 November, an October shipment should not inherit the new zone simply because someone opens it in November. Decide whether a transaction stores the effective attribute snapshot or an immutable reference to the relevant version.

A genuine correction to erroneous history needs a separate controlled process. Explain which transactions were affected, which values changed and which financial or operational decisions require review.

Prioritise conflicts by consequence

Start with fields that route work, determine eligibility, change quantities or select a commercial rule. A missing display abbreviation may be less urgent than an ambiguous unloading point, a wrong pack conversion or a carrier identity linked to the wrong legal entity.

Create a worklist with the disputed mapping, affected transaction count, business consequence, proposed resolution, owner and evidence. A high transaction count alone is insufficient: a rare equipment or handling restriction can carry a serious consequence.

Do not automatically approve a fuzzy match because its score is high. Similar addresses, company names and product descriptions are candidate evidence. A responsible master-data owner must confirm the meaning when the result affects a material decision.

Quarantine unresolved mappings in the consuming workflow. The right fallback may be a manual selection from verified options rather than an invented “default” site or unit.

Test the consuming decisions

A spreadsheet register can support a small mapping set if changes are reviewed and dated. Native master-data tools may add validation and ownership. A shared mapping service can help several systems use the same approved crosswalk, provided it exposes versions and unresolved cases.

Replay the north- and south-dock shipments, the ten-case receipt and a transaction spanning a rate-zone change. Verify destination, appointment, quantity and rate selection. Include an unknown code and an expired alias.

Acceptance should show that every in-scope code resolves to one intended meaning for its context and date. It need not force every source alias to become a different physical object.

Track new unknown codes, mappings used outside their effective period and transactions requiring manual correction. Those measures identify whether governance is working after the initial cleanup.

Make the mapping explainable

The useful master is one whose owner can explain why a transaction used a particular site, unit or rule. That explanation should survive a rename, an alias, a new pack size and a later audit.

Next actions

1. Identify the master fields that directly change routing, eligibility, quantity or rating.
2. Resolve one ambiguous site and one unit conversion against approved operating evidence.
3. Preserve source aliases, ownership and effective dates in the mapping record.
4. Replay affected decisions before releasing the changes, keeping unresolved mappings visible.