TL;DR
- Hulk's math field computes a value or price from other fields — area, dimension, quantity-tier, complex quote logic in one field.
- Area-based pricing: width × height × per-square-inch rate. Standard for print-shop, sign, sticker, and canvas stores.
- Dimension-driven cost: custom-cut materials priced by length, custom-frame pricing by perimeter.
- Quantity-tier math: per-unit price that drops at quantity breaks, computed cleanly per order.
- Where math fields beat workarounds: when add-on pricing alone isn't enough because pricing is a formula, not a fixed fee. Verify current Hulk math-field capability on the listing.
What math fields actually do
A math field in Hulk Product Options computes a value — typically a price component — from a formula that references other fields in the configurator. Instead of a fixed add-on fee for an option, the math field can be 'width × height × per-square-inch rate' or 'quantity × per-unit price with tier breakpoints' or any formula your business needs. The result feeds into the total price, often as a clean line item.
For most product-options use cases the standard option/add-on price mechanic is enough — a fixed fee per option, optionally varied by tier. But for any store whose pricing is fundamentally a formula (print shops, sign makers, sticker stores, custom-cut materials, framing, canvas printing, made-to-measure), math fields are what makes the configurator match the business model. See Hulk Product Options field types for the broader field catalog and Hulk variant-based pricing for how pricing combines.
Area-based pricing
The textbook math-field use case. Customer specifies width and height (typically via number inputs with min/max constraints); the math field computes area = width × height; the area multiplies by your per-square-inch (or per-cm²) rate; the result is the per-unit price. Multiply by quantity and you have the line total.
This is essential for: custom signs and banners, custom decals and stickers, canvas prints, large-format posters, custom cut vinyl, fabric panels. Without a math field, the alternative is pre-defining every possible width×height combination as a separate variant — fast variant explosion for any meaningful size range. Math fields side-step that entirely.
Dimension-driven cost
Linear-dimension pricing — cost as a function of length or perimeter rather than area:
- Custom-cut materials: wood molding sold by linear foot, custom rope by length, fabric by yard.
- Custom frames: priced by perimeter (2× width + 2× height) × per-foot rate, sometimes with corner/joinery surcharges.
- Made-to-measure: bespoke garments priced from measurement inputs.
- Custom packaging: corrugated box priced from internal-dimension formula.
Math fields handle the formula in one field rather than spreading the logic across the configurator. The result feels clean to the customer (one transparent calculation) and clean to operate (one source of pricing truth).
Quantity-tier math
Quantity-driven per-unit pricing — discounts that kick in at volume — can be encoded as math-field formulas with conditional breakpoints. Simple example: 1-10 units at $5 each, 11-50 at $4 each, 51+ at $3 each. Math field computes effective per-unit × quantity. This is the same pattern Inkybay handles for sticker stores, but available as a math field within Hulk for stores that need it alongside other options-app features rather than committing to a print-shop-first app.
For complex tier structures (per-tier discount of the difference rather than full quantity at the tier rate), math fields can encode that too with conditional formula branches. The configurator gets more complex; document the pricing model carefully so onboarding new SKUs doesn't require reverse-engineering the formula.
Complex quoting flows
B2B and made-to-order stores often have pricing formulas that depend on multiple inputs: customer-group, material grade, finish tier, urgency, quantity, dimension. A math field can encode the full quote formula, surfacing a transparent per-line calculation to the customer (or, for stores that hide pricing pre-quote, capturing the inputs cleanly for a follow-up quote email).
For very complex quotes the field gets unwieldy; at that point, consider whether the quote should live in a dedicated quoting tool with handoff back to Shopify for ordering. For moderately complex quotes (one or two pricing formulas with a handful of inputs), math fields in Hulk are usually enough.
Math-field pricing + live preview?
Hulk's math fields are powerful for formula-driven pricing. For products where customers also benefit from seeing a live preview of their text/photo/design on the product, layer in a personalizer. Print It My Way runs free, no per-item fees, native Cart Transform pricing.
Install Print It My Way — Free Read Hulk variant-based pricing →Frequently asked questions
What does Hulk's math field actually do?
A math field in Hulk Product Options computes a value — typically a price component — from a formula that references other fields in the configurator. Instead of a fixed add-on fee per option, the math field can be 'width × height × per-square-inch rate' for area pricing, 'quantity × per-unit price with tier breakpoints' for quantity-tier discounts, 'perimeter × per-foot rate' for framing, or any formula your business needs. The result feeds the total price. For stores whose pricing is fundamentally a formula rather than a fixed fee, math fields are what makes the configurator match the business model.
Can I do area-based (per-square-inch) pricing with Hulk?
Yes — area-based pricing is a textbook math-field use case. Customer enters width and height (via number inputs with min/max constraints), the math field computes area = width × height, and multiplies by your per-square-inch rate to get the per-unit price (then quantity for the total). This is essential for custom signs, banners, decals, canvas prints, large-format posters, and custom cut vinyl. Without a math field, the alternative would be pre-defining every possible size combination as a separate variant, which leads to fast variant explosion. Math fields side-step that. Verify Hulk's current math-field capabilities on the listing.
Can math fields handle quantity-tier discounts?
Yes — quantity-driven per-unit pricing (discounts at volume) can be encoded as math-field formulas with conditional breakpoints. Simple example: 1-10 units at $5 each, 11-50 at $4 each, 51+ at $3 each. The math field computes effective per-unit price × quantity. For more complex tier structures (per-tier discount of just the marginal units rather than the full quantity at the tier rate), math fields can encode the formula too with conditional branches — the configurator gets more complex, so document the pricing model carefully. For sticker-store-style print-shop pricing specifically, Inkybay's print-shop configurator is purpose-built; Hulk math fields are the alternative when you also need the rest of an options app.
What about dimension-driven pricing for custom-cut materials or framing?
Math fields handle linear-dimension formulas cleanly: custom-cut wood molding sold by linear foot, fabric by yard, custom frames priced by perimeter (2 × width + 2 × height) × per-foot rate, sometimes with corner/joinery surcharges. Made-to-measure flows where pricing depends on body measurements can also be encoded as math-field formulas. The advantage over scattered option-fee logic is having one transparent calculation that the customer can verify and one source of pricing truth that's easy to audit and update.
Can Hulk math fields handle B2B quote pricing?
For moderately complex quote pricing (one or two pricing formulas with a handful of inputs: material grade, finish, urgency, quantity, dimension), Hulk math fields work — encode the formula and the configurator surfaces a transparent per-line calculation. For very complex B2B quotes with many inputs and customer-group-specific rules layered on, the math field gets unwieldy and you should consider a dedicated quoting tool with handoff back to Shopify for ordering. The threshold is when documenting the formula in math-field syntax becomes harder than maintaining a separate quote-generation system. Trial on a representative quote scenario before committing.
Where do math fields beat fixed add-on pricing?
Whenever the pricing is genuinely a formula rather than a fixed fee per option. Area-based pricing (signs, stickers, canvas) — formula. Dimension-driven cost (framing, custom-cut materials) — formula. Quantity-tier discounts that aren't pre-defined as variants — formula. B2B quotes with multiple inputs — formula. For each of these, fixed add-on fees per option can't express the price; you'd either pre-define every combination as a variant (variant explosion) or use a math field that captures the formula directly. For pricing that genuinely is a fixed fee per option choice, the standard option/add-on price mechanic is simpler and is what you'd use.