Assets & tasks / MERCHANT WORKFLOW
How Can You Update a Shared Figma Product-Ad Component Without Resetting SKU Overrides?
Figma identifies certain component edits as potentially breaking changes. Adding a hidden-by-default optional property is generally less disruptive, while removing or renaming properties, renaming directly overridden layers, and restructuring variants can reset or alter existing instance overrides. Preserve a representative set of SKU instances and test the proposed change before publishing it.
Classify the change by its effect on existing instances
Figma's component-management guidance distinguishes non-breaking and breaking updates. Examples of non-breaking changes include adding optional properties and visual refinements that do not disrupt overrides or layout behavior.
Its breaking-change examples include removing or renaming properties, restructuring variants so existing instances resolve differently, and renaming layers that users have overridden directly.
The same guidance explains why default visibility matters. A new supporting-text property that starts hidden can leave existing designs unchanged. Making that content visible by default may introduce unwanted placeholder text into existing instances.
Do not classify a change as safe merely because it adds only one layer. The important question is whether the new layer changes the visible output or the way existing overrides are resolved.
| Proposed edit | Documented risk category | Review focus |
|---|---|---|
| Add hidden optional badge | Lower-risk example | Existing instances remain unchanged |
| Rename ProductImage layer | Potentially breaking | Image overrides survive |
| Rename PriceText property | Potentially breaking | Saved prices and field access |
| Restructure layout variants | Potentially breaking | Correct variant resolution |
Build a small regression set
Before publishing, identify instances that exercise the component's important behaviors: a standard product image, a custom crop, a long headline, an optional badge, and a layout variant.
Preserve the current source component and the approved SKU-specific values. Prepare a working copy or suitable isolated test environment. Figma recommends testing a changed component in a file that already uses it and cycling through property combinations.
For Organization or Enterprise plans, Figma also documents library branching as an available isolation option. Do not assume that every plan has branching or analytics access.
Compare the proposed component against the existing instance set. If a property rename is unnecessary, retain the original name. If a new layout is needed, consider adding a variant alongside the old one during a transition rather than restructuring the entire set immediately.
Hypothetical two-SKU maintenance release
Hypothetical exercise. No Figma component or library was modified. Shared component AD-CARD-V7 has instances for SOAP-LAVENDER-01 and SOAP-CITRUS-02.
The Lavender instance overrides ProductImage with lavender-soap-front-v3.png. The Citrus instance overrides the same layer with citrus-soap-front-v2.png.
Proposal A adds a hidden-by-default ShowOfferBadge boolean property. Proposal B renames ProductImage to HeroMedia. The intended maintenance outcome is to add the optional badge without losing either SKU image.
Under Figma's guidance, A is the lower-risk starting point. B requires a breaking-change review because existing overrides may depend on the original layer name. No actual result has been observed.
Choose the release action from the regression result
If the hidden badge addition leaves both product images and existing text unchanged, it is a candidate for publication after ordinary approval. Record the actual test evidence; the documentation does not certify this particular component.
If the layer rename resets the Citrus photograph, stop the breaking release. Retain the existing name or design a migration that explicitly reassigns the affected SKU content.
If a variant restructure sends Lavender to the wrong layout, inspect variant names and property resolution before publishing. Do not repair the issue by changing the product photograph.
If the update must break existing behavior, Figma recommends proactive communication, documentation, and a transition or deprecation plan. Record affected files and the person responsible for accepting library updates.
Use the library-update guide for the publication and subscriber sequence. CartVisual does not run Figma regression tests or maintain its component libraries.
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.
| Component | SKU | Current override | Proposed change | Risk classification | Actual test result | Next action |
|---|---|---|---|---|---|---|
| AD-CARD-V7 | SOAP-LAVENDER-01 | ProductImage=lavender-soap-front-v3.png | Add hidden ShowOfferBadge | Lower-risk candidate | Not tested | Test before publishing |
| AD-CARD-V7 | SOAP-CITRUS-02 | ProductImage=citrus-soap-front-v2.png | Rename ProductImage to HeroMedia | Potentially breaking | Not tested | Retain old name or plan migration |
What the sources establish
- Figma — Components collection: Tips for component management: Documents non-breaking and breaking changes, hidden optional properties, regression testing, branching eligibility, and deprecation guidance.
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 — Components collection: Tips for component management · Review date not separately recorded
Frequently asked questions
Is adding a hidden optional property always guaranteed safe?
No. Figma presents it as a non-breaking example, but the actual component and instance combinations still need testing.
Why can renaming a product-image layer affect existing posters?
Figma identifies renaming directly overridden layers as a potentially breaking change because instance overrides may depend on those layer relationships.
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