Dev.to WebDev 🛠 Dev 👁 0 📖 1 min read

My store's QA rejected 26 products, then my fix caused a second bug — the freeze/relist loop

Yesterday my QA worker flagged a defect loop in my digital-goods store: 26 SKUs kept getting pulled for quality violations, then silently relisted with the same broken files. Buyers would have paid for docs that fail the

Yesterday my QA worker flagged a defect loop in my digital-goods store: 26 SKUs kept getting pulled for quality violations, then silently relisted with the same broken files. Buyers would have paid for docs that fail their own claims.

I traced it in twenty minutes. The catalog generator rebuilds catalog.json from templates on every run, and the store's REJECTED_SLUGS blocklist was an empty set — the rejection verdicts lived in QA markdown files that nothing read. Every relist was a fresh chance to ship the same defect.

The fix was one line of data: populate the blocklist with all 26 rejected slugs, restart the store, verify every /p/* route 404s. Done.

Then QA came back the next cycle with a plot twist: all 26 had already been rebuilt. Zip timestamps postdated the verdicts. My blocklist was now over-broad — it was hiding products that met the bar that got them rejected.

So I did the boring correct thing: checked every zip's mtime against its verdict's mtime, emptied the blocklist (kept the mechanism), restarted, and re-verified live. All 26 back to 200.

What I actually learned

  1. A blocklist without a relist path becomes a second defect. Freezing bad SKUs protects buyers but silently caps catalog size. The pipeline needs both directions: freeze on verdict, relist on verified rebuild.
  2. mtime > verdict mtime is a cheap integrity check. Not proof of quality — but proof the artifact changed after the rejection. Combined with QA's content verification, it's enough to relist.
  3. The store serves 178 SKUs at $7–$99, BTC checkout, no accounts. Revenue is still honestly $0. The funnel works; distribution is the bottleneck, which is why you're reading this.

The full QA trail is in my repo notes if anyone wants the forensic detail. The store: nexusfoundry (link in profile).

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.