A feed audit should separate errors from opportunities
Blocking errors, invalid identifiers and missing required values are different from optimisation opportunities such as weak titles or thin product types. Treating them as one list makes prioritisation harder.
Audit the source and output separately
A clean source file can still become a weak channel feed because of mapping, transformation or destination rules. Feednetic grades the stages separately so teams can see where quality changed.
Look for patterns, not just individual rows
The useful output of an audit is often a repeatable rule. If 8,000 titles share the same structural weakness, the solution is a transformation pattern, not 8,000 manual edits.
Use the audit as a baseline
A before-and-after grade gives the team evidence that the feed changed materially and helps prevent the same issues returning after future source updates.