Quantity Pricing Progress

(BU) Quantity Pricing Progress shows how many more eligible units are needed for the next quantity break. It includes customizable progress/success messages and an optional progress bar. It supports volume pricing, graduated bands, individual products/variations, and mixed quantity groups.

Configure the offer first: Enable Quantity Pricing in MISC and create an eligible pricing rule. The element only displays progress; it does not create a discount, add a gift, or set a free-shipping threshold.
On this page

Set Up Progress


  1. Enable Quantity Pricing under Bricks > BricksUltimate > MISC and save. The progress element is registered automatically.
  2. Create an active, published global rule or a valid product/variation override.
  3. Add (BU) Quantity Pricing Progress to the product template near the purchase controls. It can accompany the pricing table, but the table is not required.
  4. Leave Product / variation ID empty for current-product context, or enter the intended ID.
  5. Use Cart + product quantity input for a purchase preview. Choose Cart quantity only for cart/checkout information.
  6. Edit the messages, enable/disable the bar, and style it in Appearance.
  7. Test below a break, exactly at a break, at the highest break, and after a cart reduction.

All Content Controls


ControlPurpose
Product / variation IDOptional fixed or dynamic ID. Empty uses the current product context. A variable parent follows its selected variation.
Quantity sourcePreview eligible cart units plus the purchase input, or use only units already in the cart.
Custom quantity selectorOptional unique CSS selector for a quantity input. Otherwise the matching product form is located automatically. This does not affect cart-only mode.
Hide when no eligible ruleHide the whole frontend element for an unrelated/ineligible product or unselected variable parent. Turn off to show the configured no-rule/variation text.
HeadingAn optional heading above the message. Empty removes it.
No rule messageText when no eligible offer exists and hiding is disabled.
Choose variation messageText when a variable parent still needs a variation selection and hiding is disabled.
Progress messageThe message before the highest tier, with the tokens below. Default: Add {remaining} more to unlock {discount}.
Highest tier messageThe message after the last break is reached. Default: Best quantity price unlocked. This does not necessarily mean checkout has been completed.
Show progress barAdds or removes the bar without removing the text. When off, the bar is absent rather than leaving an empty track.

Message Tokens and Examples


TokenValue
{remaining}Units still needed for the next threshold.
{quantity}Currently counted units according to the source and winning rule's group.
{next}The next minimum threshold.
{discount}The next tier's percentage/amount/price label. Graduated labels identify that the rate belongs to a band.
Add {remaining} more to unlock {discount}.
Your qualifying quantity is {quantity}. Next break: {next}.
Choose {remaining} more eligible units for the next price.

The tokens are supported in the Progress message field. The Highest tier message is custom success text, not another token template. Use text that fits the source: with purchase-preview mode, a tier can be previewed before the customer has actually added those units.

A suitable highest-tier message for a product form is Best quantity price selected. For cart-only mode, Your cart has reached the final quantity tier. may be clearer. Avoid promising free shipping, a gift, or a checkout discount that the quantity rule does not provide.

How Progress Is Calculated


Progress toward the next threshold is counted quantity / next threshold x 100, capped at 100%. It uses the full next threshold, not only the distance since the previous tier. Once the highest break is reached, progress is 100% and the highest-tier message appears.

Situation with breaks at 3 and 6Result
Counted quantity 2One more unit is needed for 3; progress is about 66.67%.
Counted quantity 3The 3-unit break is reached. The next target is 6; progress toward it is 50%.
Counted quantity 5One more unit is needed for 6; progress is about 83.33%.
Counted quantity 6 or moreThe last tier is reached; progress is 100%.

A percentage can decrease when moving to the next target. That is expected: reaching 3 changes the goal from 3 to 6. The message and table identify the new target.

With product-input mode, two eligible units in the cart plus an input of three count as five. Cart-only mode counts two. In mixed mode, eligible units of other products assigned to the same rule also contribute. A product using a different override or winning rule does not contribute.

Graduated progress identifies the next band, not a repricing of all earlier units. Pair it with the graduated table when customers need to understand the complete band calculation.

Style the Message and Progress Bar


Heading and Message controls provide typography, color, background, padding, and borders. Normal Bricks root styling remains available. The bar has separate Track thickness, Track color, and Progress color controls.

Track thickness accepts the available units, such as px or rem. Start with a restrained size such as 6px. The element does not use a fixed/minimum-height layout to create the bar: its fill and track size respond to the control, keeping it aligned without an artificial empty space.

The message uses an accessible status region, and the bar exposes progress values to assistive technology. Preserve readable contrast and do not rely on color alone to communicate eligibility. Motion respects the reduced-motion preference.

For a scoped CSS override, target your element class/ID and .bu-qp-message, .bu-qp-track, .bu-qp-fill, or .bu-qp-pricing-note. Avoid CSS that forces a hidden bar back to display.

Builder Demo Preview


The editor uses a real eligible rule where available. Without one, it renders a builder-only example with a next-tier message and 80% progress. The sample works without a selected product or an AJAX response. Your heading, message, bar toggle, track thickness, and styles still apply.

Turning Show progress bar off removes the sample bar too. Demo data never creates a rule, changes a cart, or appears on the public frontend. On a real frontend page with no eligible offer, the hide/no-rule settings apply instead.

Placement and Refresh Behavior


  • Product pages: use current-product context and purchase-input mode near the form.
  • Variable products: the normal form must supply the selected variation. Switching or resetting it refreshes the offer.
  • Query loops: keep each element within its intended repeated product context. Make a custom selector unique when you supply one.
  • Quick View / AJAX content: newly inserted pricing elements initialize automatically. Test the real popup and form.
  • Cart, mini-cart, and checkout: use the intended product context with Cart quantity only. This is one product/rule's progress display, not a list of every promotion.

Cart additions/removals, quantity changes, coupons, checkout context, and WooCommerce's cart store can refresh pricing. Matching requests are shared and repeated fragment notifications are coalesced; unchanged table rows are not rebuilt. A real context change must still update the message and bar.

Progress is based on product quantities, not cart spend. For a shipping amount threshold, use Free Shipping Notice and configure WooCommerce shipping correctly.

Troubleshooting


SymptomCheck
No frontend messageCheck rule eligibility and the hide option. Selecting a variation may be required. An editor demo is not a real offer.
Bar is missingEnable Show progress bar, verify a real eligible rule, and check custom CSS. If only styling the text, leave the bar off intentionally.
Progress counts one extra unitInput mode previews a purchase. Use Cart quantity only if the display should reflect the cart as it stands.
Progress includes another productThe rule may use mixed grouping. Check which rule each item wins, and whether that grouping is intended.
Bar moves backward at a tierThe next target changed. Progress is measured against that next full threshold, not the previous band interval.
Repeated stale updatesClear cached/minified assets, refresh the page, and check third-party cart listeners. Do not manually trigger a full fragment refresh from every pricing update event.
Error or Retry appearsRefresh an expired session/nonce and inspect the WooCommerce AJAX response, security rules, and cache exclusions.