Understanding price models

Price models let you charge different prices for the same product depending on how it is being sold. This helps you manage pricing across eat-in, takeaway, online ordering, kiosk, promotions, customer types, and VAT scenarios.

What a price model is

A price model is a pricing rule attached to a product. Instead of creating duplicate products for every sales situation, you can keep one product and apply different prices through different price models.

For example, one coffee product could have one price model for standard counter sales, another for iWantFed, and another for a timed promotion.

What can trigger a price model

Pinned functions

A pinned function on POS can trigger a different price model. This is useful when staff need to quickly switch a product into a special pricing mode such as takeaway, staff food, or happy hour.

Customer-based pricing

Price models can also be linked to customer pricing rules. This is useful if certain customers or customer groups receive different prices.

Timed pricing

You can use price models for time-based pricing, such as breakfast prices, lunch deals, or happy hour drinks. This helps you change pricing by time without editing the core product each day.

Common uses for price models

• Eat-in versus takeaway pricing
• VAT and non-VAT pricing where rules differ
• Online ordering pricing for iWantFed
• Kiosk pricing
• Customer or account-specific pricing
• Timed offers and promotions

VAT and non-VAT example for cafes

For cafes, price models are often helpful when the VAT treatment changes depending on what is being sold and how it is sold.

A common example is cold takeaway items. Some cold items may be treated differently from hot items for VAT purposes, and takeaway sales can also differ from eat-in sales.

Instead of creating duplicate products, you can use separate price models so the correct price and VAT treatment are applied in the correct situation.

Using price models for iWantFed and kiosk

Price models can be used to keep different sales channels separate.

For example, you may want one price in-store, another for iWantFed, and another for kiosk. This gives you more control over pricing by sales channel without needing to create new copies of the same product.

This is especially useful if online prices include different costs, or if kiosk pricing is used for a specific promotion or simplified menu flow.

Why price models are better than duplicate products

• You keep one core product record instead of multiple copies.
• Your reporting is usually cleaner because sales stay linked to the same product setup.
• Price changes are easier to manage across different channels or scenarios.
• You reduce the risk of one product being updated while another duplicate version is forgotten.

Best practice

• Use clear price model names such as Eat-In, Takeaway, iWantFed, Kiosk, or Happy Hour.
• Only create extra price models when there is a real pricing or VAT reason to do so.
• Avoid creating too many price models if staff will struggle to understand when they apply.
• Keep your in-store default price model clearly identified.
• Review VAT settings carefully whenever a price model is used for a different sales scenario.

Example setups

Cafe example

• Default: normal in-store pricing
• Takeaway: takeaway prices with different VAT treatment where needed
• Cold To Go: used for cold items sold under a different VAT treatment
• iWantFed: online ordering price model

Restaurant example

• Restaurant: standard eat-in price
• Takeaway: takeaway menu price
• Lunch Deal: timed daytime pricing
• Kiosk: self-service screen pricing