4
Components in the finished document
Product Feed Optimisation
Product data mapped and cleaned so shopping and marketplace surfaces accept and rank it.
Where This Sits
1
Measured directly, not asserted
3
Pieces that carry my judgment
This is a Specification and build deliverable, which means it specifies a change precisely enough to build. It is the unit of scope: it can be commissioned on its own, priced on its own, and accepted on its own, whether or not anything else is bought alongside it.
It is not a package and not a retainer. It is one document with 4 components, and the list below is the whole of it.
What Is Inside It
Every component is listed with the one sentence that says what it is. They are grouped by how each one is produced, because the difference between a number a tool gave me and a number I decided matters more than most reports admit.
Measured
Pulled straight from tools and logs. No interpretation, so you can re-run any of it yourself and get the same numbers.
- Test result log
- Evidence each item returns the correct response and lands where it should.
Judged
My reading of the evidence. This is the part you are actually paying for, and the part you are entitled to argue with.
- Feed field mapping
- How source product data maps to each required output field.
- Feed validation report
- Errors and warnings in the generated feed, grouped by field and severity.
- Exceptions list
- Items deliberately left out, with the reason, so the decision is not mistaken for an oversight.