Shopify's 1,000 videos per store per week: plan a Sume batch

Shopify's product media page says apps can create up to 1,000 videos for each store in a week. If your own app uploads generated clips, keep one Sume job per video and a running count, so the number of jobs you submit matches the number of videos you plan to upload.

What exactly does Shopify limit?

The page read on 2026-09-30 says: apps can create up to 1,000 videos for each store in a week. It does not say how the week is counted or what happens at the limit, so treat the number as a hard ceiling and stay under it. Spread evenly, 1,000 a week is about 142 a day (1,000 divided by 7).

How do I keep a count on the Sume side?

Use one Idempotency-Key per SKU and variant. A replay of the same key returns the original job instead of creating and billing a second video, per the video generation docs. Store the job id next to the SKU so the number of jobs is the number of videos you plan to upload.

for sku in sku-001 sku-002 sku-003; do
  curl -X POST https://api.sume.com/v1/videos \
    -H "Authorization: Bearer $SUME_API_KEY" \
    -H "Content-Type: application/json" \
    -H "Idempotency-Key: weekly-$sku-v1" \
    -d '{
      "model": "sume/auto",
      "prompt": "Product spin on a clean background",
      "aspect_ratio": "9:16",
      "duration": 5
    }'
done

How many jobs can Sume hold at once?

Sume admits paid jobs into a queue. The admission docs list processing concurrency and default queue capacity by plan, and say to prefer the workspace's effective generation_limits over the static table.

What should I check before a big week?

Submit in batches no larger than the accepted capacity, poll GET /v1/jobs/{id}/status, and retry a 429 queue_full with the same key. A queued job is not a failure. Shopify's weekly count concerns uploads, so a clip you generate but never upload does not count against it, as far as that page states; confirm in Shopify's own documentation.