Why Publishing Was Refused
Publishing is refused rather than completed whenever going live would leave a shopper unable to buy, or leave you collecting the wrong amount of money. The message names the option, the part, the control, the script or the product involved, and where a figure is at stake it names the figure.
This page is the one list of refusals: each message, and what to change. Some of them appear while you are still working. The checks under Conditions that decide money and Logic rules, and a script address without https, show as rows labelled Blocks publishing in Setup problems on the bottom bar, so you can clear them before you press Publish. With pricing off the app does not run the logic checks, so those rows read Will not run instead: nothing refuses the publish, and the rule or script is skipped on the product page. The rest are checked by the app when you press Publish.

A warning after a successful publish tells you something you should know: your configurator is live either way. A refusal means shoppers are still seeing the previous version. One message is neither: "Published, but some products could not be updated." means the new version reached some linked products and not others. Publish again until it reports success.
The checks from Conditions that decide money onwards run on a project with pricing on. Most of them arrive inside "Publish blocked - the configured price could not be provisioned for real charging: ... Fix the above and publish again, or disable pricing for this project.", and the tables quote the part in the middle.
Before the request leaves Composer
Composer checks the configuration against its own rules first, so these never reach the app.
| The refusal | The fix |
|---|---|
| "Cannot publish - the configuration does not match the schema (N problems). Open the issue list to see where." | A Blocking publish button appears on the bottom bar. Open it and press a row to go to the field. Fix each one and press Publish again. |
| "Cannot publish - the configuration has N problems. Fix them and try again." | A form field is invalid. Use Needs attention, over the 3D view or on the bottom bar. See Troubleshooting. |
| "Cannot publish - the configuration could not be generated from the form.", "Cannot publish - the configuration is not valid JSON. Fix it and try again." | Fix the form, or the text in the JSON view, and press Publish again. |
The project and its products
| The refusal | The fix |
|---|---|
| "Link at least one product before publishing." | Publishing from Composer opens Shopify's product picker for you. If you cancel it, a project without pricing publishes anyway, and Copy URL beside Publish gives you a URL for a BITBYBIT VIEWER block on any page. With pricing on, pick a product: Product lines and Variant matrix charging refuse to publish without one, with the next row's message or the variant matrix one. |
| "this project is not attached to any product, so the price shoppers would be charged cannot be checked. Attach a product on the project page." | With pricing on, a project needs a product. Attach one on the project page, or turn pricing off for this project. |
| "'Other project' is already published to one of these products, and two projects cannot share one." | One product carries one published configurator. Unpublish the other project, or link this one to a different product. |
| "Nothing to publish yet - edit and save the project first." | Open the project in Composer, make your changes and save. |
| "This project is already publishing - wait for it to finish before publishing again." | Wait for it to report back rather than pressing again. |
| "A publish is still running for this project. Its other actions come back when it finishes, within a few minutes." | A publish started from the project page in the app is still running. Wait until the project page shows it finished, then publish again. |
| "Published, but some products could not be updated." | Not a refusal: some linked products already show the new version, and the rest still show the previous one. Publish again until it reports success. |
| "This project is too large to publish. Reduce the scene or split it into linked scripts." | The usual cause is parsed glTF structure carried for models that do not use it. See Configuration size. |
Linked scripts
| The refusal | The fix |
|---|---|
| "Publish blocked - linked script 'Name' has no published version yet. Open it under Scripts and publish from the editor first." | Open it under Scripts and publish it. |
| "script 'Name': its URL must use https." | Fix the address on the script. With pricing off nothing refuses it, and the script never runs on the product page, so fix it either way. |
| "Scripts require the Standard or Pro plan." | This one is about publishing a script project itself. Upgrade, or remove the script. |
| "Publish this script from the editor first." | The script project has nothing to publish yet. Open it in its editor and publish from there. |
Your layout
The first three arrive inside "Publish blocked - the layout has a problem checkout cannot work around: ...".
| The refusal | The fix |
|---|---|
| "The control 'key' is placed twice in the layout." | Remove one of them. |
| "Two layout elements share the id 'x'." | Give one a different id. |
| "The tab strip ... has two tabs with the id 'x'." | Give one a different id. |
| "Custom HTML elements need the Standard or Pro plan." | Upgrade, or remove the Custom HTML elements from the layout. |
| "Camera controls elements need the Standard or Pro plan." | Upgrade, or remove the Camera controls elements from the layout. |
| "Screenshot elements need the Standard or Pro plan." | Upgrade, or remove the Screenshot elements from the layout. |
| "Downloading the 3D model requires the Pro plan." | Upgrade, or change the button's action. |
| "The link 'x' points at '...', which is not a web address, mailto:, tel: or a page on your store." | Change the URL in Composer. |
These publish with a warning instead of a refusal, and the warning says what happens:
- a Custom HTML element that still contains markup the storefront removes
- a
[label](url)in a text or message whose address is not an allowed destination, which shows as plain text - a camera whose every pointer gesture is switched off, in a project with no Camera controls element, focals or points of interest
PDF documents
| The refusal | The fix |
|---|---|
| "PDF reports require the Pro plan. Upgrade your subscription or disable both PDF report documents in the Composer before publishing." | Turn off both documents in PDF reports, or move to Pro. It is having a document enabled that blocks, not having one configured. |
Conditions that decide money
These apply to a condition that decides whether something is charged: the conditions on a priced control or option and on every element above it, on a price formula, or on a part. A condition that only decides what a shopper sees is unaffected.
| The refusal | The fix |
|---|---|
| "These use expression-editor conditions, which cannot run at checkout - switch them to the visual condition builder: ...", "priced gating cannot use the expression editor - rebuild it with structured conditions." | Untick Use expression editor and rebuild the condition from Equals (==), Not equals (!=) and Includes rows. |
| "priced gating cannot use history functions (prev/changed/initial).", "priced conditions cannot use history functions (prev/changed/initial)." | Rework the condition around the final selection. |
"priced gating cannot use {{id}} placeholder input names.", "priced conditions cannot use {{id}} placeholder input names." | Reference the control's own key instead. |
| "reads 'x', which nothing ever sets." | The condition can never match, so the charge would never apply. The message says why. Pick the control and its value from the lists again. |
| "logic rule 'x' force-shows the priced option 'y', which also has its own visibility or enablement condition." | Remove the option's own condition and let the rule own it, or drop the rule's visible or enabled override. The same goes for a rule that force-shows or force-enables a priced control. |
Logic rules
| The refusal | The fix |
|---|---|
| "a while-matching condition cannot use history functions." | Move it to an On change rule. |
| "effect 'x' is one-shot and not allowed on a while-matching rule." | Move it to an On change rule. |
| "effect 'x' is a persistent state and not allowed on an on-change rule." | Move it to a While matching rule. The same goes for an On load rule. |
| "blocking logic messages cannot gate add-to-cart when no GUI renders on the storefront." | Render at least one control or layout element, or drop the blocking message. |
| "watches 'x', which is not the key of any control." | Usually a renamed or deleted control. Point the rule at a key that exists. |
Parts
These come from Parts. See Parts for what each field does.
On a plan below Pro, a project that uses parts, or links options to your products, publishes with a warning instead: "Linked products and parts need the Pro plan. This project still publishes on your plan for now, but a later update will refuse it: upgrade your subscription, or remove them in the Composer." Upgrade, or take them out, before that update arrives.
The refusals in this table and in the next one are collected together and reported as "Publish blocked - the pricing configuration has values that cannot be charged: ...". The message names up to five of them and then says "and N more", so clear the ones you can see and publish again to reveal the rest.
| The refusal | The fix |
|---|---|
| "two parts share the id." | Give one a different id. |
| "belongs to a part that is not in the list." | Pick its parent again, or clear it so it becomes a top-level part. |
| "is inside itself." | A part cannot be its own parent, directly or through its ancestors. |
| "is nested too deeply." | Flatten the assembly. The message names the limit. |
| "and the parts it sits inside multiply out to N." | A child's quantity multiplies its parents'. Lower a quantity somewhere in the chain. |
| "cannot carry its own price and a linked product at the same time." | Clear one of them. |
| "is charged, so its quantity has to be a whole number of things to ship." | Use a whole number. A part with no price and no link may hold a measurement. |
| "is priced and marked as already part of the base price, but it links no product." | Clear Already part of the base price so the price is charged, or link a product. |
| "cannot be negative - a part adds to the price, it does not subtract." | Use a price formula for a reduction. |
| "unitCode is not one of the units a part can be counted in." | A part is counted, never measured out, so the length, area, volume and mass units are not available. |
| "picks a variant of one product, which Shopify charges at its own price on a line of its own, so it cannot be part of the base price." | Untick Already part of the base price on the part, and lower the base price by what the part costs. |
| "picks a variant of one product, so it cannot also link a fixed product or carry its own price." | Clear the link or the typed price. |
| "has a product option that names no control and no fixed value, so no variant can ever be chosen for it." | In the part, choose a control or a fixed value for every option of the product. |
| "lists a variant that does not have one value for each of the product's options." | Refresh the part in Composer, which reads the variants from the store again. |
| "is not an id the store gave." | The same: refresh the part in Composer. |
| "lists a value of a product option twice among the ids it read from the store." | The same: refresh the part in Composer. |
| "picks a variant of one product, so checkout names it by its id." | Give the part an id of at most 100 letters, digits, dots, dashes or underscores. |
Priced options and quantities
| The refusal | The fix |
|---|---|
| "two controls share the key." | Give one a different key. |
| "has two options with the value 'x' - the total would count both while the cart charges one." | Give one a different value. |
| "an option may link at most 10 products." | Split the choice, or move some of the items into Parts. |
| "control, which draws no quantity stepper." | A shopper quantity belongs on a dropdown, radio or checkbox option. |
| "is on a control the theme renders itself, so no stepper is drawn." | Switch the control to one 3D Bits draws, or drop the quantity. |
| "is already the key of another control or option.", "both carry their shopper quantity as the input." | Rename one of them. |
| "is above its max", "is outside the allowed range." | Correct the range on the option's quantity. |
| "nests conditions more than 10 deep - checkout cannot evaluate it." | Simplify the condition. |
| "the most this option can charge - its price times the quantity a shopper may choose - stops being represented exactly." | Lower its price, its linked quantity, or its maximum quantity. |
| "which has a second equally short spelling that means the identical value." | Round the number the message names to fewer digits. |
Turning the price into a real charge
These run at the moment you publish, and most of them read your Shopify catalogue to do it. Charging methods explains the methods they refer to.
| The refusal | The fix |
|---|---|
| "some linked prices are missing, so the displayed price would not match what is charged." | Re-link the products in Composer so each link carries a price, and publish again. |
| "shoppers could not add these to the cart at all, because the linked product costs more than the option charges." | Raise the option's price to at least the linked product's, or unlink it and charge a plain price. |
| "a product linked to option 'x' no longer exists, and that option ships N products together." | Re-link or remove that product. |
| "a product linked to option 'x' could not be read from Shopify (...), so it cannot be confirmed that the products this option ships would reach the order. Please try publishing again." | Shopify could not be asked. Publish again. |
| "shoppers could not add this to the cart at all: 'part' is linked at the product level, not a specific variant." | Open each part the message names in Parts and pick a variant of that product, or clear the link and give the part its own price. |
| "shoppers would get 'Cannot find variant' at add-to-cart." | A product the configuration charges through is not purchasable: deleted, unpublished, or with no available variant. The message names each one. |
| "the variant matrix needs a linked product on this project." | Link a product, or use a different charging method. |
| "Variant matrix charging generates variants on ONE product, and this project is linked to several." | Link one product per project for the variant matrix, or use Product lines charging. |
| "the generated variant matrix produced no matchable variants." | Check the priced options, or use a different method. |
| "this configuration cannot be charged ..." | For the selections it names, the options chosen charge less than the products they add. Raise their prices by at least the amount the message names. |
| "... one cart line can carry - shoppers choosing it would get no cart at all." | Lower the configured total, or charge more of it through linked products or the options' own products. |
| "in Product lines charging the base price is this product's price in Shopify, and a shopper who picks a variant pays that variant's price as the base." | Set the product's price to the base price on the project page or in Shopify, or set the base price to its price in Composer. |
| "in Product lines charging the base price is this product's price in Shopify, and a part linked to a product adds that product to the cart at its own price ..." | Untick Already part of the base price on each part the message names, and lower the base price by what they cost. |
| "linked product costs something different in Shopify now (...), and this configurator saves that product at more than one price ..." | Sync the prices, or give the product the same price everywhere this configurator links it, and publish again. |
| "linked product costs something different in Shopify now: ... Bundled parts charging sets every part's price from what you published ..." | Publish from the project page, then press Sync prices and publish when it appears there to adopt what your catalogue says. Like every publish from that page, it puts the saved draft live. |
| "a part picks a product's variant ...", and the other refusals about parts picked from your variants | Each is explained in Pricing troubleshooting. |
| "the configured pricing rules are ... needed to verify a cart of ..." | Reduce the priced options and conditions, or use Variant matrix charging. |
| "even a single configured item cannot be verified at checkout: ..." | The project asks too much of checkout, and the message says where. Use fewer priced options and parts, simpler conditions and plain numbers rather than expressions, and reuse one expression across parts. Managing complexity goes through it. |
| "could not verify the companion charge products are purchasable (...). Please try publishing again.", "Shopify did not answer with a price for ..." | A read from Shopify did not come back. Publish again. If the message goes on to "Also waiting for you, and not a retry: ...", fix what it names there as well. |
| "the store's currency could not be read from Shopify." | Publish again. |
| "could not read this product's own price." | Publish again. If it persists, the product may have been deleted or hidden from the app; check it on the project page. |
| "a product this project is attached to no longer exists, or the app can no longer see it." | Remove it from the project on the project page, then publish again. |
| "a product this project is attached to has more variants than can be checked." | Attach a product with fewer variants, or use Single line or Variant matrix charging. |
Store-side plumbing
These are rare, and none of them is caused by anything you authored.
| The refusal | The fix |
|---|---|
| "pricing enforcement could not be provisioned ... Try publishing again.", "generated catalog failed: ...", "variant matrix generation failed: ..." | A step against Shopify failed part-way. Publish again: it is safe to repeat. |
| "metafield definition could not be created ...", "Shopify did not answer when asked whether the ... metafield can be read at checkout ..." | Publish again. |
| "metafield definition exists without storefront read access ..." | Delete the pricing metafield definitions the message names in your Shopify store settings, then publish again. The app recreates them. |
| "the checkout validation could not be activated ..." | Open the app from your Shopify admin, accept any permission prompt, and publish again. If it persists, reinstall the app. |
| "the Cart Transform could not be activated ..." with Single line charging | Publish again. If it persists, reauthorise the app or switch to Product lines or Variant matrix charging. |
| "the 3D Bits Cart Transform is not installed on this shop ...", or "switched off", with Bundled parts charging | Open the app from your Shopify admin, accept any permission prompt, and try again, or switch to Product lines charging. |
| "with ... the bundle cannot be assembled from its parts ..." | The message says what to change for the configuration it names, or charge through Product lines. |
| "one part of the bundle ships ... units, over the ... one nested part may carry" | Shopify limits how many of one part a bundle may hold. Lower that part's quantity per set, or charge through Product lines. |
| "a shopper may order up to ... of this configuration, and past ... one of its parts ships more than the ... units a nested part may carry" | Set the quantity control's maximum to the number the message names, or lower that part's quantity per set. |
| "The checkout pricing rules from an earlier publish could not be removed from this product. Publish again in a moment." | You see it as "Published, but some products could not be updated." Publish again in a moment: it is safe to repeat. |
| "the Cart Transform could not be activated, so the parts chosen from your variants could not be joined to their product ..." | Open the app from your Shopify admin, accept any permission prompt, and publish again. |
| "3D Bits could not finish setting up checkout for the parts chosen from your variants. Nothing is wrong with your setup - publish again in a moment." | Exactly that. If it keeps happening, contact us. |
| "... 3D Bits also could not put this configurator's helper products back the way your published version uses them, so publish again as soon as you can." | This ends another refusal. Fix what the rest of the message names and publish again soon: until then, shoppers may be charged or refused differently from what the live configurator shows. |
| "the checkout pricing rules disagree with the displayed price (...). This is an internal error - please contact support." | Exactly that. Send us the project and we will look at it. |
Still refused, and none of these fits
Take the message verbatim and send it to info@bitbybit.dev, along with the project file from the button labelled Download project file (scene + editor state) under Files on the bottom bar. Every refusal is deliberate and traceable, so there is always a specific answer.
For what a shopper can be told instead, see Troubleshooting.
Verified against the product in November 2026