Assets & tasks / MERCHANT WORKFLOW
How Can You Update Gelato Mockups in Bulk Without Replacing Production Artwork?
Gelato provides separate bulk operations for updating product designs and product mockups. Update Product Mockups uses a Reference Product ID, whereas Update Product Designs uses Print File URLs. However, choosing the mockup operation does not establish that every production or commerce setting is isolated. Gelato also warns that reference-product placement and options, including pricing, must be correct because template settings can be applied to resulting products. For a mockup-only refresh, treat preservation of existing print files, variants, pricing, and other listing data as explicit conditions to verify—not guaranteed behavior.
Choose the bulk operation without assuming complete field isolation
Gelato's March 11, 2026 instructions distinguish two CSV operations. Update Product Designs uses Print File URLs to replace production designs across selected products or variants. Update Product Mockups uses a connected reference product and its Reference Product ID to update mockup presentation.
The second operation is the relevant candidate when a merchant wants different storefront images but intends to retain approved print artwork. It does not follow that every other field is protected.
Gelato's reference-product preparation instructions tell merchants to verify design placement and product options, including pricing and mockups, because those settings are applied to products created from the template. The documentation does not provide a complete field-by-field preservation guarantee for existing products updated through the mockup operation. Its reference-template language therefore creates a real scope question, not permission to assume that only image pixels change.
| Requested change | Documented operation | Required caution |
|---|---|---|
| Replace print artwork | Update Product Designs | Print File URLs affect production design |
| Refresh storefront mockups | Update Product Mockups | Reference Product ID; verify broader reference settings |
| Change pricing or variants | Not the objective of this refresh | Hold if unintended effects cannot be ruled out |
The bulk operation affects store listings and Gelato says it cannot be undone. Do not use an unreviewed live-catalog upload to discover the scope.
Inspect the reference product and export the actual CSV
In Gelato, open Stores, select the connected store, and navigate to Update Product Mockups. Gelato instructs merchants to use Export CSV to obtain existing product records. Work from that exported schema rather than constructing a replacement file with guessed columns.
Choose a connected reference product whose mockups suit the intended targets. Record its actual Product ID, product type, print-area placement, orientation, variant configuration, mockup selections, and commerce settings, including price where applicable.
Compare those values with every target. A reference poster using a different orientation or print placement may be unsuitable even if its room scene looks attractive. A reference with different variant or pricing settings also requires investigation before use.
Keep only the target rows that genuinely need updating. Preserve their existing Product ID and title. Populate Reference Product ID with the actual connected reference identifier. Do not populate Print File URLs as a workaround for a mockup request.
Before upload, preserve an authorized baseline of each target's current print-file assignment, placement, variants, prices, and storefront images. Confirm which existing store-managed mockups would be replaced; this is a replacement workflow, not an additive gallery operation.
If the available documentation or account controls cannot establish an acceptable scope for the merchant's products, hold submission and obtain clarification through the merchant's authorized Gelato support or account workflow. The absence of a preservation guarantee is not evidence that a particular field will change, but it prevents promising that it cannot.
Hypothetical poster catalog with a reference-settings conflict
Hypothetical editorial exercise. No Gelato CSV was exported, uploaded, validated, or processed. All identifiers and settings below are fictional.
The merchant has reference product GEL-REF-POSTER-01, a portrait poster with a reviewed wall-scene mockup. Its proposed baseline records a centered print placement, portrait orientation, one size variant, and reference price REF-PRICE-01. That price is an internal fictional identifier, not an actual amount or an approved target price.
Target GEL-POSTER-102 uses print file botanical-102-v3.png, centered portrait placement, one size variant, and existing price record PRICE-102. Target GEL-POSTER-103 uses coastal-103-v2.png, portrait placement, two size variants, and PRICE-103. The reference's single-variant configuration has not been shown compatible with target 103's two variants.
Product GEL-MUG-104 uses mug-104-v1.png and is excluded because its product type and placement differ from the poster reference.
| Target | Reference | Known compatibility | Proposed disposition |
|---|---|---|---|
| GEL-POSTER-102 | GEL-REF-POSTER-01 | Type and placement aligned; price preservation unresolved | Hold upload pending scope confirmation |
| GEL-POSTER-103 | GEL-REF-POSTER-01 | Variant configuration differs | Exclude until compatible reference established |
| GEL-MUG-104 | None | Different product type | Exclude |
For target 102, the intended CSV would retain its actual exported Product ID and title and set Reference Product ID to the connected poster reference. This is a proposed row edit, not a file ready for submission. Neither target's print artwork, price, or variant structure is assumed preserved.
Separate validation, processing, and storefront readback
Gelato documents Upload CSV and format validation before processing. Passing that validation establishes neither reference compatibility nor the truthfulness of the resulting storefront.
Its instructions describe checks of stalled sub-operations every three hours, up to three retries, with unsuccessful sub-operations marked failed. Operations stuck beyond two days may be terminated. Review per-target outcomes rather than interpreting an overall completed state as proof that every row succeeded.
If the CSV fails validation, correct the exported schema, actual IDs, or reference values. Do not switch to Update Product Designs simply to bypass the error.
If a target's variant count, placement, or pricing differs from the intended baseline after processing, stop further rollout and investigate the affected product before allowing it to represent the intended offer. If its print-file assignment changes, treat that as a production-sensitive issue requiring authoritative readback—not a cosmetic mockup discrepancy.
If the target's settings remain correct but the storefront still displays an old mockup, investigate the update result and destination synchronization separately. If previously customized store images disappear, reconcile the replacement with the approved gallery plan rather than assuming the operation appends images.
The product-revision guidebatch review
Use the example with your own product records
The filled records are hypothetical editorial examples. The entry-template row is for your own files, settings and observations; it does not connect to another application.
| Target Product ID | Reference Product ID | Target type and placement | Reference placement | Target variants | Reference variants | Target price record | Reference price record | Approved target print file | Existing mockups to replace | CSV decision | Actual validation and processing | Actual print-file and placement readback | Actual variant and price readback | Actual storefront images | Next action |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GEL-POSTER-102 | GEL-REF-POSTER-01 | Portrait poster; centered | Portrait poster; centered | One size | One size | PRICE-102 | REF-PRICE-01 | botanical-102-v3.png | Current poster gallery; exact files to inventory | Hold | Not submitted | Not inspected | Not inspected | Not inspected | Clarify scope and price preservation before any upload |
| GEL-POSTER-103 | GEL-REF-POSTER-01 | Portrait poster; centered | Portrait poster; centered | Two sizes | One size | PRICE-103 | REF-PRICE-01 | coastal-103-v2.png | Current two-variant gallery; exact files to inventory | Exclude | Not submitted | Not inspected | Not inspected | Not inspected | Find a compatible reference or retain current mockups |
| GEL-MUG-104 | None | Ceramic mug; wrap placement | Not applicable | Mug configuration | Not applicable | PRICE-104 | Not applicable | mug-104-v1.png | Current mug gallery | Exclude | Not applicable | Not inspected | Not inspected | Not inspected | Do not map mug to poster reference |
What the sources establish
- Gelato — Bulk update product designs and mockups: Official instructions dated March 11, 2026. Establishes separate design and mockup operations, Print File URLs versus Reference Product ID, exported CSV and retained target IDs/titles, reference placement and options including pricing, compatibility checks, validation, irreversible listing effects, and sub-operation retries. Does not guarantee isolation of every non-mockup field.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Gelato — Bulk update product designs and mockups · Review date not separately recorded
Frequently asked questions
Does Update Product Mockups guarantee that Gelato leaves print files, variants, and prices unchanged?
No such comprehensive guarantee is established by the cited instructions. Gelato separates mockup and design operations, but also warns that reference-product placement and options, including pricing, matter. Verify the intended scope and retain before-and-after records.
Can a Gelato bulk mockup update be undone if it replaces the wrong storefront images?
Gelato explicitly warns that the operation affects store listings and cannot be undone. Resolve compatibility and scope uncertainties before submission; do not use a live update as an exploratory test.
YOUR NEXT CAMPAIGN
Create assets from a clear source
Bring your reviewed source photo or brand brief to CartVisual. Check the current tools, account access and credits before generating, then compare every result with your source.
Create a CartVisual account Open the workspace Check access and credits