Amazon catalog management services

How the service runs

1. 01

   Export

   Current listings and attributes downloaded.

   Output: Live catalogue

2. 02

   Compare

   Checked against your product master.

   Output: Difference list

3. 03

   Plan

   Fixes grouped and approved by you.

   Output: Fix plan

4. 04

   Fix in bulk

   Changes uploaded by file; results checked.

   Output: Corrected catalogue

5. 05

   Control

   Change process and log handed over.

   Output: Stable catalogue

Differences the comparison finds

You approve the changes

Some catalogue changes affect how customers find and choose products, such as moving products between families or changing option names. Group proposed fixes by type, show examples and agree them with whoever owns the range before anything is uploaded. Make the low-risk fixes first, such as completing attributes, and the structural ones afterwards, checking each batch before the next.

Keep a copy of the catalogue as it was before changes.

Checking upload results

After every bulk upload, check how each row was processed and whether errors or warnings were reported. Fix the causes in the file and re-upload the affected rows. Errors ignored in one upload can reappear in the next. Afterwards, spot-check a sample of listings on Amazon to confirm they show what you expect.

What you should receive

Example: a homeware range

Warning signs in a proposal

• Changes made without your approval

  Families restructured in ways you did not expect.

• No comparison with your data

  Fixes based on guesses about what is right.

• One-by-one edits for large ranges

  Slow, inconsistent and hard to trace.

• No log of uploads

  Nobody can say what changed or when.

Fixing the product master first

The comparison sometimes shows that your own product data is incomplete or wrong, for example dimensions never measured or materials recorded inconsistently. Fix the product master first, because it is the source for every future upload, then update Amazon from it. Otherwise the same errors return the next time someone uploads a file. Where information is missing, ask suppliers or measure samples rather than guessing.

Agree who keeps the product master up to date as new products arrive.

Access during the work

Give the provider their own user access with permissions limited to catalogue work, and remove it when the engagement ends unless ongoing support is agreed. Keep the bulk files and log in a shared location you control, so the work stays usable after the provider leaves.

After the clean-up

Plan a short catalogue check each month: new products added correctly, families intact and attributes complete. The listing health audit pages describe a wider review that can be repeated a few times a year.

Working in batches

Upload changes in manageable batches, such as one product family or category at a time, and check each before the next. If something goes wrong, only a small part of the catalogue is affected and the cause is easier to find. Large single uploads save little time and make problems harder to trace.

Reusable templates

Keep the bulk file templates used in the clean-up, filled with your column mappings, so future uploads start from a known, working file.