Assets & tasks / MERCHANT WORKFLOW
How Should You Expose Product Photos, Prices, Headlines, and Offer Badges in a Figma Poster Component?
Figma currently documents five component-property types: Boolean, Instance swap, Text, Slot, and Variant. For a reusable product poster, use Text for headlines and price strings, Boolean for optional badge visibility, Instance swap for curated nested media components, Slot for flexible content that editors need to add or rearrange, and Variant for predefined layout states. A plain PNG filename is not an instance-swap value. Component properties guide editors toward intended changes but do not lock other layers or verify commercial facts.
Select the property type by the editor's actual job
Figma's current Component property fundamentals documentation lists five types. Its separate Edit instances article describes four commonly exposed controls, but that narrower overview is not the complete taxonomy because Slot is also documented.
| Property type | Documented role | Poster example |
|---|---|---|
| Text | Change text content | Headline and PriceText |
| Boolean | Show or hide a layer | ShowOfferBadge |
| Instance swap | Replace a nested component instance | ProductMedia using curated media components |
| Slot | Add, edit, or rearrange flexible content | Optional supporting content area |
| Variant | Select a predefined component state | Square or Portrait layout |
The distinction between Instance swap and Slot matters for product imagery. Instance swap suits a controlled set of predefined media components. A Slot is a flexible area where an editor can add and rearrange content inside an instance without detaching it. An ordinary image-fill replacement is a third method: it changes the image content of a layer but does not automatically create an instance-swap property or Slot.
Figma explicitly says component properties do not restrict access to other layers. Therefore, the proposed field contract is editorial guidance, not an access-control mechanism. If a team needs enforced editing restrictions, it must evaluate actual permissions and supported governance controls separately.
Author a coherent nested-media component structure
Start with a main component named POSTER-MASTER-V6. Define text layers for Headline and PriceText, a badge layer controlled by ShowOfferBadge, and layout variants named Square and Portrait.
For a curated photo selector, create actual nested components such as Media/MugCobalt/Front and Media/MugSand/Front. Each media component contains the appropriate source image as its artwork. The PNG is the source of that component's visible image, not the value of the instance-swap property.
Place a nested media instance in the poster master and expose an Instance swap property named ProductMedia. Configure the preferred alternatives to point to the actual media components. An editor can then select the appropriate component through the available instance control.
For an open-ended product-content region, consider a Slot named SupportingContent. Figma describes Slots as flexible areas for adding, editing, and rearranging content. This may suit a campaign where the number or order of supplementary elements changes. It is less appropriate than a curated swap when the editor's task is simply choosing one of two approved product-media components.
If the requirement is only to replace a photograph inside a fixed frame, an image-fill override may be simpler. Its crop and product identity still require inspection. The image-fill replacement guide
Figma's Explore component properties instructions cover authoring on main components and component sets. The feature is documented across plans but requires edit access to the file. Publishing a shared library or granting access to collaborators is a separate permission decision.
Hypothetical two-SKU mug poster with real component values
Hypothetical editorial exercise. No Figma component, Slot, instance swap, or export was created or tested. A fictional merchant has poster master POSTER-MASTER-V6 and two products, MUG-COBALT-12 and MUG-SAND-12.
The media-component library contains Media/MugCobalt/Front, whose source artwork is mug-cobalt-front-v3.png, and Media/MugSand/Front, whose source artwork is mug-sand-front-v2.png. These are proposed component identities and separately recorded source filenames.
The Cobalt poster instance is POSTER-COBALT-01. Its proposed ProductMedia value is Media/MugCobalt/Front, Headline is Meet the Cobalt Mug, ShowOfferBadge is false, and Layout is Square.
The Sand instance is POSTER-SAND-01. Its ProductMedia value is Media/MugSand/Front, Headline is Meet the Sand Mug, ShowOfferBadge is false, and Layout is Square.
Both PriceText values are Pending approval, deliberately nonpublishable placeholders. The optional SupportingContent Slot is proposed as empty in both instances.
| Field | Cobalt value | Sand value |
|---|---|---|
| ProductMedia | Media/MugCobalt/Front | Media/MugSand/Front |
| Source artwork | mug-cobalt-front-v3.png | mug-sand-front-v2.png |
| Headline | Meet the Cobalt Mug | Meet the Sand Mug |
| PriceText | Pending approval | Pending approval |
| ShowOfferBadge | False | False |
| SupportingContent | Empty Slot | Empty Slot |
| Layout | Square | Square |
The intended export identifiers are poster-cobalt-square-v1.png and poster-sand-square-v1.png. Neither file exists in this exercise.
Test the field contract without treating it as a lock
On a duplicate working instance, verify that ProductMedia swaps between actual nested media components. If the dropdown shows no appropriate Cobalt component, inspect the nested instance and its configured preferred values. Renaming a PNG file will not create the missing component relationship.
If the editor needs to add and rearrange arbitrary supporting content, evaluate the Slot approach rather than multiplying predefined media components. Confirm the current UI and intended Slot behavior in the actual file; the verified fundamentals establish flexibility but do not establish every account-specific eligibility or configuration detail.
If the Cobalt photograph appears with the Sand headline, correct the instance values and source mapping. A technically successful swap does not establish that the selected SKU and copy agree.
If switching from Square to Portrait loses an image or text override, inspect the variant structure and preservation conditions. The variant-override guide
If the badge is hidden correctly but the price remains unapproved, hold export. Boolean visibility and text editability do not validate promotions, prices, or eligibility.
Finally, inspect the exported file for crop, headline wrapping, correct SKU image, and actual approved commercial copy. Component-property exposure is not a security boundary: an editor with sufficient access may still modify other layers. CartVisual does not create Figma component properties or synchronize them with catalog data.
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.
| Template | Instance ID | Fictional SKU | Property | Property type | Target layer or nested component | Permitted values or content | Proposed instance value | Source artwork | Actual instance state | Actual export evidence | Next action |
|---|---|---|---|---|---|---|---|---|---|---|---|
| POSTER-MASTER-V6 | POSTER-COBALT-01 | MUG-COBALT-12 | ProductMedia | Instance swap | Nested media instance in ProductFrame | Media/MugCobalt/Front; Media/MugSand/Front | Media/MugCobalt/Front | mug-cobalt-front-v3.png | Not configured | Not exported | Create nested component and verify swap |
| POSTER-MASTER-V6 | POSTER-SAND-01 | MUG-SAND-12 | ProductMedia | Instance swap | Nested media instance in ProductFrame | Media/MugCobalt/Front; Media/MugSand/Front | Media/MugSand/Front | mug-sand-front-v2.png | Not configured | Not exported | Verify Sand component and source mapping |
| POSTER-MASTER-V6 | POSTER-COBALT-01 | MUG-COBALT-12 | Headline | Text | Headline text layer | Approved product-specific headline | Meet the Cobalt Mug | Not applicable | Not configured | Not exported | Check copy and longest-line wrapping |
| POSTER-MASTER-V6 | POSTER-COBALT-01 | MUG-COBALT-12 | PriceText | Text | Price text layer | Verified current offer string | Pending approval | Not applicable | Not configured | Not exported | Hold until actual price is approved |
| POSTER-MASTER-V6 | POSTER-COBALT-01 | MUG-COBALT-12 | ShowOfferBadge | Boolean | OfferBadge layer visibility | True; False | False | Not applicable | Not configured | Not exported | Keep hidden pending promotion approval |
| POSTER-MASTER-V6 | POSTER-COBALT-01 | MUG-COBALT-12 | SupportingContent | Slot | SupportingContent flexible area | Approved additional content; empty | Empty | None | Not configured | Not exported | Confirm Slot eligibility and empty-state layout |
| POSTER-MASTER-V6 | POSTER-COBALT-01 | MUG-COBALT-12 | Layout | Variant | Poster component set | Square; Portrait | Square | Not applicable | Not configured | Not exported | Inspect variant override preservation |
What the sources establish
- Figma — Components collection: Component property fundamentals: Primary source for all five current property types, Slot flexibility, curated instance swapping, and the explicit statement that component properties do not restrict access to other layers.
- Figma — Explore component properties: Documents authoring component properties on main components and component sets, nested-layer targets, preferred instance swaps, all-plan availability, and required file edit access.
- Figma — Edit instances with component properties: Documents consuming exposed controls in the instance sidebar, editing text and visibility, swapping nested instances, and choosing variants. Its four-control overview is not treated as the complete current taxonomy.
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: Component property fundamentals · Review date not separately recorded
- Figma — Explore component properties · Review date not separately recorded
- Figma — Edit instances with component properties · Review date not separately recorded
Frequently asked questions
Does Figma have four or five component-property types?
Figma's current fundamentals and authoring documentation list five: Boolean, Instance swap, Text, Slot, and Variant. The narrower Edit instances overview describes four common controls but does not exhaust the current taxonomy.
Can I use a component property to lock the logo while allowing the product photo to change?
No. Figma explicitly says component properties guide customization and do not restrict access to other layers. Use the properties to make intended edits clear, and handle permissions and approval separately.
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