Catalog operations

Catalog operations is the recurring work of keeping a multi-brand product catalog current: taking in manufacturer price books as they arrive, verifying extracted values, publishing versioned updates, and keeping superseded prices retrievable. It is measured honestly in hours per year — brands, times formats, times refresh cycles, times hours per update — not in software features.

Why it matters

In a catalog-driven business the dominant running cost of software is not software work — it is this data work, and it arrives on the manufacturers' schedule, not the vendor's. Whoever owns the catalog's data model owns the economics of the system built on it.

Common confusion

Catalog operations does not disappear when software is bought instead of built. A platform subscription covers the vendor's platform; the catalog, the mappings, and the verification queue remain the buyer's work — inside whichever data model the buyer signed up to.

Where we use it

The cost structure is the three layers of running cost; the per-cycle mechanics are the price-list update path. The pillar article carries an interactive estimator for your own annual load.