The Sourcing Logic of Cross-Brand Commonality: Cut SKUs with Platform Sharing, Not with Guesswork

One door handle fitting three badges and five nameplates is not a marketing claim. It is the predictable result of platform sharing and badge engineering in Japanese light commercial vehicles. For a trader, the value of this fact is not that it is interesting. It is that it simultaneously reduces your SKU count, your inventory capital and your dead-stock exposure.

Commonality is also where return rates are highest. The reason is simple: most buyers judge commonality by whether two parts look the same, instead of verifying it against OEM part numbers. This article gives you an executable method — how to confirm commonality, how to build the reference tables, how to present multi-fitment on a quotation and in a catalogue, and when you must not consolidate at all.

1. Why the same part fits vehicles wearing different badges

Answer first: because vehicle makers share platforms, not because parts makers are lazy. Japanese light commercial vehicles amortise development and tooling cost by deriving several nameplates from one chassis and body structure. For exterior parts such as door handles, door hinges, latches and hood locks, as long as the mounting face and the actuation travel are unchanged, there is no engineering reason to cut a new tool.

For procurement this means that demand which looks fragmented at the nameplate level is actually concentrated at the part level. Your job is to find that concentration and convert it into cash benefit.

2. Platform sharing versus badge engineering

They are not the same thing. Platform sharing means several different vehicles are derived from one chassis. Badge engineering means the same vehicle is sold under different marques and model names. Badge-engineered pairs have the highest probability of parts commonality, because they are literally the same vehicle from the same production line. Platform derivatives must be verified part by part, because a derivative may have changed door structure or lock specification.

Work in this order: first ask whether it is the same vehicle rebadged, then whether it is a platform derivative, and only then compare part numbers item by item. Reverse that order and you will be hunting for evidence to support a conclusion you already assumed.

3. Which Japanese LCV families are worth auditing first

For exterior parts, the families worth auditing first are the relationship between the Toyota Town Ace and Lite Ace lines, the Toyota and Daihatsu cooperation in the light commercial segment covering families such as the Gran Max and Hijet, and the continuity of the Toyota Hiace across generations and body types. These nameplates carry different names in different export markets, which makes them high-probability territory for shared parts.

This must be said clearly: the above is a list of directions worth investigating first, not a set of interchange conclusions you can apply directly. Every single interchange claim has to come back to part-number level verification.

4. Visual similarity is not evidence

Answer first: photo comparison can be used to exclude, never to confirm. Two door handles can look almost identical while the pawl angle differs by two degrees, the rod hole position by three millimetres, and the substrate and plating specification are different. The result is a door that does not close tightly, rattles, or works loose after six months.

Use vision correctly, as the first sieve. If the appearance is clearly different, reject immediately. If the appearance matches, move to part-number verification and never skip it. Visual screening saves you time, not verification steps.

5. Three grades of commonality: same number, supersession, functional interchange

Split commonality into three grades so that internal communication cannot go wrong. Grade one is the same OEM part number: direct interchange, lowest risk. Grade two is a supersession relationship, where an old number has been replaced by a new one; this is usually backward compatible but not necessarily forward compatible. Grade three is functional interchange, where the numbers differ but form, mounting interface and travel correspond.

Grade three carries the highest commercial value and the highest risk. Without measurement records and trial-fit records, grade three should never appear in your catalogue.

6. The OEM part number is the only verifiable anchor

Answer first: the only identifier both buyer and seller can verify independently is the OEM part number. Nameplates vary by market, model years shift by a year between build date and registration date, body-type names differ by country. Only the part number is a unique key inside the manufacturer's own system.

So every cross-reference you build must use the part number as the primary key, with nameplate and year as attributes rather than as the basis of judgement. Any interchange table that cannot state a part number is an opinion, not data.

7. How supersession chains work

When a manufacturer improves a part or rationalises its numbering, the old number is flagged as replaced by a new one, forming a chain from A to B to C. Three things matter in practice. The chain can have several levels. It can be one-to-many, where an old number splits into several new numbers. And it can be many-to-one, where several old numbers are consolidated into a single new number.

One-to-many is the dangerous case. When it happens, the new number cannot be pushed back unconditionally over every application of the old number; it has to be split by model and year.

8. Why you must never delete an old part number

Answer first: old numbers are a traffic asset and a communication asset. Your customers' old catalogues, the parts still on the vehicles, and the market's spoken habits all still use the old number to search and to enquire. Deleting the old number from your database is the same as switching those enquiries off.

The correct treatment is to keep the old number as an alias, mark its status as superseded, and point it at the current number. When a search hits the old number, the system should display the current number together with a short replacement note.

9. Left and right: the most common and most expensive error

Answer first: side errors are the number one return cause for exterior parts. The definition must be locked down: as seen by the driver facing the front of the vehicle, left is LH and right is RH. You must also state whether the vehicle is left-hand drive or right-hand drive, because the driver's seat position changes what a customer intuitively calls the left side.

Quotation, catalogue and package label must all carry both the LH/RH text and a diagram. Do not use text alone, and do not use a picture alone.

10. Body type: van, pickup, double cab

Answer first: under one nameplate, the van, the pickup and the double cab frequently differ in door count, side door type (sliding or hinged) and rear door type (tailgate or barn doors). The handles and latches that go with them differ accordingly.

When you build the table, body type must be its own column. Never bury it inside the model-name string, or you will never be able to filter on it and never be able to export it as structured data.

11. Model years and facelift break points

Answer first: record years as a start-to-end range rather than a single year, and flag whether a mid-cycle facelift break point exists inside that range. Exterior parts are the most likely to change at a facelift, because even a small styling revision moves handles, garnish covers and lock apertures.

Keep four separate fields: year from, year to, includes pre-facelift, includes post-facelift. One field cannot carry those four facts.

12. Regional specification and market variants

Answer first: the same nameplate in different markets may carry different lock hardware, different anti-theft configuration, and different plating and weathering specifications. Typical configuration differences across the Middle East, Southeast Asia, Africa and Latin America are enough to make the same vehicle need a different part.

Put a market code in your cross-reference table, and ask the customer at enquiry stage which market the vehicle was sold into, not just what it is called.

13. A six-step process to verify commonality

In one line: VIN, OEM part number, supersession check, catalogue cross-check, physical measurement, trial fit record. The first three steps are data verification, the last three are physical verification. Skip any one of them and you cannot publicly claim interchange.

Turn the six steps into a fixed form and record an owner and a date for every interchange pair. When a customer disputes a fitment later, that record is the basis of your position.

14. The measurement checklist for physical verification

Answer first: measurement needs a fixed item list, otherwise results taken by two different people cannot be compared. A reasonable minimum set for exterior parts includes mounting hole centre distance, hole diameter, handle travel, lock cylinder aperture position, pawl angle, rod interface type, overall length, width and thickness, plus material and surface treatment.

For every item record the gauge used and the tolerance, and keep photographs and a sample number. Measurement data with no sample number cannot be reproduced by anybody a year later.

15. How to design the cross-reference tables

Answer first: one table should do one job. Split it into three. A part master, one row per part number. An alias table, mapping old numbers and alternate numbers to the canonical number. And a fitment table, one row per combination of part number, model, year range, body type and side.

Never pack several models into one cell separated by commas. That breaks filtering, breaks reporting and breaks data exchange at the same time, and it also destroys any audit trail of who added what.

16. One canonical number plus a set of aliases

Answer first: each physical part may have exactly one canonical part number; everything else is an alias. The canonical number is used for stock, quotation and shipping documents. Aliases are used only for search and matching, and never enter a transaction document.

The alias table must record source and status. Source can be OEM, competitor, or customer-assigned. Status can be current, superseded, or suspected and pending confirmation. If source and status are mixed together, the alias table becomes a rubbish tip within a year.

17. Normalising part numbers: O versus 0, I versus 1

Answer first: the characters most often confused during manual entry and OCR are O and 0, I and 1, S and 5, B and 8, along with full-width versus half-width characters, hyphens and stray spaces. Run a normalisation pass before ingest: upper-case, strip non-alphanumeric characters, standardise length checking, and keep the original string.

The normalised form is used only for matching. It must never overwrite the raw data, because the original string is your only way to trace where an error came from.

18. Avoiding false merges from a one-character difference

Answer first: any automatic matching routine needs a similar-but-not-equal interception rule. When two part numbers differ by exactly one character, they must not be merged automatically; they go into a human review queue. Manufacturers routinely use the last one or two characters to distinguish side, colour, facelift version or market specification.

Write the rule explicitly: any pair with an edit distance of one requires human confirmation, with the confirming person and the date recorded. This one rule blocks most catastrophic false merges.

19. The commercial payoff of SKU consolidation

Answer first: consolidation is not about having fewer rows in a database. It is about placing the same capital on fewer, faster-moving items. When demand from three nameplates converges on one part number, monthly shipments on that number triple, and both reorder frequency and reorder quantity improve.

The benefit shows up in this order: purchasing leverage, minimum order quantity thresholds, rack space, stock-count labour hours, and finally write-down and obsolescence risk.

20. Inventory turns and dead stock

Answer first: dead stock is usually not caused by buying too much, but by buying too finely. When demand is split across too many near-identical numbers, each of them needs its own safety stock, total inventory becomes artificially inflated, and each one can go stale independently.

After consolidation, safety stock can be pooled and the total level falls naturally. Review three numbers every quarter: total active part numbers, the percentage of numbers with movement, and the value held in numbers with no shipment for twelve months.

21. Packaging and shipping density

Answer first: consolidation also improves freight economics. Once volume concentrates on one part number, you can ship full cartons of a single item. Carton sizes stabilise, stacking becomes predictable, and volumetric utilisation rises, so you no longer break cartons to combine odd-lot items.

Exterior parts are mostly awkward shapes, so standardising carton size often has a bigger effect on landed cost than negotiating unit price. This part of the payoff is regularly underestimated.

22. How to present multi-fitment on a quotation

Answer first: a quotation must let the buyer see at a glance which applications one part number covers, instead of hiding fitment in an attachment. Each line should carry your part number, the corresponding OEM number, side, model and year range, body type, packaging method and carton quantity.

Multi-fitment belongs in a dedicated column on the same line, together with one verification sentence, for example: fitment is based on OEM part number cross-reference; please confirm by VIN.

23. Writing fitment for catalogues and websites

Answer first: a catalogue has to serve human readers and machines at the same time. Humans need a clean model and year table. Machines need structured fields so that search engines and AI answer systems can extract and answer correctly.

Avoid vague phrasing such as universal fit or suits Asian vehicles. That wording does not produce orders. It produces wrong parts, returns and complaints.

24. Make VIN and OEM number mandatory intake fields

Answer first: adding two fields to your enquiry form removes most wrong-part incidents. Ask the customer for the VIN and for the OEM number stamped on the old part, plus three photographs of the old part: front, back and mounting face.

If the customer can only supply nameplate and year, mark the quotation as not VIN-verified so the risk is carried knowingly by both parties, rather than argued about after the container lands.

25. When not to consolidate

Answer first: do not consolidate when a difference could affect safety, sealing or durability. Physically fitting is not the same as functioning for the life of the vehicle. Anywhere a locking mechanism, pawl strength or anti-release design is involved, keep the extra SKU.

Apply three tests: is the difference quantifiable, does it fall inside tolerance, and do you have trial-fit and durability data. If any one of those is missing, list the parts separately.

26. Where the line sits for safety-related items

Answer first: latches, door hinges, hood locks and tailgate locks are high-consequence parts. If they fail, the consequence can be a door opening in motion or a component detaching from the vehicle. These parts do not accept close-enough interchange.

The handling rule is straightforward: even when the external shape is identical, keep separate part numbers with separate verification records, and do not merge them on the grounds of functional interchange. An extra SKU costs far less than one incident.

27. How this connects to ACES and PIES data discipline

Answer first: the cross-reference tables you build internally are structurally the same thing as ACES fitment data and PIES product data. ACES answers what the part fits, PIES answers what the part is, and both use the part number as the primary key.

Even if you do not currently ship to North America, organising your data in this shape means that when a channel later demands a standard format, you will barely have to rework anything. It is the cheapest one-off investment in the whole exercise.

28. What evidence to demand from a supplier

Answer first: ask a supplier for evidence, not for assurances. A reasonable request list is an OEM part number cross-reference list, a key dimension drawing or measurement report, trial-fit photographs of the sample, explicit marking of side and body type, and packaging method with carton quantity.

If the supplier can only answer that the part fits a lot of vehicles, it means verification has not been done. At that point what you need is not a discount. It is data.

29. A ninety-day consolidation rollout

Month one is the audit: export every part number, flag duplicates and suspected interchanges, and identify the top twenty percent of items by value. Month two is verification: run part-number and physical verification on that top twenty percent, and build the canonical and alias tables. Month three is deployment: update the quotation template, the catalogue and the enquiry form, and set a quarterly review.

Do not attempt everything at once. Start with the category that carries the most value and the most returns, and you will see turnover change within the first quarter.

30. The pricing and competition trap of shared parts

Answer first: the more nameplates one part number covers, the easier it is to shop around. The volume that consolidation creates is an advantage, but it also turns that number into a market focal point that anybody can quote. The response is to move your value into data and service: clean fitment data, explicit side and body-type marking, stable carton quantities and a reliable lead time commitment.

Quote a single-part-number price alongside a package price for the consolidated group, so the customer sees total cost of ownership after consolidation instead of comparing one unit price in isolation.

31. Standard handling when a wrong part is shipped

Answer first: wrong parts cannot be eliminated entirely; what matters is that every incident feeds back into the data. The standard sequence is: obtain photographs of the old part and its OEM number, confirm the VIN, compare the shipping record against the fitment table, decide whether it was a data error or a communication error, update the fitment or alias table, then close and notify.

Tabulate the causes of wrong-part cases every quarter. If side errors plus body-type errors together exceed half of them, the problem is your forms and your labelling, not a careless customer.

32. Maintenance rhythm and update triggers

Answer first: a cross-reference table is not a one-off project. It needs a fixed rhythm plus event triggers. A quarterly full review is a sensible rhythm. Event triggers include a manufacturer supersession announcement, a new model launch, a customer-reported wrong part, and a supplier retooling or a change of supply source.

Record a version number, a date and the reason for every change, and keep the previous version. A cross-reference table with no version history cannot prove what you relied on at the time a dispute arose.

33. Conclusion: commonality is a discipline problem, not a luck problem

Everybody knows commonality is valuable, but few actually capture it. The difference is whether the verification process and the data structure have been turned into a system: part number as anchor, measurement as evidence, structured fields as presentation. Do those three things and return rates fall while inventory turns rise.

HAO-GUO has long supplied exterior parts for Japanese light commercial vehicles, including door handles, door hinges, latches and hood locks, and can provide part-number cross-reference and dimensional information for specific models so that buyers can complete verification before making a consolidation decision.