Managing complexity
Checkout has only so much time for each cart. Publishing works out how much work your project asks of it and refuses one that asks for too much, rather than let it go live. How much that is depends far more on how many cart lines a configuration adds - parts linked to your products and priced options, in Product lines - than on how many parts with typed prices you have.
This page tells you which choices are cheap, which are expensive, and what happens when you go too far.
The short version
- Parts that carry a typed price are cheap. A hundred of those is not a problem.
- Parts linked to a real product are the expensive kind. Each one ships as its own cart line, and the whole cart may carry about 117 of those lines, so they run out long before typed-price parts do. Around thirty is where it starts to bite.
- Nesting is cheap, far cheaper than one more formula.
- Quantity formulas are the expensive part of the rules themselves, and specifically how many different ones you write.
- Nothing breaks quietly. If a project is too complex, 3D Bits refuses to publish it and tells you what is binding.
The one rule worth remembering
Reuse the same formula text across parts. Do not write a slightly different one for each.
This is the biggest lever inside the rules, and it is not obvious.
Write the same ceil(width / 4000) on thirty parts and checkout has one formula to work out. Write
thirty that differ only slightly, ceil(width / 4000), ceil(width / 4001) and so on, and it has
thirty.
The two projects are the same size. Both publish today, but the shared formula leaves more room for parts and options.
If several parts need genuinely different quantities, prefer one shared formula driven by a different input over many bespoke formulas.
What a project can carry
Rough guidance for Product lines charging, with everything else left simple:
| Your project | Configured items per cart |
|---|---|
| Up to 100 parts with typed prices, fixed quantities, no formulas | 4 (the maximum) |
| 30 parts, six levels deep, all sharing one formula | 4 |
| 30 parts, six levels deep, each with its own formula | 4 |
| 20 parts nested twenty levels deep, one shared formula | 4 |
| Up to about 29 parts linked to real products you ship | 4 |
| Around 35 parts linked to real products you ship | 3 |
| Around 50 parts linked to real products you ship | 2 |
| Around 100 parts linked to real products you ship | 1 |
| 118 or more linked parts in one configuration | refused - will not publish |
"Configured items per cart" is how many configured products a shopper can have in one cart at the same time, each on its own cart line. One configuration bought in a quantity of several counts once. Ordinary products do not count toward this limit. Every publish states the number for the project in its result, whether or not the project lowers it.
Three things to read from that table:
- Fixed quantities cost almost nothing. If a part's quantity never changes, type the number instead of writing a formula for it.
- Depth is not what costs. Twenty levels is barely more than six.
- A linked part is not a cheap part. A part with a typed price is only an amount, but a part linked to a product you ship is a real cart line, and every line is one more thing checkout has to verify. The first four rows assume typed prices throughout - swap those hundred parts for a hundred linked ones and the cart holds one of that product at a time.
Fixed ceilings
These do not move, whatever else you do:
- 4 configured items in one cart
- 20 levels of part nesting
- 1,000,000 units of any single part. Publishing refuses a typed quantity, or a nest of parts whose quantities multiply, past it. A quantity formula that works out more is charged and listed as 1,000,000, so keep formulas inside that range.
Priced options
Each option that adds money goes into the rules, and in Product lines charging each one that is switched on becomes its own cart line. Many priced options therefore cost you in two ways at once. The table below is about Product lines; Bundled parts is counted differently and is covered under Charging methods.
What costs is how many priced options one configuration can have switched on at the same time, not how many you have authored. The boat's Length, Helm, Collection and Planks are radio groups, so they post at most four lines however many options they hold, because a radio group holds one choice at a time. Twenty priced options given a switch each can all be on together, and post twenty. Roughly:
| Priced options a shopper can have on at once | Configured items per cart |
|---|---|
| up to about 29 | 4 |
| around 35 | 3 |
| around 50 | 2 |
| around 100 | 1 |
| 118 or more | refused - will not publish |
A part picked from your variants takes a little more room than an option's line, so it lowers these numbers a little more - see How many configured items fit in one cart.
If you have a great many, consider:
- Combining them into one line. How option charges reach the order, in the project's Storefront settings, charges all options through at most three combined lines instead of one line each.
- Single line charging, which prices everything into the product itself.
See Charging methods for the trade-offs.
When publishing is refused
3D Bits works out the cost before it saves anything, so an over-complex project is caught at publish rather than by a shopper at checkout. The message says, in its own words, which of these is binding:
- The rules are too large: the rules themselves do not fit. Reduce the number of parts, priced options or visibility conditions.
- Too expensive to work out: the rules fit, but checking them takes too long. Use fewer priced options and parts and simpler conditions, share one formula across parts, and replace formulas with fixed numbers where the quantity never varies.
- Too many cart lines: a single configuration would add more lines than checkout can verify. Combine the option lines into one charge, and count what one configuration can have switched on at once: about 117 lines is what the whole cart may carry.
A configuration whose options charge less than the products they add is refused too, whatever its size. The app names the selections and the exact figure at publish.
A project that publishes with a lower cart limit has not failed. It simply means shoppers can buy fewer of that configured product at once, and 3D Bits tells the shopper clearly if they try to exceed it.
The limit can also move at a publish where you changed nothing. When an update to 3D Bits checks more of each configuration, the next publish can show a lower cart limit, or ask you to simplify a project that sat right at the edge.
If you need more headroom
In rough order of how much they buy you:
- Reduce priced options, or combine their cart lines.
- Share one quantity formula across as many parts as possible.
- Replace formulas with fixed numbers wherever a quantity never varies.
- Simplify the formulas themselves - a short expression is cheaper than a long one.
- Split the product into two simpler configurators if it is really two products.
Nesting deeper, or adding more parts with fixed quantities, is nearly free - so restructure toward those rather than away from them.
Verified against the product in November 2026