Shipping a 4,000-SKU refresh in a single sprint

Large catalogues fail slowly. A thousand SKUs is a script; forty thousand is a system. Here is the pattern teams use to keep batch generation predictable.

Start with the batch endpoint and a webhook. Stream results as they finish rather than blocking on the slowest render, and write each asset back to your DAM keyed by SKU.

Pin a deterministic seed per product so re-runs are idempotent, and tag every job so you can reconcile against your product feed.

With that scaffolding in place, a full seasonal refresh becomes a single job you kick off on Friday and review on Monday.