# When two product catalogs use different naming systems, how should customer identification relationships be retained before merging the website?

Source: https://www.jvds.cn/en/share/website-design/catalog-merge-name-correspondence
Language: en
Published: 2026-10-08
Author: JVDS Design Studio

Mapping names when merging product catalogs starts with confirming what different terms refer to. Two catalogs may use different series names, model formats, or sales short names. Keeping only the tidier set when merging pages may prevent existing customers finding familiar products; treating every similar name as a synonym may combine different products incorrectly.

Organizing mappings concerns material meaning, not just string replacement. Retain sources and context, have product owners check them, then decide the public explanation. This article focuses on name recognition rather than database migration, redirects, or automated merging programs. See [How to Migrate a Website Without Losing Content](https://www.jvds.cn/en/share/website-design/website-cms-tech-migration) for related checks.

## Retain original names first to identify what customers recognize

Collect model numbers, series names, former names, and abbreviations from actual materials, noting their catalog locations and product subjects. Customers may still hold old promotional material. Extracting names only from current pages does not establish that historical terms have no purpose.

Separate formal model numbers from descriptive names. An understandable product term may cover multiple specific objects, and an internal code may be unsuitable externally. The company confirms relationships; standardizing names does not authorize redefining model numbers.

Identical wording can have different contexts. A series name in one place and a specific product name elsewhere lose hierarchy if merged. Different wording may refer to the same object, which needs material-based checking. Editors record differences before using similarity to decide real relationships.

Sources should be traceable. A two-column “old name/new name” list without origins is insufficient. Material subjects and historical purposes help professionals assess mappings, especially when several names are similar and text alone can lead to errors.

![Miniature scene distinguishing different names for one object from similar names for different products](https://www.jvds.cn/upload/2026/1004/1791058816835-496711.webp)

## Checking whether the subject is identical matters more than choosing a pleasing name

Place names beside their product materials, known model numbers, and scope, then ask owners whether they describe the same object. Retain unresolved status when more materials are needed; similar photos or word lengths are no basis for merging.

When one object has several names, explain the usage relationship: the formal name, the context of an old name, and how current content supports recognition. Not every former name must remain permanently in the title, nor can a new name replace every historical record.

Clarify differences when distinct objects have similar names. One small model-number difference may represent a real configuration difference. Do not remove it for layout consistency without evidence. Website expression can aid understanding but cannot change product identity.

Suppose two catalogs use an old series term and a current name, but one similar model actually represents another object. Confirm recognition mappings for the former while retaining the latter's distinction. This illustrates semantic checking, without implying any actual corporate renaming or product replacement.

## Mapping results include more than “merge”

The result may be different names for the same object, different objects, or an unresolved relationship. Each has its next step: explain the same object accurately, preserve differences, or supplement materials. Do not force every item into a one-to-one new name merely to tidy the list.

If a series contains models, record the hierarchy instead of claiming equality. Customers searching a series may need to identify a specific object next. Pages can provide explanations without mapping a broad series directly to an arbitrary single model.

Abbreviations may become ambiguous across contexts. Confirm what each means in its materials and explain publicly where needed. Every abbreviation need not enter the main title, but maintainers should know expressions customers may still use so later checking finds the context.

Name mapping differs from replacement relationships. Two products appearing sequentially do not establish that the new one replaces the old one merely because an old catalog name is no longer adopted. Identity and permissible replacement each need their own evidence. This article preserves name meaning without technical conclusions.

![Miniature scene connecting identification clues in old materials with current product subjects](https://www.jvds.cn/upload/2026/1004/1791058816835-597475.webp)

## Public treatment of former names depends on customer recognition tasks

If existing customers commonly search using old materials, current content can supply accurate former-name relationships with company-approved wording. Explain the historical or alternative term so readers do not mistake two names for two products offered simultaneously.

Old names need not repeat everywhere. Specific product identity can carry recognition explanations while catalog overviews use current names; place detailed relationships where reading suits them. Usage rules should be explainable. Do not stack every similar term into titles merely for search coverage.

When a relationship is unconfirmed, provide a usable checking method. Users can state the original material's name or known model number for product staff to identify. The page should not return an apparently matching current product while hiding uncertainty over whether it is actually the same one.

When historical materials retain old names, current readers also need to understand their scope. Establishing relationships does not require rewriting every file, but pages and opened materials should not appear unrelated. Material owners determine usage without editors changing historical facts themselves.

## A mapping record should tell later staff what evidence supports it

Retain the original term, source subject, current adopted name, confirmed relationship, and remaining questions. This need not be a long public table; it helps the next editor understand the reason. “Standardized” alone can lead to repeated errors with similar models and conceal whether the original name was a series-level term.

State the scope when confirming relationships. Different series names across two catalogs do not prove a one-to-one match of every model. Confirmation of one product cannot establish that two whole catalogs are identical. Conclusions attached to actual objects prevent later searches following an overbroad merger rule.

When new materials contradict current records, inspect their sources and contexts. They may involve historical terms, another configuration, or an organization error. Retain existing evidence and the new question for owners to check. Prior standardization should not exclude new facts, and the last file received should not overwrite every relationship automatically.

## Combining two catalogs does not establish one common set of facts

Even matching names may retain differences in document versions, usage scope, or product descriptions. Placing them together is an organizing action, not automatic proof of current validity. Resolve contradictions through subjects and evidence instead of choosing the last-received file to overwrite the other.

Check image and attachment identities too. A former-name mapping does not confirm that its old image remains usable. Different objects should not directly share materials simply because they look similar. Name organization should preserve further questions instead of silently expanding into asset replacement.

When teams use different short names, collect actual terms and confirm public usage and internal identification relationships. Pages need not show every internal word, but sales should not keep sending materials impossible to compare with the current catalog. Explain relationships first, then arrange usage individually.

This scope covers only inspected materials. If another historical catalog has not been read, completing two current catalogs does not establish universal naming consistency. Retain sources and conclusions and check later additions, instead of relying on personal memory to decide identical subjects.

## Check mapping clarity through an existing customer's search task

Prepare constructed material using an old name and ask someone uninvolved in organization to find the current product. Observe whether they confirm one object or mistake two names for two products. Avoid real customer materials and do not assume every site has automatic alias search.

Then provide a pair of similar names representing different products and check whether explanations retain their differences. If users infer interchangeability from similar wording, add identity and scope rather than making the names even more alike. Correct distinctions sometimes matter more than uniformity.

Also test an unresolved name: can users recognize that checking is required instead of receiving false certainty? Receiving staff should continue assessment using retained sources. Update adopted records after confirming identity so unknowns do not quietly disappear during website merging.

Product-catalog name mapping is complete when sources are traceable, subject relationships have evidence, existing customers can identify products, and similar names have not been merged incorrectly. The website gains an accurate identification path beyond standardized text formatting. See [How to Design a Manufacturing Product Catalog](https://www.jvds.cn/en/share/website-design/manufacturing-product-catalog-design) for related checks.

![Miniature scene rehearsing same-object, different-object, and pending name relationships](https://www.jvds.cn/upload/2026/1004/1791058816835-429717.webp)

## Frequently Asked Questions

### Can products be merged directly when names match?

Not from wording alone. Check objects, materials, and hierarchy first; identical series and model names may have different meanings.

### Should all old names be removed from the new site?

Follow customer recognition needs. Confirmed historical relationships can retain suitable explanations without repetition everywhere or erasing necessary clues.

### Does name mapping establish that a new model can replace an old one?

That cannot be inferred. Recognition relationships and technical replacement are different judgments; the latter needs professional evidence.

### What if the site lacks alias search?

Clear name explanations and real checking contacts can support identification first. Do not claim automatic capabilities already exist.

### Can two names be merged before their relationship is known?

Retain pending status and sources. Insufficient materials should not create a certain mapping; first add evidence capable of identifying the objects.