Start standup from a health score
Why marketplace catalogs need one ranked list, and what the morning looks like when the score is honest.
The signals that predict a listing suppression already exist. They sit in half a dozen reports nobody reads until sales dip. That is the most expensive way to find out.
One number the team can argue about
Pull the reports into one place. Reduce them to a health score per listing. Weight content completeness, variant integrity, policy flags, and inventory. Rank the catalog by risk. Explain the factors that drag each score down.
Standup starts from that list. Not from a hunch. Not from who shouted last.
What the agent does not do
It does not push a fix unattended. Catalog QA that writes back through SP-API still waits on a person. The dashboard's job is to be read before the suppression. The approval queue is a different job.
Why this is starter-shaped
A ranked list, a score, and the notes to run it. That is the shape of a starter. Nothing on this site sells that file yet. The case study is already public.
Want this run for your operation?
This playbook comes straight from client work. If you'd rather have it done than do it, that's what JS Labs is for.
GET IN TOUCH