Original demonstration / 001
A launch review,
with the workings.
Before a campaign goes live, small catalogue problems need clear answers. Here is what we found in a sample desk collection, and how each finding changes the launch decision.
The decision: hold launch.
7 source rows → 3 candidates / 4 heldTwo of the three candidates meet this example’s stock policy. None is upload-ready: the merchant identities and destinations are deliberate placeholders. A candidate record is a step in the review, not platform approval.
Every row has a next step.
Stocked variants with a stated currency
Keep as review candidates. The merchant still needs to verify the live price, selected variant, image and delivery market.
Zero stock
Keep the inventory fact and turn off advertising eligibility under this example’s stock policy. Confirm whether backorders are supported.
Price without a currency
Hold the row. Ask the merchant for the currency; do not infer it from neighbouring products.
One identifier, conflicting prices
Hold both rows until the merchant identifies the authoritative record. Do not silently pick one price.
Missing stable variant identifier
Hold the row until the merchant supplies the identifier. A temporary ID could break reporting continuity.
Product data is only part of readiness.
A real launch also needs purchase-measurement checks: a completed purchase, a retry or page refresh, two separate purchases, and a failed checkout must each produce the intended result. Order amount, currency, refunds and reporting delays need reconciliation.
These are proposed acceptance cases, not executed tests. Receiving a test event alone does not establish advertising attribution or incremental sales.
Inspect, then reproduce
The source is included.
The example contains the invented catalogue, candidate records, findings and a Python script. Download and extract the folder, then run python reproduce.py with Python 3. No packages, credentials, network or advertising spend are required.
ZIP · 5 files · Python 3, no dependencies
The checks verify the expected holds, stock exclusion and stable identity after a price change. The script is scoped to this fixture; it is not a complete validator for every product or currency. For live work, we recheck the current specification and actual advertiser account.