Skip to main content

Pricing Settings – Overview

Understand how pricing works in Hoops. Learn how to structure pricing, manage variants, and control how prices appear on SalesDocs, SalesPresentations, and invoices.

Pricing in Hoops controls how your prices are calculated, displayed, and invoiced.

There are three key areas to understand:

  • Pricing Structure (how pricing is presented)

  • Variant Handling (how variants are priced)

  • Presentation Modes (how pricing appears in SalesPresentations & SalesStores)

Use the guides below to choose the right setup for your workflow.


Pricing Structure

Roll-Up Pricing

Combine all costs into a single price per item.

Best for clean, simple quotes where you don’t want to show internal breakdowns like decoration or setup costs.


Itemized Pricing

Break pricing into separate line items.

Best for transparency and detailed quotes where customers expect to see how pricing is built.


Variant Handling

Variant vs Averaged Pricing

Control how pricing is applied across sizes, colors, or other variants.

  • Variant Pricing: Each variant has its own price and invoice line

  • Averaged Pricing: All variants share a single blended price


Hide Variant Breakdown from Customer

Control whether customers see the variant-level detail (e.g. size or color breakdown).

Best for simplifying the SalesDoc when variant detail isn’t important.


How Pricing Modes Affect Invoices

Understand how your pricing setup impacts invoices sent to accounting platforms.

  • Variant Pricing → multiple invoice lines

  • Averaged Pricing → single combined line


SalesPresentation & SalesStore Pricing

Flat Rate vs Quantity-Based Pricing

Control how pricing behaves across quantity breaks for decorations and additional charges.

  • Quantity-Based: Different price per quantity level (pricing grid)

  • Flat Rate: One price applied across all quantities


Pro Tip

Create multiple SalesDoc templates with different pricing setups (e.g. Variant vs Averaged).

This allows you to quickly switch pricing styles depending on the job, without reconfiguring each time.

Did this answer your question?