Quantity Pricing Table
(BU) Quantity Pricing Table displays the current product's eligible quantity tiers, unit rates, and optional savings. The reached tier is highlighted. For graduated pricing it shows explicit band ranges, including the regular-price band when needed.
On this page
Set Up the Table
- Open Bricks > BricksUltimate > MISC, enable Quantity Pricing, and save. This automatically registers the Table and Progress elements.
- Create and publish an active pricing rule, checking sale products, roles, dates, and overrides.
- Open the single-product template in Bricks and add (BU) Quantity Pricing Table near the purchase form.
- Leave Product / variation ID empty to use the current product. Keep Cart + product quantity input for a purchase preview.
- Set the heading and column labels. Choose whether to show savings and make tier quantities clickable.
- Style the element, save, and test the actual product page. Change quantity, add products, and select variations to verify the active tier and final cart price.
All Content Controls
| Control | Purpose and behavior |
|---|---|
| Product / variation ID | Optional explicit WooCommerce product or variation ID; dynamic data is supported. Empty uses the current product context, including a product loop. |
| Quantity source | Choose Cart + product quantity input to preview the pending purchase plus eligible cart units, or Cart quantity only to show purchased units only. |
| Custom quantity selector | Optional CSS selector for the intended quantity input. Otherwise the element finds a matching WooCommerce form.cart in its product/loop scope. |
| Hide when no eligible rule | Hides the complete frontend element when no offer matches. Turn it off to show your no-rule or choose-variation message. It does not create eligibility. |
| Heading | Optional heading above the table. Leave empty when your surrounding layout already supplies a heading. |
| No rule message | Text shown when no rule is eligible and the hide option is off. |
| Choose variation message | Text for a variable parent without a selected variation, when the element is allowed to remain visible. |
| Show savings per unit | Adds or removes the savings column. Savings compare each row's rate with the eligible base price, not with the whole order total. |
| Click tier to set quantity | Turns quantity labels into buttons in product-input mode. Clicking changes a matching input; it does not add products. Cart-only mode does not offer tier selection. |
| Quantity / Unit price / Save / unit | Custom column headings. Changing the text does not change how prices or savings are calculated. |
Connect the Correct Product and Quantity
The default lookup uses the closest product/loop scope, then finds a WooCommerce add-to-cart form matching the configured product or variation. For a variable parent, the selected variation ID determines the offer. Selecting another size or color refreshes its own eligible tiers.
Use an explicit ID for a table on a landing page, sidebar, or layout without a current WooCommerce product. If no matching quantity input is present, input mode previews one unit. That can still display an offer, but tier buttons cannot operate without an input.
Use a unique selector when you intentionally connect a nonstandard input:
#wholesale-purchase input[name="quantity"]
The selector targets an input, not its wrapper or an Add to Cart button. Custom selectors are resolved at page level; use an ID or another unique scope so repeated cards do not all target the first input.
Counting example: two units already in the eligible cart plus an input of three preview five units. In mixed mode, those existing units may belong to other eligible products using the same winning rule. Cart-only mode ignores the purchase input.
Read Volume and Graduated Rows
Volume
Labels such as 3+ and 6+ identify minimum quantities. The next row starts the next tier. The reached tier's rate applies to every eligible unit of that product. A shared group can choose the tier, but each product's base still determines its own percentage or fixed-amount adjustment.
Graduated
Rows show ranges such as 1-2, 3-5, and 6+. The first row uses regular eligible pricing when the first discount begins above unit 1. Each row's unit price applies to its band only. The final cart uses a blended unit price to represent all occupied bands.
With a 100 base, 3-5 at 90, and 6 onward at 70, six units cost 540, not 420. The row showing 70 is not a promise that all six units cost 70. The pricing note identifies graduated rates and combined groups. See the full pricing examples and mixed-group allocation.
Rates follow WooCommerce's shop tax-display and currency-format settings. The table does not include shipping or calculate the complete checkout total. Its savings column is a per-unit comparison for that rate, not the total savings across a graduated order.
What Happens When a Customer Clicks a Tier?
The element subtracts eligible quantities already in the cart from the selected threshold, then updates the matching product input. With two eligible cart units, clicking a 6+ tier normally sets the pending quantity to four.
Minimum, maximum, and step attributes on the input still apply. Quantity is rounded upward to a valid step where needed; an unreachable threshold cannot raise the value above the maximum. Clicking a lower tier cannot remove units already in the cart. The quantity input does not go below its own minimum.
The customer must still click Add to Cart and satisfy stock and required-option validation. The table is not a quantity-rule manager: it does not create purchase minimums, pack sizes, or a new input step.
Customize the Appearance
In Appearance, the Heading, Table heading, Rows, Active tier, Tier button, and Message controls provide typography, color, background, padding, and border settings. Normal Bricks root styling controls remain available for the outer element.
Keep the active state distinguishable without relying only on subtle color differences. Check that long labels and your currency amounts fit on mobile. The default table wrapper allows horizontal scrolling if necessary rather than forcing text outside the page.
For a targeted CSS override, scope it to your element ID or custom class. Useful selectors are .bu-qp-table-wrap, tr.is-active, .bu-qp-tier, and .bu-qp-pricing-note. Prefer builder controls for supported styles. Do not hide the graduated/group context in a way that makes the displayed rate misleading.
Builder Preview and Demo Data
Real eligible rules take precedence in the editor. When no product or rule is available, a builder-only sample shows three tiers at 3+, 5+, and 10+, with one highlighted row. Your labels, savings toggle, and styles apply to that sample.
The demo is server-rendered, does not request prices through AJAX, and cannot change quantities or cart contents when clicked. It never appears on the public frontend. Testing a real customer role, sale policy, or cart total must be done on the storefront.
Product Loops, Quick View, and Cart Layouts
- Single product: keep current-product context and use the matching purchase input.
- Product loop: place it inside the repeated product item. Use unique scopes for any custom input selector. A variable parent still needs a selected variation from a matching form.
- Quick View: include it with the product's normal AJAX-loaded purchase form. Newly inserted elements initialize automatically; test the popup's product IDs and required variation selections.
- Mini-cart or checkout: supply the intended product context and choose Cart quantity only. It is not an aggregate table of every offer in the cart.
A table with a manual product ID can be placed elsewhere for information. Click-to-set requires a matching form/input on that page. Pricing rules continue to work even if the table is not present.
Troubleshooting
| Symptom | Check |
|---|---|
| Element is missing from Bricks | Enable Quantity Pricing in MISC, save, and reopen the editor. Do not look for a separate Table activation switch. |
| Frontend table is hidden | Check the actual product/variation rule, active/published state, role, sale exclusion, dates, and overrides. Disable Hide when no eligible rule to reveal the configured message. |
| Builder works but frontend does not | The builder may be showing the demo. It does not create or confirm a real offer. |
| Tier buttons do nothing | They are read-only in the builder. On the storefront, verify input mode, click-tier setting, matching input selector, and the input's maximum/step. |
| Wrong active quantity | Check whether the source includes a pending purchase and whether the winning rule combines products. Existing cart units are included intentionally. |
| Request fails after leaving a page open | Reload to refresh the nonce. Check AJAX/cache/security errors. A failed request clears stale prices and provides Retry. |