Product images / MERCHANT WORKFLOW
Canva Autofill vs Bulk Create: Which Workflow Should Merchants Use for Product Posters?
Choose Canva Bulk Create when an editor can prepare a product table, connect its fields to a design, and manually generate a reviewed batch. Evaluate Canva Autofill when an authorized application needs to populate an existing labeled design or brand template through an API workflow. Autofill is not merely automated Bulk Create: it requires eligible access, the appropriate application authorization model, valid dataset fields, Canva asset IDs for images, asynchronous job handling, and review of the returned design. Neither workflow automatically publishes product advertisements or keeps every previous export synchronized.
Choose by who initiates the production job
Canva's Bulk Create instructions describe an editor-led workflow using manually entered data, spreadsheet files, Canva Sheets, or connected data applications. Each row creates a design version, while columns provide values for connected text or image elements. The documented workflow supports up to 150 connected data fields and is available on desktop web or the desktop application for specified eligible plans.
Autofill uses labeled fields in an existing Canva design or brand template. An application supplies values to those fields through Canva's REST APIs. The application must identify the correct source, inspect its current dataset, and execute an Autofill operation. A saved label is preparation, not a completed job.
| Decision | Bulk Create | Autofill API |
|---|---|---|
| Who starts the work? | Campaign editor | Authorized application |
| How are images supplied? | Connected image data, including embedded spreadsheet images | Canva asset IDs in image-field payloads |
| What identifies the output? | Generated design versions | Job status and returned design information |
| What must be reviewed? | Every relevant generated design | Completed job, populated design, export, and destination |
The 150-field Bulk Create limit is not a general Autofill API payload limit. Similarly, Canva Sheets selection limits should not be applied to an unrelated REST request.
Verify the authorization model before planning Autofill
Canva's developer documentation describes Autofill for applications acting on behalf of eligible users on supported Canva Pro, Teams, Enterprise, Education, and Nonprofit plans. The Help Center and developer eligibility descriptions should be checked independently against the actual account and integration. A paid account alone does not establish that every API route or service application is available.
For a public or private application acting on behalf of a user, Canva documents the OAuth authorization-code flow and the design:content:write scope for creating Autofill jobs. The application must also obtain the relevant permissions for reading its source design or brand-template dataset and accessing media assets.
Canva separately documents service applications that act on behalf of the application itself using OAuth client credentials and the service:design:content:write scope. This is a different authorization model, not an alternative permission that any merchant can select merely because a subscription is paid. Service-app eligibility, configuration, and source access must be established through the applicable Canva developer and organizational requirements before proposing that route.
The official Autofill development guide describes app creation, MFA prerequisites, OAuth setup, dataset access, and asset preparation. The merchant should obtain a working authorization path before estimating an automated production workflow.
Map real Canva image assets, not local filenames
For Bulk Create, the editor connects product columns to design elements. Canva documents that images from a spreadsheet must be embedded in cells rather than supplied as ordinary cloud-storage URL text. For API Autofill, the input contract is different: an image field uses type: image and a valid Canva asset_id.
The developer must upload or identify each approved image in Canva's asset library, obtain its actual asset ID, and preserve the SKU-to-asset mapping. Canva's asset-upload workflow is asynchronous; the upload job must finish and return a usable asset before that ID is used in Autofill. A local filename such as blue-mug-approved.png is a source identifier, not a valid REST image-field value by itself.
For a hypothetical source design DESIGN-MUG-POSTER-V3, suppose dataset inspection confirms the exact field names SKU_TEXT, PRICE_TEXT, and PRODUCT_IMAGE. The intended payload structure for one record is:
{"type":"create_from_design","design_id":"DESIGN-MUG-POSTER-V3","data":{"SKU_TEXT":{"type":"text","text":"MUG-BLUE-24"},"PRICE_TEXT":{"type":"text","text":"$18"},"PRODUCT_IMAGE":{"type":"image","asset_id":"CANVA-ASSET-BLUE-EXAMPLE"}}}
Every identifier in this example is fictional and non-executable. Replace it with a real source design ID, actual dataset field names, and the real asset ID returned by Canva. Canva's API also supports create_from_brand_template and update_design; select the operation that matches the intended ownership of the output.
Canva warns that unknown field names may be silently skipped. Therefore, do not infer that a field was populated from an accepted request alone.
Hypothetical two-SKU Autofill and Bulk Create comparison
Hypothetical CartVisual editorial exercise. No Canva authorization, asset upload, dataset retrieval, Autofill job, generated design, or export was executed. A homeware merchant has two proposed poster records: MUG-BLUE-24 with source image blue-mug-approved.png and price $18; and MUG-WHITE-25 with white-mug-approved.png and price $23.
For Bulk Create, the editor connects the SKU, price, and embedded image columns to the intended elements, generates two test designs, and inspects each result. For Autofill, the developer first obtains two distinct Canva asset IDs. In this exercise they are represented by nonworking placeholders CANVA-ASSET-BLUE-EXAMPLE and CANVA-ASSET-WHITE-EXAMPLE.
The proposed source is DESIGN-MUG-POSTER-V3. The two intended jobs are JOB-BLUE-01 and JOB-WHITE-01, and their expected completed designs are DESIGN-BLUE-C01 and DESIGN-WHITE-C01. These labels are planning identifiers, not Canva-issued job or design IDs.
| SKU | Expected image asset | Expected text | Required output check |
|---|---|---|---|
| MUG-BLUE-24 | Blue mug asset ID | MUG-BLUE-24; $18 | Blue mug and $18 in the returned design |
| MUG-WHITE-25 | White mug asset ID | MUG-WHITE-25; $23 | White mug and $23 in the returned design |
Canva's Autofill create operation returns an asynchronous job. The application retrieves the job status until it succeeds or fails. On success, it records the actual returned design ID and opens that design for inspection. Exporting is a separate operation; publication is another separate responsibility.
Diagnose the four evidence stages independently
Authorization: If the application cannot initiate a job, check its OAuth model, token, required scopes, eligible account, and source access. Do not switch to service credentials without confirming service-app eligibility.
Job execution: If Canva returns a failed asynchronous job, preserve its actual error and investigate the reported cause. A submitted request is not a completed design.
Field population: If the job succeeds but the blue mug appears with the white mug's price, reject the design. Compare the SKU record, dataset field names, actual Canva image asset IDs, and returned design. If a field remains unchanged, investigate silent skipping or a missing source label before regenerating the entire campaign.
Export and publication: A correct returned design still requires an authorized export and a review of the actual delivered file. The existing field-matching guide covers manual mapping defects, while the static-output guide explains why changing a spreadsheet does not automatically replace previously generated ads.
CartVisual, the publisher, can help prepare product creative through Product Poster Maker. Canva authorization, asset uploads, Autofill execution, exports, and publication remain external operations. The worksheet below is an editorial record, not a Canva import file or CartVisual integration.
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.
| Route | SKU | Source design | Dataset fields | Source image | Canva image asset ID | Expected price | Authorization and job | Returned design | Actual field observation | Export state | Next action |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Bulk Create | MUG-BLUE-24 | Manual poster copy | SKU_TEXT; PRICE_TEXT; PRODUCT_IMAGE | blue-mug-approved.png | Not applicable; embedded image data | $18 | Not executed | Not generated | Not observed | Not exported | Connect fields and inspect blue mug with $18 |
| Bulk Create | MUG-WHITE-25 | Manual poster copy | SKU_TEXT; PRICE_TEXT; PRODUCT_IMAGE | white-mug-approved.png | Not applicable; embedded image data | $23 | Not executed | Not generated | Not observed | Not exported | Connect fields and inspect white mug with $23 |
| Autofill | MUG-BLUE-24 | DESIGN-MUG-POSTER-V3; fictional | SKU_TEXT; PRICE_TEXT; PRODUCT_IMAGE; to verify | blue-mug-approved.png | CANVA-ASSET-BLUE-EXAMPLE; fictional | $18 | User OAuth not checked; JOB-BLUE-01 is fictional | DESIGN-BLUE-C01; fictional | Not observed | Not exported | Obtain real asset ID, dataset, job ID, and returned design |
| Autofill | MUG-WHITE-25 | DESIGN-MUG-POSTER-V3; fictional | SKU_TEXT; PRICE_TEXT; PRODUCT_IMAGE; to verify | white-mug-approved.png | CANVA-ASSET-WHITE-EXAMPLE; fictional | $23 | User OAuth not checked; JOB-WHITE-01 is fictional | DESIGN-WHITE-C01; fictional | Not observed | Not exported | Verify separate white asset ID and rendered $23 |
What the sources establish
- Canva Help — Create designs in bulk: Primary instructions for editor-led Bulk Create, connected fields, supported plans, desktop availability, and image handling.
- Canva Help — Set up your designs for Autofill: Primary instructions for preparing labeled fields in Canva designs and checking feature availability.
- Canva Developers — Create design autofill job: Primary API contract for operation types, image asset_id values, OAuth scopes, distinct application authorization models, asynchronous execution, and silently skipped unknown fields.
- Canva Developers — Get design autofill job: Primary job-status and result-retrieval operation.
- Canva Developers — Autofill designs with data: End-to-end guide for eligible account and app preparation, asset upload, dataset access, job execution, and returned design handling.
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.
- Canva Help — Create designs in bulk · Review date not separately recorded
- Canva Help — Set up your designs for Autofill · Review date not separately recorded
- Canva Developers — Create design autofill job · Review date not separately recorded
- Canva Developers — Get design autofill job · Review date not separately recorded
- Canva Developers — Autofill designs with data · Review date not separately recorded
Frequently asked questions
Can I put a local image filename into a Canva Autofill image field?
No. Canva's REST image-field contract requires an asset_id. Upload or identify the approved image in Canva's asset library, obtain the actual asset ID, and associate it with the correct SKU.
Can any paid Canva account use service:design:content:write?
No such universal entitlement is established. That scope belongs to Canva's separate service-application authorization model. Confirm service-app eligibility, configuration, and source access independently of ordinary user-authorized Autofill eligibility.
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