Why cron, not a big red button
One-shot “rewrite everything” blows rate limits and trust. A minute cron gives steady throughput and time to spot bad batches before they publish everywhere.
WordPress plugin · my tooling · Plugin
Catalog teams drown in thin copy. Blind AI dumps are dangerous; pure manual is too slow. I wrote a plugin that rewrites Woo descriptions on a minute cron, shows status in admin, tags what the model touched, and lets humans override any single product.
My role Plugin author — cron pipeline, admin UX, override model, tagging.
Merchants wanted GPT help without waking up to a thousand hallucinated descriptions and no audit trail.
Scheduled GPT-3.5 jobs, admin status column, gpt-updated taxonomy/tagging, and per-product manual overrides so the model never gets the last word by default.
Bulk description quality with a human brake pedal — the same pattern I reused conceptually across Bondi catalog work.
One-shot “rewrite everything” blows rate limits and trust. A minute cron gives steady throughput and time to spot bad batches before they publish everywhere.
AI without an escape hatch is a liability. The status column and manual path exist so merchants can keep brand voice on hero SKUs.
Steady rewrite throughput instead of API spam.
See what ran, what’s pending, what failed — in Woo, not a spreadsheet.
Per-product manual control when the model is wrong.