GUIDE · BEST PRACTICES
Catalog best practices: what the cleanest supplier files do differently
The suppliers whose files sail through validation do a short list of unglamorous things on every submission. None of them require special tooling, and every one of them exists because skipping it produces a specific, expensive failure. This is that list — the standard we hold our own work to, written for the brand that wants to hold its catalog to the same.
1. Declare the reference-database versions you actually used
Every ACES file states which releases of the vehicle and qualifier databases it was built against, and those databases update monthly. A file validated against one release and declared against another is the classic source of phantom errors: IDs that were valid when mapped and orphaned by the time of submission. Record the release with the work, and revalidate when you upgrade.
2. Qualifiers, not notes
If a distinction can be expressed as a coded qualifier or a structured vehicle attribute, it belongs there. Free-text notes are where fitment knowledge goes to hide: humans read them, validators do not, and every note that carries real fitment logic is a future overlap flag. We once converted 555,583 free-text notes to zero on a single brand's catalog — every surviving distinction re-expressed in structured form, with a map of what every note became. That is the end state to aim for, even if you walk there gradually.
3. Clear conflicts by correction, never by deletion
Overlap and duplicate flags tempt the fastest fix: remove records until the report is green. Every removed record is a vehicle you no longer sell against. Resolve each conflict by fixing the wrong record or differentiating the right ones — and measure success as zero flags with coverage preserved, not zero flags alone.
4. Validate before submission, every time
The cheapest rejection is the one that never leaves your building. Run schema validation plus the known failure modes — stale vehicle IDs, invalid part-type and position combinations, overlap and duplicate detection, qualifier syntax — before the receiver does. An official validation pass is also an asset: when a trading partner claims your data is bad, a current zero-error assessment is the defense. We have used exactly that to disprove an 81,346-record accusation.
5. Know your receiver's dialect
The standard is one thing; each receiver's implementation of it is another. Confirm per partner: which ACES and PIES versions they ingest (most still take 4.2 / 7.x even though 5.0 / 8.0 are released), whether they expect full or incremental files, which description codes and lengths they mandate, and their image specifications. When a receiver's spec sheet disagrees with the standard, the spec sheet wins — they are the ones rejecting the file.
6. Keep product data as honest as fitment data
On the PIES side, the same discipline applies: attribute values drawn from the official attribute database rather than invented, distinct descriptions per coded type instead of one blob pasted five times, package dimensions a shipping system can trust, and interchange records treated with the caution they deserve — a wrong cross-reference sells your part into a failure.
7. Log everything you change
A catalog cleanup you cannot explain is a catalog cleanup you cannot defend. Every transformation — note converted, record corrected, duplicate collapsed — should leave a row in a log: before, after, why. It turns the next receiver dispute into a lookup instead of a crisis, and it is how we hand work back to clients: the clean file, plus the ledger of exactly what changed.
8. Audit on a cadence, not after a rejection
Catalogs decay quietly — new SKUs, new model years, monthly database releases — and the brands that stay clean check quarterly instead of reacting annually. If you want a baseline today, our graded audit is free, returns in 24–48 hours, and names your top problems with the records behind them. The grade you get is the same scale we use to prove our own work: one brand went from an F (34) to an A (97) on it.
Frequently asked questions
Which ACES and PIES versions should we build to?
The version each receiver actually ingests. ACES 5.0 and PIES 8.0 were released in April 2026, but most trading partners still take ACES 4.2 and PIES 7.x. Confirm per receiver before building, and never ship a newer version to a partner that has not announced support.
How often should a catalog be audited?
Quarterly is the practical cadence for most suppliers — enough to catch decay from new SKUs, model-year expansions, and monthly reference-database releases before any receiver does. At minimum, validate before every submission.
What does a good catalog cleanup deliverable look like?
Two files: the clean, validated catalog, and the log of every change made to produce it — each converted note, corrected record, and collapsed duplicate with its reason. If a provider cannot hand you the second file, the first one is a black box.
Do we need to license the Auto Care databases ourselves?
Yes — the VCdb, PCdb, Qdb and PAdb are licensed by each brand directly from the Auto Care Association, and your catalog work happens within that license. A provider should work inside your licenses, not resell database content.
FIND OUT WHERE YOU STAND
Get your catalog graded — free, in 24–48 hours.
Send a file, get back a letter grade and your top problems: overlaps, duplicates, notes that should be qualifiers, and the exact records behind each flag. No obligation, no black box.