Product Data and Catalogue Management: One Source of Truth

A single source means each piece of information is edited in one place and everywhere else is fed from it. When a price changes, you change it once, and the site, the marketplace and the quotation document update themselves. With several sources, every change becomes several manual edits, and one of them is always forgotten.

The cost of a forgotten update reaches the customer. An order arrives at an old marketplace price, an item shows as in stock on the site after it has sold out, the same product has different dimensions on two channels and becomes a reason for a return. Each error is small; together they wear away trust and margin.

A single source also protects your team's time. Instead of preparing products from scratch for each new channel, you convert the existing data into that channel's format.

Set the field list by the strictest channel. Marketplaces usually demand brand, barcode, category and required attribute fields, while your own site also needs attribute values for search and filtering. If you collect the richest version once, supplying plainer channels is easy; doing it the other way round means gathering the data again.

Give every product a unique identifier and never reuse it. A stock code, a barcode and a web address are not the same thing; they should sit side by side in the same record so that if one changes, the record does not break.

• A unique product identifier and stock code
• Brand, barcode and category
• Name, short and long description
• Variants such as colour, size and dimensions, each with its own code
• Images: main image, extra images, order and alternative text
• Price, currency and tax information, with a separate field where a channel has its own pricing rule

Every field needs an owner. Management or sales sets the price, the warehouse supplies stock, the content team writes the description, the photography team prepares the images. A field with no owner decays over time; if everyone can edit it, nobody is responsible.

Limit editing rights. A setup where everyone can read but only the owner can change cuts errors off at the start. If changes are logged, then when something goes wrong you can see who changed what and when.

In a small team the ownership may sit with one person; what matters is that it is written down. A team that knows who does what does not stumble over a holiday or a departure.

Each marketplace has its own category tree, required fields and image rules. The most robust approach is to hold your data in one format and prepare a mapping table for each channel: which category of yours corresponds to which category there, which of your attribute names is which of their fields. The mapping is built once and new products fit automatically.

To automate the transfer you can use the integration routes the marketplace offers; as these change over time, check the current documentation. Until an integration exists, a spreadsheet transfer can be a stopgap, provided the spreadsheet is an output generated from the source rather than the source itself.

Keep channel-specific content separate. Title length and keyword conventions differ on marketplaces; copying the site description unchanged performs poorly there and can create duplicate content problems in search engines.

With a few hundred products and one or two channels, a well-built spreadsheet or your shop's own panel is usually enough. A separate PIM starts to make sense with thousands of products, many variants, several languages, many channels and several people entering data at once.

Before choosing a tool, write down the need: how many products, how many channels, how many languages, who enters data, where the data comes from. If the answers point to a process rather than a tool, build the process first. A tool solves a complicated problem, but it does not make untidy data tidy; it only keeps it in a more expensive place.

The commonest mistake is collecting data and never cleaning it. If one brand is entered with three spellings and one colour with five names, filters and mappings break. Build a shared vocabulary first: brand names, colour names and units written one way.

The second is forgetting images. The text is tidy but the photographs have different sizes and backgrounds, and the catalogue looks scattered. Image size and naming rules are part of the data rules.

The third is being unable to undo a change. Before a bulk price or description update, back up the current state; one wrong bulk operation can damage hundreds of products.

• No shared vocabulary for brand, colour and size
• Typing the same information by hand in several places
• Not taking a backup before a bulk update
• Copying site text unchanged to a marketplace

If you have few products and sell through a single channel, a separate catalogue system is unnecessary. Your site's panel is the source; all you need is to fill the fields consistently. A heavy setup introduced too early creates work for the team and nobody uses it.

Do not change the source structure in the middle of a large migration, a platform change or a busy campaign period either. Document the current state first, then move in a calm period. If you want to review your site's titles and descriptions, you can use our meta tag generator.