Layout
The Controls tab decides what you ask. The Layout tab decides how it is arranged and what else appears alongside it. The panel arranges the boat's, and Price it pins its total to the foot.

Elements
You build the panel from elements, added with Add element 1. GUI Elements at a Glance shows each one as the panel draws it. A control you have not placed still shows, at the top of the panel, and a new element lands at the top of its list.
Control places one of your controls. Adding a control in the Controls tab creates the question, and placing it here decides where it appears.
Section groups elements under a heading, the simplest way to break a long panel into parts that make sense, like Finishes, Equipment and See it. It takes a Title and an optional description.
Row lays its children out in a horizontal line, wrapping onto a new line when they no longer fit. It is what you reach for when two things belong side by side: a price beside a quantity, a strip of buttons. Its children keep their conditions, their greying out and their pricing. Besides an optional title, a row has a Gap (px) between its children, an Align setting for how they line up across it, a Justify setting for how leftover horizontal space is shared out along it, and Wrap onto a new line when it does not fit, which is on by default. Turn wrapping off only for a row you know stays narrow, because otherwise the children overflow.
Accordion does the same as a section but collapses, which keeps a panel with many options from becoming a wall. Put the choices most shoppers change at the top, Expanded, and fold the rest away. It can carry an icon or small image beside its title.
Tabs split the panel into pages the shopper switches between. Good when your product has genuinely separate areas of choice, and worse than accordions when the choices interact, since a shopper cannot see both at once. Initially active tab chooses which opens first, and each tab has its own visibility and availability conditions.
Text and Message add words. Text is plain explanation, in one of four styles from Heading down to Caption. Message is a highlighted note, for a lead time or a warning about a particular combination, with a Severity of Info, Success, Warning or Error. Either can carry a link written as [label](https://...), which becomes clickable in the panel - Read the [care guide](/pages/care) first. The destination has to be a web address, a mailto: or tel: address, or a page on your store; anything else stays as the literal text you typed.
Image places a picture, useful for a diagram explaining what a measurement refers to. It takes Alt text, an optional caption and a Max height (px).
Link is a hyperlink on its own, shown as plain link text or as a button. It can open in a new tab and carry an icon, and both its text and its destination are translatable, so a French shopper can be sent to the French page. The same destination rules as inline links apply, and publishing stops on one that breaks them.
Divider is a line - or, set to Empty space, nothing at all, which is how you get breathing room between two groups. Either way Size (px) sets the size.
Parts list shows what the configuration is made of, drawn from the Parts tab, as labels and quantities. It never shows your internal part numbers. Parts themselves need the Pro plan. Empty message sets what it says when the configuration resolves to no parts at all; left empty it simply hides itself.
- Show how many of each turns the quantities on or off.
- Group rows decides whether the list reads like your parts tab or like the order. One row per part prints what you authored. One row per product, parts underneath gives any product that several parts point at a row carrying the total for that product, with those parts listed underneath it, and Fold each product's parts away behind a chevron tucks them in. Use it when your bill of materials names the same product more than once: four fittings of the same bracket read as four rows of one, while the cart charges a single line of four. The number is for one configured item, so a shopper buying two is charged for twice as many. Parts nested inside an assembly are left where they are.
- Show each part's picture puts the linked product's image beside each row. A part linked before pictures were recorded shows none until you refresh Linked products on the project page. Size the pictures under Style.
- Show what each part costs adds a price column. It is off to begin with, because the list is a build sheet before it is a quote. A part that adds nothing on top of the base price has its price column left empty rather than showing zero, and nothing shows at all while pricing is switched off.
- Let the shopper fold the list away puts the list behind a toggle, with its heading still in view, so a long bill of materials does not push your buy button off the screen. Start with the list open chooses how it starts.
Price shows the running total. Amounts in your store's own currency are written the way your currency formatting in Shopify's settings writes them, on the panel, the customer's PDF and the cart card, so they match your theme. A format without decimals shows whole amounts; the cart charges the exact amount. Other currencies are written in that currency's usual style. It renders nothing at all until pricing is enabled in the Pricing tab, so if you have placed one and the panel shows no total, that is the first thing to check. Show price breakdown itemises it, which is worth doing, since a total that changes without explanation makes people suspicious. The sections below cover its breakdown, discounts and promo code.
Quantity lets them buy several of the configured item. It is the familiar - N + stepper: the displayed price multiplies by it, the cart line ships at it, and on the product page it stays in step with your theme's own quantity input. The Add to cart element hides its own stepper when this element is present, so the two never disagree.
Add to cart places a buy button inside your panel. While the panel has one, the app hides your theme's own add to cart and express checkout buttons, as long as the theme block's Theme buy buttons setting stays on Auto (recommended). You set the Button text, the Success message and Error message, whether it shows its own quantity stepper or takes the quantity from one of your numeric controls, and After adding: Stay on the page, Go to cart or Go to checkout.
Confirmation appears after adding to cart, and can offer the shopper a link back to their configuration, so they can return to it or send it to someone. It reacts to an Add to cart element, so without one in the panel it never appears, and Composer warns you. The copyable link also needs the configuration to be remembered in the URL, a setting in the Settings tab.
Validation summary collects any outstanding problems in one place. Each entry is a link: clicking it opens whichever accordion or tab the offending control is hiding in, scrolls to it and puts the cursor in it. It hides itself while everything the shopper can see is valid.
Download PDF gives the shopper a document of what they designed. The button renders nothing unless the customer document is enabled and designed under PDF reports. Pro plan.
Custom HTML places a fragment of your own HTML, with its own CSS, for content the other elements cannot express. Custom HTML spells out what survives. Standard or Pro plan; publishing refuses it on a lesser plan.
Camera controls lets shoppers move the camera without dragging. Camera controls has the details. Standard or Pro plan; publishing refuses it on a lesser plan.
Screenshot lets shoppers save a picture of the 3D view. Screenshot has the details. Standard or Pro plan; publishing refuses it on a lesser plan.
Sections, rows and accordions can hold other elements, and each tab of a Tabs element holds its own, so you can nest as deeply as the product needs. Every element also offers Clone element, Move To for shifting it into another container or back out to the top level, and - for sections, rows, accordions and tabs - Convert To, which turns one into another without rebuilding its contents. Custom styling gives one element a style of its own.
The price breakdown
The boat's Price element sits in the Main panel - pinned to the bottom area 1, so the total stays in view while the choices scroll.

Breakdown style 2 decides how the breakdown reads, and it only appears once you have switched the breakdown on. Let the shopper fold the breakdown away and Start with the breakdown open work as they do on the parts list.
- One line per charge is the default. The base price, each priced option, each formula and each part gets one line stating what it is and what it adds.
- Draw the parts, with pictures and quantities gives the charges that come from your parts the same treatment as the Parts list, with the same Show how many of each, Show each part's picture and Group rows. Everything else stays a plain line. It suits a product priced from its bill of materials, with good photography.
Where a configuration is charged by options and by parts, this style separates the two into an Options and a Parts section, each with its own subtotal, then the total. Where only one of the two carries any charge there are no headings and no subtotals.
A price breakdown drawn as parts already shows the labels, quantities and pictures. Use both only when you want the build sheet somewhere the price is not.
The store's discounts
Discounts show on every Price element while pricing is on and the product is sold through one of the charging methods; Pricing test mode shows none. Untick Show the store's discounts to never show them on that element. When your store runs a discount this configuration qualifies for - an automatic discount, or a code the shopper has already put on their cart - the element shows it the way Discount style 3 says:
- Concise - new price, discounts named underneath is the default, and reads the way Shopify's own checkout shows a discounted item: the total struck through, the price after discounts beside it, and one line underneath naming each discount in a small tag, with the amount saved. Hovering a tag shows its value.
- Price only - new price and percent saved, one line keeps it to the one line, for a panel with no room to spare.
- Itemized - one row per discount lists each discount on its own row with its value, then the total after discounts.
Concise Total €4,996,800 €4,746,960
Spring sale You save €249,840
Price only Total €4,996,800 €4,746,960 -5%
Itemized Total €4,996,800
Spring sale (5% off) -€249,840
Total after discounts €4,746,960
In the first two, the first figure is struck through.
When the shopper changes something that moves the total, the discounts keep their place and a small spinner stands in for them until Shopify has priced the new configuration, usually about a second, so the buy button does not jump.
The numbers come from Shopify. While the shopper configures, the storefront asks Shopify to price exactly the product, options and quantity on screen, the same way checkout will, and shows the discounts Shopify gives it. The rows appear only when Shopify's price for the configuration is the total the shopper sees, to the cent. Shopify prices the configuration on its own, for a shopper it does not know, so "Final price is confirmed at checkout" shows under the rows, and a few discounts only settle there:
- discounts that depend on the rest of the cart, such as a minimum spend across the whole order or buy X get Y, and those limited to logged-in customers or B2B buyers, show at checkout rather than on the product page;
- discounts limited to once per order or once per customer can show here and still be refused at checkout;
- a subscription (selling plan) price is usually not the total shown, so the rows stay hidden for it;
- in a currency other than your store's, conversion rounding can leave Shopify's price a few cents away from the total, and then the rows stay hidden - see Other currencies.
Promo code
Promo code 4 advertises one of your discount codes on the Price element, as a chip with the code picked out. Type the code exactly as you created it under Discounts in your Shopify admin; Shopify matches codes regardless of case. The chip needs pricing switched on, like the rest of the element.
- Apply puts the code on the shopper's cart. From then on Shopify applies it to everything in the cart it covers, at checkout as well as in the discounts above. Apply is not offered in Pricing test mode, where the chip only copies.
- The small copy icon beside it copies the code for shoppers who would rather type it at checkout.
- Before the code is applied, the chip reads "Use code SEATRIAL". As soon as Shopify confirms the code lowers this configuration's price, it reads "Save €6,000 with SEATRIAL" instead, and it goes back to the plain wording whenever the configuration does not qualify. If the shopper later removes the code from their cart, the chip offers it again.
- Once the code is on the cart but gives nothing on this configuration, the chip says it is on the cart and that any saving applies at checkout. That is also what a code limited to logged-in customers or B2B buyers shows.
- The saving is checked for the first two different codes across your Price elements; a third still offers Apply and copy, without stating a saving.
- Promo wording replaces "Use code {code}" with your own words;
{code}is replaced with the code, and if your wording leaves{code}out, the code is added at the end. - Promo placement puts the chip Below the total or Beside the total, wrapping underneath when there is no room.
Composer cannot check a code against your store, so a mistyped code never saves anything. Open the product page and press Apply once to be sure. To see the rows and the chip before you publish, open the discount simulator in Play - see Edit mode and Play.
Width and grow
Every element, of every type, carries a Width: a number and the unit it is measured in - px, %, rem or ch. Leave it empty and the element fills the space it is given, which is what almost all of them should do.
Width behaves differently inside a row, where it is a starting size rather than a final one. A second field appears there: Grow, the share of the row's leftover width this element takes. Zero, the default, keeps the element at its natural size. Two children at 1 each split the space evenly between them, and 2 against 1 takes twice as much.
Showing and greying out
Every element, not just a control, carries two conditions. Visibility decides whether it is on the page at all. Availability, the Enabled when condition, leaves it on the page but greys it out, with a Disabled hint explaining why.
Both cascade. Disable a section and everything inside it is greyed out too, at any depth, and a control with no hint of its own borrows the nearest one above it. Anything a shopper cannot reach is also never charged for, and checkout holds to the same conditions.
Visible, or just unavailable
The choice between the two is a choice about what the shopper learns, and Hiding versus greying out goes through it with the boat's own rules: hide what carries no information, and grey out what does.
Place a control here and its Visibility section points you back at the Controls tab: one condition, in one place, and the same one that decides whether the control is charged. If a placement from an older edit still carries a condition of its own, Composer says so and offers to clear it - the two are combined, so the control appears only when both match, which is rarely what anyone meant.
Only for visitors from a link
Page address shows an element only when the address of the product page carries a query parameter you name, such as ?preview=staff or ?trade - for a panel part meant for visitors who arrive from a campaign, a staff link or a trade portal. Give a Value (optional) to require that exact value, or leave it empty to accept any. Both compare exactly, capital letters included. It works together with Visibility: the element shows only when both hold. Bare control placements take it from a section around them.
Three things set it apart from the other conditions:
- It tailors, it does not protect. Anyone can type the parameter into the address, so never use it to hide a price or a choice someone must not get.
- Choices inside are charged either way. Checkout cannot see the page address, so a control inside keeps its default whether the element shows or not, and that default counts toward the price. Give any priced choice in such an element a default that costs nothing.
- Required fields inside are required only for those visitors. Everyone else never sees them, so they can add to cart without filling them in.
Don't use the parameter your shared configuration links carry (bb-config, unless you renamed it under The URL parameter): everyone opening a shared configuration would then see the element. Composer lists that under Setup problems. Publishing warns you about a required or priced control inside such an element. An Add to cart inside one is likewise for those visitors only: everyone else keeps your theme's own buy button, even though the panel's button hides it for those visitors.
In Play, the link button in the toolbar appears once an element uses a page address. It lists every parameter your panel uses, so you can switch each on and see the panel as those visitors will. The Layout tab preview always shows these elements, so you can design them.
Areas: putting panel parts elsewhere
By default the whole panel sits together beside the 3D view. Areas let you break that up.
Each top-level element carries an Area field, and there are thirteen built-in choices. An element nested inside a section, an accordion or a tab renders where it sits, so Composer only shows the field at the top level. If you want a control in a canvas corner, it has to be a top-level element.
| Area | Where it lands |
|---|---|
| Main panel (default) | The panel beside the 3D view. |
| Main panel - pinned to the top, Main panel - pinned to the bottom | Inside the main panel, staying in view while the controls between them scroll. |
| 3D canvas - top left, 3D canvas - top right, 3D canvas - bottom left, 3D canvas - bottom right | Overlaid on the corners of the 3D view. |
| 3D canvas - top center, 3D canvas - bottom center, 3D canvas - left center, 3D canvas - right center | Overlaid on the middle of that edge of the 3D view. |
| 3D canvas - center | Overlaid in the middle of the 3D view. |
| Near the buy buttons | Immediately after your theme's add to cart form. |
Canvas corners suit a small control that belongs visually on the product, as Length does on the boat. The edge midpoints suit something the shopper reads first, or a row of camera buttons. The centre overlay suits something that should interrupt, such as a confirmation after adding to cart. The buy area suits things decided at the last moment, like quantity or a gift note.
On a phone, and on a tablet that stacks, the corner and edge areas stop overlaying the model and stack underneath the panel instead, because a phone has no room for anything floating over the view. The centre overlay stays where it is. Where an area goes on a phone is where you change that.
While you are in Play in Composer, its own buttons share those two edges with your areas: the toolbar sits on the top edge and the Stop button on the bottom edge. An element in the top center or bottom center area keeps the edge, exactly where the storefront draws it, and Composer's buttons step inward to make room.
Pinned to the top or bottom of the panel
The two pinned zones keep part of the main panel in view while the shopper scrolls through the controls - typically the price, the breakdown and Add to cart at the bottom, as on the boat, and perhaps a title or a lead-time note at the top. They share the panel's background and are separated from the controls by a thin line.
Beside the 3D view the panel has a fixed height, and the zones take what they need from it:
- A zone is as tall as its content by default. Tallest it may grow, in its row of the areas list, caps it in pixels or as a percentage of the panel; beyond the cap the zone scrolls inside.
- The controls between the zones always keep at least 40% of the panel. Controls keep at least, on the main panel's row, changes that. When the zones would take more, they shrink and scroll instead - the top zone first, since the bottom one usually holds the price and Add to cart.
- A price breakdown or parts list placed directly in a zone is limited to 30% of the screen's height and scrolls inside, so the total and Add to cart stay in view when the shopper opens a long breakdown. A Max height in the element's Custom styling overrides that.
On phones, and on tablets that stack the 3D view above the controls, the page scrolls instead of the panel, so the zones simply sit at the top and bottom of the controls. Keep on screen on phones, on the bottom zone, turns it into a bar along the bottom of the screen; it is held short enough that the 3D view and some of the controls stay visible. The same flow applies wherever the panel is not ours to size: when your theme's product information joins the panel, and when a GUI Controls theme block hosts the GUI.
The areas list: how wide an area is, and folding it away
Under the elements there is an areas list, one row per area in play: the main panel, every built-in area that holds at least one element, and your custom areas. An area you have not placed anything in is not listed, and an area that still carries settings after its last element left stays listed with "no elements yet", so you can see the settings and reset them. Each row's header sums up what is set on it. A built-in area starts on its default - full width, no fold toggle, shown on every screen - behind a Configure button, and Reset to defaults puts it back there.

This is where an area's own size is set. Width 1, Smallest width and Largest width each take a number and a unit. On the main panel they size the panel inside its column. The column beside the 3D view is set by Controls panel width on the app's Canvas Size page in the Split layout, and by your theme in the Inline layout. On the canvas corners and edge midpoints it replaces the built-in cap of 60% of the view, which is what you reach for when a corner control is coming out cramped.
Shopper can fold it away adds a toggle that collapses that area's contents, leaving only the toggle over the canvas. It is the answer to a corner control that is useful but keeps covering the product. Start folded decides which state it opens in; after that the shopper's own choice sticks as they carry on configuring. Show the toggle on limits the toggle to Every screen, Phones only - 769 pixels and below - or Desktop only, which means every wider screen, tablets and laptops included. Toggle icon puts one of the built-in icons in place of the default chevron, and Toggle corner pins the toggle to a particular corner instead of following the area's own.
The two pinned zones have neither of these: their row holds Tallest it may grow and, on the bottom one, Keep on screen on phones. An area with nothing in it draws nothing, whatever you set here.
Where an area goes on a phone, and which screens hide it
Shoppers' screens fall into four kinds by width - phones up to 769 pixels, tablets from 770 to 1023, laptops from 1024 to 1535 and desktops above that, the same four the app's Canvas Size page draws. Phones always stack: the 3D view on top, the controls below. Tablets stack too in the Split layout, unless you chose Side by side for them on that page; in the Inline layout they keep the canvas areas over the model, as laptops and desktops do. Two settings in each configured area's Per screen group decide what that does to it.
Hide on 2 is a checkbox per kind of screen, on every area but the main panel and its pinned zones, custom areas included. A hidden area still renders and its controls still count towards the price and the order data; only its box disappears. Its required fields still block Add to cart on the screens where it is hidden, so never put a required control in an area you hide. Use it for a corner control that earns its place on a wide screen and only clutters a phone, or the other way round.
When stacked 3, on the nine canvas areas, says where the area lands once nothing can float over the model:
| Placement | Where it lands |
|---|---|
| Below the panel | In a full-width stack after the controls. The default for the corners and the edge midpoints. |
| Above the panel | Between the 3D view and the controls. |
| Pinned under the canvas | In a strip stuck to the bottom edge of the 3D view, which stays put while the shopper scrolls the controls. This is where the boat keeps Length, and where a price and an add to cart button belong on a phone. The strip has no background of its own, so the controls scroll visibly behind it - give the area an area card if that bothers you. It pins only when your storefront layout is Split, the one that keeps the 3D view itself pinned; in the Inline layout the strip simply sits above the controls. |
| Stays on the canvas | Floating over the model, as it does on a wide screen. The default for the centre. |
If the only add to cart button in your GUI lives in an area you hide on some screen, shoppers on that screen keep the theme's own add to cart button instead - the storefront never hides both - but the price shown and the button they press then come from different places. With Product lines charging it is worse: the theme's button adds the product without the lines its choices are charged through, and the cart refuses it. Either keep an add to cart visible on every screen, or hide the area on none.
Stacked order decides the sequence within a placement; lower comes first, and areas without one follow in the built-in order. You rarely type it: the Order on phones block under the list draws the phone as the shopper scrolls it - the areas on the canvas, the pinned strip, the above stack, the main panel, the below stack - and you drag a row, or use its arrows, to move it inside its group. Areas hidden on phones are listed underneath.
The 2D preview at phone width and the 3D preview's phone button (see Previewing as you go) both draw the result, and the app's Canvas Size page draws it on the product page skeleton with your other settings around it.
Your own areas
Add custom area puts a new row in the same list. Each one is an Id of your choosing, a CSS selector that finds a spot in your theme, and a Position saying where to land relative to what the selector matched: Append inside, Prepend inside, Before or After. Assign an element to that id and it appears there. A custom area takes the same size, folding and per-screen settings as a built-in one. That is how you spread the panel across the product page.
Areas fail softly, by design. If a selector matches nothing on the live page - the theme changed, or the element only exists on some templates - the elements assigned to it fall back to the main panel rather than disappearing. The same happens to elements pointing at a custom area you have since deleted.
You can also override where an area lands by placing a GUI Controls block in your theme. The block claims one area and hosts it wherever you drop it in the theme editor, which is useful when a selector cannot express the position you want. Its area list does not offer the canvas centre - if that is the area you want, type canvas-center into the block's Custom area id (optional) field instead.
Previewing as you go
While the GUI section is open, the right side of Composer shows the panel itself rather than the 3D view, at desktop or phone width. At desktop width, elements you have sent to other areas are drawn as separate labelled blocks beneath the panel. At phone width the preview stacks the way a phone does - a placeholder for the 3D view with the areas that stay on it at their corners, then the pinned strip, the areas above the panel, the panel, and the areas below it - with the areas you hid on phones named underneath.
Play has the same switch: the phone button in its toolbar renders the stacked layout around the real 3D view in a phone-wide column, so you can scroll the controls with the pinned strip in place and the model in view. The eye button hides the controls in both previews, and on the phone one the 3D view then takes the whole column.
The preview has two modes. Preview behaves as the page does: use the form, watch conditions react. Inspect adds an editing layer - hovering outlines what you are pointing at, clicking still works as it does for a shopper, and double-clicking opens and highlights that element in the editor. On a panel with forty elements this saves a lot of scrolling.
If you have translations, a language toggle appears here too, so you can read the panel as a shopper in that language would. A reset button puts every value back to its default. While a field in the tabs needs fixing, the bottom bar shows Needs attention, which lists each problem and takes you to it.
Check mobile early and often. A panel that is comfortable on a wide screen can become an enormous scroll on a phone, and most of your shoppers are on a phone.
Verified against the product in November 2026