Launch checklist · Catalog Scout 1.0.3

Local proof

[ ] Extract the archive and compare it with package-manifest.json.
[ ] Double-click OPEN-ME-Catalog-Scout.html and click Try the sample batch. You should see 8 products, 10 facts drafted and a report download.
[ ] Load your own CSV and confirm the sample store name is cleared.
[ ] Node 20.19 or newer: run npm test (30 tests), npm run sample and npm run dry-run in source/.
[ ] Rerun the same input and confirm reused. Add rows above existing products and confirm they are not counted as new findings.
[ ] Run npm run evaluate and npm run gate, and read ACCURACY.md. Check a sample of findings on your first real batch.
[ ] Replace the BotMyBiz return links and keep the license notice.

[ ] Clear your business name and domain. No availability check is included.
[ ] Qualify prospects on whether their vendors send CSV/Excel line sheets.
[ ] Get permission for exports and line sheets, and agree how long you keep them.
[ ] Create private per-client folders (intake.json, inbox/, processed/, reports/) and a backup.
[ ] Get sending authorization before any outreach.
[ ] For 5 pilots, measure review minutes per batch, hours spent winning each pilot, and accepted versus wrong drafts.

[ ] Verify hosting, runner, email and payment terms and costs, and get approval for any spend.
[ ] If using the Shopify pull, test it on the merchant's own store with their own app. It has only been tested against a mock.
[ ] Set up billing and test a sandbox charge and refund. Keep test IDs separate from revenue.
[ ] Set up delivery, and test duplicate suppression.
[ ] Activate a scheduler for intake.mjs only after a manual run, and make sure stale alerts reach you.
[ ] Put measured numbers into ECONOMICS.csv, then pass the kill tests in FIRST-TEN-CUSTOMERS.md or re-scope.

Completion means observable evidence, not ticked boxes. This kit does not perform owner-account steps.