Your whole catalog,
not one product at a time

Why catalog work is a different problem

A one-off generator optimises for the best possible single image. That is the right goal when you are making an ad and the wrong one when you are making a thousand product shots. At catalog scale three things start to matter that nobody optimises for: the cost of the marginal asset, whether a run can happen without a human clicking through it, and whether the output lands back where your listings live.

That is the whole design brief here. Import a catalog by CSV or connect a store, pick the scenes once, and let the run happen. You are not sitting in a browser approving each frame.

What it costs when the volume is real

Per-video pricing is fine for a campaign and painful for a catalog. Product images run 1 credit each, so the arithmetic stays boring as the number of SKUs climbs — a 400-product catalog at six scenes each is a number you can work out before you start rather than a surprise at the end of the month.

Credits never expire. Buy for a seasonal push, use the remainder in six months. Nothing is forfeited because a quarter ended, which matters when catalog work is bursty by nature.

If your platform is not connected yet

The badges above are honest: some platforms are live, some are in beta, some are still being built. When yours is not ready, the REST API is — submit a batch of products, poll for completion, pull the URLs back. That is the same path our own integrations use, so nothing about it is a second-class route.

CSV import works regardless of platform. Export your catalog, run it, take the images wherever you need them.