How do I catch Canva matching a product price to the wrong text field?

Build a diagnostic fixture

Create a small spreadsheet with two data rows and two columns: SKU and Price. Use deliberately distinguishable values, such as SKU “SKU-RED-742” and Price “17.43” for the first row, then SKU “SKU-BLUE-906” and Price “82.16” for the second. These values are illustrative and are chosen only to expose a swap; replace them with your own test values if needed.

Make a non-production copy of the product design. Add one text element intended for the SKU and another intended for the price. Keep the labels visually separate, for example “SKU:” beside the SKU element and “Price:” beside the price element, so the rendered result provides evidence of which field received which value.

Connect fields deliberately

In Canva’s bulk workflow, rows create design versions and columns provide fields. Each page needs field connections, so treat the connection from the SKU column to the SKU text element and the Price column to the price text element as separate checks. Do not infer the mapping from column order or from similar-looking values.

The relevant field type here is text: SKU and Price are both being inserted into text elements. A price column containing numeric-looking values is still not proof that Canva connected it to the correct text element. Record the intended mapping before running the test: SKU → SKU text; Price → Price text.

1. Prepare only the two illustrative rows and the two named columns.
2. Open the copied design’s bulk-create workflow and connect the SKU column to the SKU text element.
3. Connect the Price column to the price text element.
4. Generate the two test versions, then inspect the actual design pages and any available data or field indicators.

Illustrative exercise: compare A and B

Illustrative exercise: Asset A is the SKU text element, explicitly defined as the location that must display “SKU-RED-742” on row one and “SKU-BLUE-906” on row two. Asset B is the Price text element, explicitly defined as the location that must display “17.43” on row one and “82.16” on row two.

Pass means row one shows Asset A = “SKU-RED-742” and Asset B = “17.43”, while row two shows Asset A = “SKU-BLUE-906” and Asset B = “82.16”. Fail means either value appears in the other element, a row uses the other row’s value, or an element remains unchanged or blank. The exercise is a procedure example, not a claim that it has been tested.

Branch on the evidence

If both rows pass, keep the recorded mapping and repeat the same field-connection review when you add more columns or pages. Check the final designs separately because a video preview can be static and may not expose the completed result.

If the values are swapped, blank, or duplicated, stop before creating the production batch. Recheck the field type and the explicit connection for both text elements, then regenerate the two-row fixture. If the mapping is correct but only the rendered layout is wrong, inspect the copied design’s text elements and page assignments rather than changing the source prices or SKUs. If a cloud photo-storage URL is being used as a value, remember that such URLs are treated as text; image content must be embedded in a cell, not left as a floating image.

Acceptance record

Accept the handoff only when every test row displays the intended SKU and Price in their distinct text elements, with no blank, cross-row, or swapped value. Save the tested column names, the intended connections, and the observed row-by-row result beside the batch request so another editor can audit the same mapping before production generation.

Scope of the documentation

The official references below support tool behavior and feature boundaries. The test fixture, branching decisions and acceptance criteria are Itemlume editorial recommendations; citation does not imply endorsement. Illustrative sizes, names and timings are not your production specifications.