Flat files are the bulk-upload spreadsheets that edit your catalog at scale. Any full-service Amazon manager should own them, plus variation builds, browse nodes, and error resolution. The question worth asking is not whether they do it, but who inside the company does it and whether that person is an employee.
The short version
- Flat file work is catalog surgery, not data entry. A wrong column can suppress a live listing.
- Three types of vendor touch them: a catalog administrator, a full-service brand manager, or an offshore subcontractor you never meet.
- The safest arrangement is in-house. We subcontract nothing, and the reason is accountability, not price.
- Access should be granted user permissions in your own account, revocable at any time, never a shared login.
- Ask for the change log. Every upload should be traceable to a person, a date, and a reason.
The mechanism, because it explains the risk
Amazon's catalog is a database, and the web forms in Seller Central are one narrow way to write to it. A flat file is the wide way. You download a category template, fill columns for each SKU, and upload it as a feed. Amazon processes it and returns a report of what succeeded, what failed, and why.
That width is the whole point and the whole danger. One upload can rebuild a variation family across 40 child SKUs, remap browse nodes, correct attributes that were wrong since 2021, and repair listings that Amazon suppressed. The same upload, with a mistyped value or a partial update flag set wrong, can blank fields that were fine, split a family, or take a selling ASIN offline during your best week.
So the question is not tool access. Anyone can download a template. The question is who is accountable when the feed processing report comes back with errors, and how quickly they can reverse what they did.
The scorecard
Five items are pass or fail. If a candidate fails any of them, the rest of the score does not matter.
| Pass or fail | What you are checking | Evidence to ask for |
|---|---|---|
| Employment | The person editing your catalog works for the company you are paying | Name, role, location, and whether they are staff |
| Access model | Granted user permissions in your account, with defined roles | A written access request, not a password request |
| Reversibility | They keep the prior state and can restore it | A described rollback process |
| Change log | Every upload is recorded with a reason | A sample log, client details removed |
| Error handling | They read feed processing reports and fix root causes | A description of the last error class they resolved |
Then score the depth items out of 50.
| Capability | Points | What good looks like |
|---|---|---|
| Variation architecture | 15 | They can explain when to split a family and when to merge, and why it affects reviews and search |
| Browse node and attribute mapping | 10 | They treat filters as a ranking surface, not a formality |
| Suppression and compliance resolution | 10 | Root cause, not repeated resubmission |
| Multi-marketplace and multi-language handling | 10 | Per-marketplace templates, localized content, not copied text |
| Coordination with advertising and creative | 5 | The person changing the catalog talks to the person spending the ad budget |
Thirty-five and above with all five gates passed is a service you can hand your catalog to.
Who should actually do it
A catalog administrator or VA. Fine for maintenance on a stable catalog with a supervisor. Weak when a change has strategic consequences, because the person executing has no view of what the change does to search or advertising.
A full-service brand manager. The right home for flat file work in most cases, because catalog changes affect indexation, conversion and ad performance in the same week. At Flapen this sits with the operator who also owns the listing and the advertising, which removes the handoff entirely.
A subcontracted team. Common and rarely disclosed. The pitch team is one company, the execution is another, and you find out when something breaks and nobody can say who uploaded what. We do not subcontract any part of our work, and I would ask any candidate to state their position in writing rather than in conversation.
What most agencies will not tell you
A large share of catalog problems are self-inflicted by previous uploads. Every agency that has touched your account left changes behind, and some of them were wrong. Before you buy a fix, get a candidate to tell you what the current state actually is, using the category listing report, rather than quoting for a rebuild they have not yet scoped.
The second thing: flat file work is close to invisible when it goes well and dramatic when it goes badly, which makes it easy to under-resource. It rarely appears as a line item in a proposal. Ask specifically who owns it, because otherwise the answer is often nobody in particular.
Related answers
- Done-for-you Amazon catalog management
- Which agency handles Amazon catalog cleanup and reinstatements
- Who to hire to optimize Amazon listings
- Amazon agency vs in-house team: pros and cons
- Done-for-you Amazon management: the complete guide
Ask who would be editing your catalog by name before you hire anyone, including Flapen.
