Season rollovers
Move thousands of products between seasonal collections on a date (SS26 out, FW26 in) with the tags your theme and ads depend on.
See the template →Drops, sales, markdowns, collection rollovers: apparel is bulk changes on a calendar. Collaudo runs them from a plain-English brief, and rehearses every change on your real catalog before it goes live.
Move thousands of products between seasonal collections on a date (SS26 out, FW26 in) with the tags your theme and ads depend on.
See the template →Tag what's new for exactly N days, then untag it automatically. Your 'New in' collection stays honest without anyone touching it.
See the template →Mark down a whole collection with charm pricing and a margin floor, and roll it back when the event ends.
See the template →Tag every product that's genuinely discounted and untag it when the promo ends, so the sale collection never lies.
See the template →Flag every variant a markdown would push below your floor before the price changes, not after the weekend.
See the template →Tag products running low on core sizes so merchandising sees broken size runs before customers do.
See the template →Runs on the full catalog with writes held. You approve the report, then it goes live. How the dry run works →
Yes: that is the shape of job it exists for. The automation walks the entire catalog, computes every tag and collection change, and shows you the full list before anything is applied. A 3,000-product rollover reads the same as a 30-product one: one report, one approval.
Whatever you decide, and nothing before you decide it. The dry run lists every product whose tags would change, so you can check the collections and feeds that depend on them before approving. Nothing writes until then.
Yes: on a schedule, on an event (like a product update), or on demand. A drop that goes live every Thursday at 09:00 is one sentence in the brief.
Describe the job, watch the AI build it, rehearse it, deploy it.
Free plan · no card · 🇪🇺 EU data residency