A catalog team can ship an ACES file that looks finished. Every part number has applications. The record count is high. The receiver accepted the file.
Returns still arrive.
That happens because completeness and correctness are different problems. Completeness asks whether an application exists. Correctness asks whether that application belongs on that vehicle configuration—and whether a technician using a lookup will get the part that actually fits.
Three patterns show up often.
Over-mapping. Applications are added “to be safe.” The part appears on engines, submodels, or years where it does not belong. Lookup succeeds. Installation fails. The return is coded as a catalog error even if the warehouse shipped exactly what the lookup requested.
Stale vehicle configuration. Auto Care vehicle data moves. An application that was valid against an older configuration can survive in a file long after the make/model/engine combination has been refined. The file is still “complete.” The configuration is no longer the one the receiver is using.
Unchecked supplier fitment. Inbound supplier ACES is ingested because it is easier than reviewing it. Supplier over-mapping becomes your published over-mapping. Your brand carries the return rate.
A useful review does not start with “how many applications do we have?” It starts with samples: known problem SKUs, high-return SKUs, and a supplier whose files historically need cleanup. Compare those applications to the current vehicle configuration and to the fitment your product team believes is true.
If those three sources disagree, the file is not ready—no matter how complete it looks.
InterWest Technology Group reviews ACES and PIES files for Auto Care compliance and for this kind of practical correctness: your data, your internal records, and the files your suppliers send.
InterWest Technology Group 