Before you start
- What goes in
- A base project, a CSV or TSV table, named image assets and selected mockup outputs.
- What comes out
- A ZIP of stills and/or videos for the valid variant rows, named by SKU, scene and dimensions.
A practical example
Citrus, berry and mint
Prepare columns sku, flavour, image and colour. Create one text layer for flavour, one image layer for the illustration and one compatible colour layer in the base design. Use the real filenames in the image column.
Step-by-step walkthrough
Prepare a clean base design
Complete the structure, layout and scene. Name the text, image and colour objects so you can map them confidently. Check one finished base mockup before creating a range.
Load the variant table and assets
In Advanced → Export, open SKU batch and choose the CSV or TSV file. Add the image files, a supported ZIP or a folder of assets using the controls provided.
Map each column
For each column, choose the text, image or colour layer it changes, or Ignore. The sku column can be used for filenames only. Ensure the type of each mapping matches the target layer.
Choose outputs
Select Mockup still · current scene, Ticked scenes or Mockup video · current scene. Tick additional scenes in Scenes before choosing that option.
Review the plan before running
Check variants × outputs, the estimated work and Rows that will be skipped. Correct missing images or invalid values instead of silently accepting an incomplete range.
Export and inspect the range
Run the batch, extract the ZIP and review at least every distinct variant and scene. Confirm the SKU, wording, image and colour agree. The variants are rendered from copies; they do not replace the open base project.
Options at a glance
| Control or choice | What it changes | How to use it well |
|---|---|---|
| Variant table | CSV or TSV rows describing individual products. | Use unique, meaningful SKUs and consistent column values. |
| What each column changes | Maps data to a compatible text, image or colour layer. | Ignore administrative columns that should not appear on the pack. |
| Variant images | Uploaded files resolved against the image names in the table. | Use exact, unambiguous filenames and inspect unresolved-image messages. |
| Current scene / Ticked scenes | One or several still-image compositions per variant. | Keep the framing consistent across the range and avoid unnecessary duplicate scenes. |
| Mockup video | A video output for each variant in the current scene. | Test one short video first; work grows with both the number of rows and outputs. |
Detailed control reference
Find the control, understand its effect, and choose it for the job you are making. Available controls depend on the selected structure, object, workspace and output.
Advanced → Export → SKU batch
CSV/TSV columns, SKU and Ignore
Each row describes a variant. Columns map to compatible text/image/colour layers, or Ignore. SKU can identify filenames without appearing on the artwork.
- When it helps most
- Use clear stable layer names and a unique product identifier. Map the changing flavour separately from the brand and net quantity.
- Impact and trade-offs
- An unmapped or ignored column does not change the design. A column intended for the filename is not automatically printed on the package. Review column-to-layer mappings before rendering every row.
- Worked example
- Use columns sku, flavour, illustration and colour. GROVE-CITRUS can name the file while Citrus Sunrise replaces only the Flavour text layer.
SKU batch → table mapping and assets
Variant image uploads and colour values
Uploaded image files are resolved against the table’s image references; colour mappings change compatible colour layers.
- When it helps most
- Use exact unambiguous image names and consistent valid colour values. Include every image needed by the requested rows.
- Impact and trade-offs
- A missing or ambiguous asset can skip a row; a replacement with a new aspect ratio can crop differently under the base layer’s Fit. A darker variant colour can make unchanged text unreadable. Inspect each meaningful difference.
SKU batch → outputs
Current still, Ticked scenes and Current video
Chooses which presentation outputs to generate for each valid variant. Multiple ticked scenes multiply the still outputs; video adds its own render work.
- When it helps most
- Use consistent framing for an ecommerce range and additional scenes only where the destination needs them. Test one representative row before a large run.
- Impact and trade-offs
- This workflow produces mockup presentation assets, not a variable-data production PDF for each SKU. A larger row × scene count increases time and storage; device and encoder limits can exclude requested outputs.
- Worked example
- Three flavours × two still scenes = six expected stills if all rows are valid. Adding one current-scene video per flavour requests three additional videos. Compare the plan and final receipt to those counts.
SKU batch → pre-run plan and export result
Rows that will be skipped and final receipt
Shows invalid rows, missing images or unavailable outputs before and after processing so the delivered range can be reconciled.
- When it helps most
- Correct required rows before running. Use the final list to match each SKU to its actual files and investigate omissions.
- Impact and trade-offs
- A completed ZIP is not proof that every requested product was rendered. Do not publish a partial range accidentally. The batch works on variant copies and does not replace the open base project.
What this batch workflow produces
SKU batch creates presentation stills and videos from the base design’s variants. It is not a variable-data press-sheet workflow and does not imply that each table row produces a separate production PDF.
The plan can skip rows with invalid values, unresolved images or outputs unavailable on the device. Read both the pre-run report and the final receipt, then reconcile the resulting file count with the requested range.
Check meaningful differences, not just the first image
A long flavour name can wrap where a short one does not. A replacement image can have a different aspect ratio. A dark background can make existing text unreadable. Review those cases in the finished range before publishing the assets.
Check your work
- Every column maps to the intended layer.
- Image names resolve to the correct uploaded files.
- No required row is listed as skipped.
- Long names and differently shaped images fit.
- File names and visible product variants agree.
Troubleshooting
A row is skipped for a missing image
Compare the table value with the uploaded filename and remove ambiguity between similarly named files.
A column cannot change the desired object
Check the layer type. The batch maps compatible text, image and colour layers; restructure the base design if needed.
The batch is much slower than expected
Reduce scenes, resolution or video outputs and test a smaller range. Estimates are approximate and device-dependent.