Assets & tasks / MERCHANT WORKFLOW
Why Did Importing Revised Brand Tokens Update Only Some Figma Poster Values?
Figma's Import mode operation updates existing variables only when token names and types match. Importing into a new collection follows different requirements: tokens must appear across the imported files with compatible supported types. A partial update can therefore be consistent with the documented matching rules rather than evidence that every poster ignored the import. Audit the token records before editing individual poster colors.
Identify which import operation was used
Figma documents importing design tokens into a new collection and importing a file to update an existing mode. These are not interchangeable operations.
For a new collection, the imported files create modes. Figma creates variables only for tokens present in all imported files, with supported values and the same supported type across those files. For an existing mode, the documented Import mode operation updates variables whose token names and types match.
Figma also normalizes nested token names with forward slashes. If two incoming tokens normalize to the same name, only the first encountered is imported and the duplicate is ignored. This can matter when one file uses a nested object structure and another uses an already flattened name.
The official Modes for variables page lists supported token types, including color, dimension, font family, duration, number, and an accepted string form. Dimension values require supported pixel units, and duration values require seconds. An arbitrary JSON key is not automatically a supported design token.
| Import condition | Documented implication |
|---|---|
| Existing variable has matching name and type | Eligible for mode update |
| Existing variable has same name but incompatible type | Not a documented matching update |
| Token absent from one file in new-collection import | Does not meet the all-files creation requirement |
| Two tokens normalize to one name | First imported; duplicate ignored |
| Unsupported token value or unit | Does not meet the supported import contract |
Compare the token identity, not just the visible color
Start with a preserved export or record of the existing collection and the intended new token file. Compare the token path, type, mode, and value. A visually similar swatch can be stored under a different name and therefore fail to match the existing variable.
For example, brand/primary and brand-primary should not be assumed to identify the same variable. Likewise, a string-valued offer label cannot be safely updated by a color token simply because both have a similar business name.
Inspect the actual target mode. Updating the Light mode does not automatically prove that the Dark mode received the same new value. The separate mode-selection mechanism is covered by the variables overview. A correctly imported value also will not change a poster element that is not bound to that variable.
The existing brand migration guide explains which physical stock and publication placements should adopt a new identity. This guide isolates a narrower data-import failure before those creative decisions are executed.
Hypothetical three-token campaign revision
Hypothetical CartVisual editorial exercise. No token file was imported and no Figma poster was inspected. Fictional collection ALDER-BRAND-TOKENS contains a Light mode. The intended campaign update changes the primary color, retains a string offer label, and introduces a new accent color.
The preserved existing collection contains brand/primary as Color, copy/offer-label as String, and no brand/accent. The proposed import file contains brand/primary as Color with value #174A45, copy/offer-label as Color with value #D8B86A, and brand/accent as Color with value #E9C96A.
The offer-label type change is deliberately invalid for the intended text update. The accent is a new token rather than a matching existing variable.
| Token | Existing type | Incoming type | Expected import assessment |
|---|---|---|---|
| brand/primary | Color | Color | Matching update candidate |
| copy/offer-label | String | Color | Type mismatch; revise token source |
| brand/accent | Absent | Color | Not an existing-mode match |
The expected assessments follow the documented matching rule; they are not observations of an executed import. The merchant should not conclude that the revised poster is approved merely because the primary swatch changes.
Repair the input contract before adjusting poster instances
If the primary color updates but the offer label does not, inspect the offer token's type and name. Correct the incoming source to a supported String token when the intended value is text, then use the supported mode-import procedure after confirming the target variable identity.
If a new accent color is absent, determine whether the operator intended to create a new variable or update an existing one. An existing-mode import that updates matching variables is not a promise to create every new token automatically.
If a token is present in one imported file but missing from another during new-collection creation, reconcile the files. Figma's all-files requirement matters before any poster-level debugging.
If a value updates in the collection but not on a poster, inspect the poster's actual variable binding and selected mode. Do not repeatedly reimport the same file to fix an unbound layer or an explicit mode override.
Finally, compare the affected poster instances and exports against approved brand artwork and exact commercial text. A token import changes design data; it does not approve a rebrand, update a storefront, or verify a product price. CartVisual does not import Figma tokens or publish the resulting posters.
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.
| Collection | Mode | Token name | Existing type | Incoming type | Incoming value | Expected import decision | Actual observation |
|---|---|---|---|---|---|---|---|
| ALDER-BRAND-TOKENS | Light | brand/primary | Color | Color | #174A45 | Matching update candidate | Not imported |
| ALDER-BRAND-TOKENS | Light | copy/offer-label | String | Color | #D8B86A | Resolve type mismatch | Not imported |
| ALDER-BRAND-TOKENS | Light | brand/accent | Absent | Color | #E9C96A | Review new-variable creation route | Not imported |
What the sources establish
- Figma Learn — Modes for variables: Primary documentation for Import mode, new-collection imports, supported token types, name/type matching, and duplicate normalized names.
- Figma Learn — Overview of variables, collections, and modes: Explains the variable and collection structure required to interpret imported mode values.
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.
- Figma Learn — Modes for variables · Review date not separately recorded
- Figma Learn — Overview of variables, collections, and modes · Review date not separately recorded
Frequently asked questions
Does Import mode create every new variable in my token file?
Figma documents Import mode as updating existing variables whose token names and types match. New-collection import has a separate creation contract.
Can two differently nested token names collide?
Yes. Figma normalizes nested names using forward slashes and documents that only the first token is imported when normalized names collide.
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