> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to keep a product catalog consistent across channels
- URL: https://blog.jestor.com/keep-a-product-catalog-consistent/
- Published: 2026-09-16T18:56:32.000Z
- Updated: 2026-09-16T18:56:32.000Z
- Author: Bruno Bannach

To **maintain a product catalog** across several channels, decide which attributes are universal and which legitimately differ. In **Jestor**, the product is one record with shared attributes, and channel specific values are connected records rather than copies.

## Why catalogs diverge

Each channel needs its own description length, image format and category structure. The simplest response is a separate catalog per channel, and from that moment they drift.

A product is updated in one place, and customers on another channel see outdated information for months.

What one catalog with variations prevents:

- The same product described inconsistently
- Prices updated on one channel and not another
- Discontinued items still listed somewhere
- New products launched on one channel only
- No single answer to what you actually sell

## Shared or channel specific

| Attribute                      | Shared       | Channel specific             |
| ------------------------------ | ------------ | ---------------------------- |
| Product identity and code      | Yes          | No                           |
| Technical specification        | Yes          | No                           |
| Status, active or discontinued | Yes          | No                           |
| Description                    | Base version | Length and tone vary         |
| Category                       | Internal     | Each channel imposes its own |
| Price                          | Base price   | May differ per channel       |

## Step by step to structure it

1. **Create one product record** per real product.
2. **Hold universal attributes** on that record.
3. **Create channel records** connected to it for variations.
4. **Keep status universal**, so discontinuing removes it everywhere.
5. **Maintain the base description centrally**, adapting per channel.
6. **Map internal categories** to each channel's taxonomy.
7. **Report on channels missing a product**, which reveals gaps.

## Why status must be universal

Every other attribute can reasonably differ per channel. Status cannot: a discontinued product still listed on one channel generates orders you cannot fulfil, which is worse than not listing it at all. Keeping status on the shared record makes discontinuation a single action.

## Why choose Jestor

In **Jestor**, a product is one record with channel variations as connected records rather than duplicates, status lives on the shared record so it applies everywhere, and the catalog can mirror products from the **ERP**, which remains the registry of record.

## Frequently Asked Questions

### Should each channel have its own catalog?

No. One catalog with channel specific variations avoids drift. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Which attribute must never differ per channel?

Status, since a discontinued product still listed generates unfulfillable orders.

### Where does the product registry live?

Usually the ERP, mirrored into the operational layer.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.