What’s inside: output checking · company memory
The question this file answersWho checks that the shelf label, the PIM and the site show the same price before the promo goes live?
Fits: retailers publishing hundreds to thousands of SKU updates a month.
Typical pattern, not a measured team — the e-commerce playbook counts catalogue updates in hundreds to thousands of SKUs a month, with no separate volume for promotions. A promo spreadsheet, the PIM and the live site disagree; a merchandiser reconciles them by hand weekly, and a customer finds the mismatch.
On Thursday the merchandiser opens a review list of the conflicts — a handful of lines, not the whole promo — and the rest is already staged in the PIM for go-live. The margin conversation still happens; the copy-paste does not.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
promo file, PIM and site compared line by line — the same build as our catalogue file; no published figure for promotions
Before: a merchandiser rebuilds prices by hand every Thursday. After: the three sources are compared line by line and only the conflicts wait for a decision. The percentage stays on the catalogue file.
Nobody has published a figure for promotional price synchronisation. Forrester's (2023) 40–60% faster time-to-publish and the Salsify/Akeneo 50%+ on attribute entry both describe catalogue enrichment and stay on the parent file. Not a margin claim.
Your PIM and shop platform stay — Akeneo, Salsify, Plytix and Shopify, Magento or the ones you run. The supplier-catalogue build is run against prices instead of attributes:
Brand decisions. Margin arguments. The promotion that is really a story, not a price.
Not a margin claim.
If the PIM and the shop platform hold different SKU codes for the same item, the match fails until an alias table exists — that is the first fortnight's work. Channels without a price API need a file upload, and go-live timing then depends on the platform's sync. Forrester's 40–60% concerns catalogue enrichment and belongs to the parent file — promotions have no figure of their own — and brand or margin calls stay with a person.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Ops.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.