Catch catalogue errors before a move

How we help

Before and after

A catalogue migration looks tidy until the target rejects a missing SKU, a repeated code or a price in the wrong format.

You receive a trial file, a list of rows needing attention and a checklist for rerunning the check before the live import.

A worked example

Two sizes share the same SKU and a sale price contains an unexpected text value. The rehearsal shows which rows are affected and how their source and target fields line up.

What you receive

A field map and prepared trial import file
An exceptions report for the sample
A checklist to repeat the rehearsal with another sample

Where your team stays involved

Your catalogue owner decides which SKU is authoritative and approves any corrections before the live move.

One source export, one target template and up to 100 de-identified sample rows. Production import and full catalogue cleanup sit outside the rehearsal.

Starting the conversation

Tell us which catalogue is moving, the destination and one field you expect to be troublesome.

Ways we can help

Rehearse the catalogue import

Ask for a price

Test a sample against one destination template. Receive the field map, trial file, exceptions and repeatable checklist.

What you receive

The field map, a prepared trial catalogue file, an exceptions report and a repeatable checklist.

Plan the catalogue change first

£195 one-off

If the migration route is undecided, map the current workflow and choose where a rehearsal would help.

What you receive

A map of the catalogue change, key checks and a proposed first step.