Features

How to Share Product Data Across Brand Websites: Field Ownership and Release Checklist

Share product data across brand or regional websites with clear field ownership, stable product IDs, site mapping and a release checklist for specifications and

When several brand or regional websites publish the same products, assign each product a stable identifier and give every field an owner. Headquarters maintains approved shared specifications, site editors maintain local page content, and regional owners sign off on market availability and certificates. For each change, list the target sites, languages, fields and reviewers, then check the version visitors actually see.

This guide is for companies that share product information across websites with separate editorial teams. See the multi-site CMS guide for site and domain setup and the product catalog guide for categories, detail pages and filters within a site.

1. Create a field ownership register

Choose one real model and compare its live pages, manuals and technical records. For each field, document who supplies the value, which sites and languages can use it, and who approves changes. For specifications, retain the source unit, applicable product version and approval date.

Example fieldOwnerRelease rule
Model and ratingsCentral engineeringUse the approved version for each model
Title, case study, inquiry linkSite editorAdapt for the local audience and language
Certificates and availabilityRegional leadCheck market, dates and files

Ownership can be split even within one asset. Headquarters can supply the approved drawing while the site editor writes the local download label. When manuals differ by market or product version, record exactly which file applies. See manual and certificate version management.

2. Link site records using a stable product ID

Give each independently maintained product or variant a stable ID. Titles, translated names and URLs can vary by site; connect them to the master record through a mapping register. Use one row per product and site. Record the site, CMS record ID, enabled languages, public URLs for those languages, latest applied product data revision and owner.

Use that register to distinguish the same product on two sites, two language pages on one site, and similar models with different specifications or certificates. Mark ambiguous records, unapproved destinations and mismatched models as pending until their owner confirms the mapping. Add the mapping and publication scope before expanding to another site or language.

3. Choose a workflow based on change frequency

  • Few shared fields and infrequent changes: Keep approved values in a controlled spreadsheet or existing master record. Give each editor a release checklist and collect the published revision and URL. Time one real update and track missed changes before investing in automation.
  • Existing PIM or ERP: Keep established sources of record. For example, a product information management system (PIM) can supply approved specifications and assets while the website CMS holds local introductions and inquiry links. Confirm destination filters, field mapping and file revisions before estimating integration work.
  • Frequent changes across several sites: Pilot a batch of products and compare the cost of manual updates, review and rework with the cost of running an integration. Specify writable fields, allowed sites, what happens when a batch runs twice, and how failures are handled. Assign each field one authoritative editing source.

The Pimcore implementation guide describes centralizing product data and selecting what to distribute to each channel. Use that principle to clarify fields and destinations before choosing whether to add a dedicated PIM.

4. Example: a revision goes to two sites

In this fictional example, the master product ID is DV-310. Engineering approves a wiring drawing update from R4 to R5. Group site A and export site B show the same hardware version. Regional site C shows a different version and keeps its separately approved drawing. Only A and B are on the change list. Each has Chinese and English pages, so four pages need release checks.

  1. Engineering supplies the R5 drawing, applicable hardware version and effective date. Editors check the download label in each language and retain their local case studies and inquiry links.
  2. Try the update on a test copy of site A. Open the file from both language pages and verify the R5 mark inside the drawing. Compare the other fields on each page with their original values.
  3. After the sample passes, publish to the live A and B sites. Open both language pages on each site and verify R5. On site C, verify that the prior drawing and local notes still appear. Close the batch with links for A, B and C, observed revisions, outcomes and reviewers.

5. Record the scope and outcome of each release

  1. Before release: Save prior values, file URLs and revisions. List the sites, records, languages and fields to change, including which sites should keep their existing revisions.
  2. Pilot: Try one real model in a test environment. Pause the affected item if a record is missing, the destination is wrong, or the units conflict. Send it to its owner for review.
  3. After release: Read each stored record back and open the public pages. Check specifications, units, files, language links and local inquiry routes. Record verified, pending review or failed, with the next owner.
  4. When something goes wrong: Pause the affected batch. Compare the original, submitted and current values. Preserve valid intervening edits and repair the affected fields per site. Use the bulk edit recovery checklist for the full procedure.

6. What can CatchCMS handle?

CatchCMS supports multiple sites within one instance, with content and languages managed per site. Content models and dynamic fields can organize product identifiers, specifications and asset revisions for a project. Multilingual editing supports page copy and fields configured for translation. Admin accounts can be assigned access by site and function.

A headquarters master catalog, automatic distribution, source system connectors, inheritance rules and central approval need project design and implementation. A small team can start with a shared register and sign-off per site. For a launch project, contact CatchCMS with your site count, languages, data sources and a real sample change to scope CMS setup and integration work.

Frequently asked questions

Can two sites use different page titles for the same product ID?

Yes. The ID connects both pages to the master data. Editors can write titles for each language and audience. Verify model, specifications and asset revisions against the scope approved for that site.

Can a regional team change a specification owned by headquarters?

Send the proposed change and supporting evidence to the central owner. For an actual regional variant, document the model, sites and effective dates that the specification applies to, then approve it for release.

Do we need a PIM from day one?

For infrequent changes, start with a controlled register. Complete one update across your sites and track the effort. When several teams or channels frequently reuse specifications, assets and translations, use observed duplication and mistakes to evaluate a PIM or integration with your existing systems.