Logic Without a Panel
A configurator does not have to render anything. If every control in your configuration has Product page rendering set to External - bound to an existing theme input via selector, so that each one reads a field your theme or your options app already shows, 3D Bits draws no panel of its own. The shopper sees your form, and only your form.
Your Logic rules still run. Not all of them can do everything, though, and knowing which half you have is the difference between a rule that quietly works and one that quietly does not.
When your configurator is running without a panel
3D Bits renders a panel when either of these is true:
- at least one control has Product page rendering set to Rendered by 3D Bits - drawn on the product page, or
- the Layout tab holds anything besides plain control placements: a heading, an image, a price, an add-to-cart button, or a tab group with at least one tab in it.
If neither is true there is nothing to draw, and your rules run without one. It is always one or the other, never both.
This is worth checking rather than assuming, because a single rendered control anywhere in the configuration puts you back on the ordinary route where everything applies.
What still runs
Everything that decides a value or changes the 3D scene:
Set a control's value, and reset it to its default. The written value goes into the configuration and drives the model, and it holds until the shopper changes that field again. Your form is not touched: the field keeps showing what the shopper chose.
Override the minimum, maximum or step of a number or a slider. A value that falls outside the resulting range is pulled back into it in the configuration; your own field still shows what the shopper entered.
Selection fallbacks. When a rule takes away the option that is currently chosen, the configuration falls back to the option you marked as the default, or to the first one still available. In a group of checkboxes the removed option is unticked instead, and a switch turns off. The scene follows the fallback, exactly as it would with a panel.
Show or hide a 3D element - a model, a part of a glTF file, a marker, a dimension, a decal or a light.
Force a material variant, or a colour or texture variant.
Run a script, on the plans that include scripting.
All three triggers behave normally: On load fires once when the page opens, On change fires once at the moment something changes, and While matching holds for as long as its condition is true. Conditions that look at what a value used to be work too, because the rule engine keeps its own history of every settled pass.
What does not run
Showing, hiding, enabling or disabling a control or an option. These need a control that 3D Bits draws. A dropdown that belongs to your theme is not ours to grey out, so the effect is evaluated but nothing changes on screen.
The value half of the same rule still applies, and that gap is the thing to watch:
Take the rule from Options and Rules, which greys out Port beach club while Tender is ticked. Without a panel, your theme's own Port beach club field stays as it was, ticked. The configuration drops the option, so the 3D model changes - but the shopper's form was not touched, and it is your form that submits to Shopify.
If your rules take options away, either render the affected controls in 3D Bits so the shopper sees what happened, or reflect the same restriction in your own form.
Messages. A Show a message effect has nowhere to appear. With Debug Mode on, a message from an On load or On change rule is printed to the browser console instead, which is how you confirm the rule fired. A While matching rule's message is not printed; the rule shows in the console's rule trace while it matches. The shopper sees nothing either way.
Blocking add-to-cart with an error message. With no panel there is no add-to-cart button of ours to block, so publishing a priced configuration refuses that combination and names the rule. Rendering one control is usually the better answer, because the shopper then sees the reason as well as the refusal.
3D Bits attaches the configuration to the cart only when it renders something on the page. If pricing is on in a configuration that draws no panel, a shopper who uses your theme's own add-to-cart button adds the product without its configuration, and the cart refuses it with "... is made to order and has to be configured on its product page - please remove it from the cart and add it again from there." Nothing sells.
When another system owns the price, which is the usual reason for running this way, turn off Enable pricing under GUI, Pricing in Composer. The shopper then buys at the product's own price through your theme's button. If you want 3D Bits to price the configuration, render at least the controls that carry money, and give the panel an add-to-cart button of its own. See Pricing.
Seeing what it is doing
Turn on Debug mode in the project's Storefront settings, open a product page and open your browser's console alongside the debug panel. The two show different things, and the difference is the point:
- The panel's Live tab lists the field names and values read from your page. It shows what is on the page, not what logic did with it, so a value a rule has overwritten still appears here as the shopper left it.
- The console shows what logic did. Every key whose settled value changed is printed as it changes, matched and fired rules are printed as a trace, and messages from On load and On change rules are printed as they fire.
A rule that fights another rule warns in the console too, whether or not Debug mode is on, naming the key of the control the two rules keep changing. That is the signal to simplify rather than to add a third rule.
Turn Debug mode off before the page goes live. The panel is visible to shoppers.
Where to go next
Custom Forms is the contract your form has to meet for any of this to read correctly. Using Another Options App covers running 3D Bits beside an app that renders the form for you. Logic covers writing the rules themselves.
Verified against the product in November 2026