|
Setting Up Product Pricing
Setting Up Product Pricing

Overview

The Price tab has two columns:

  • Options (left) say what a shopper chooses: who is going (Pax), the one choice that sets the price (a Variant or a Package) and the extras they can add (Add-ons).
  • Prices (right) hold the amounts, grouped by the store they sell through. Each store has a default price structure, and can also have seasonal structures or, for events, releases. Each structure has its own prices, taxes, rules and settings.

Set the options first. The price grid is built from them: with a variant or package, every item gets a price for each pax type; without one, each pax type has its own price. Add-on items get their own price boxes too.

What you type is what shoppers see. “Foreign visitor, Adult 1,500” is entered as 1,500 and shown as 1,500 - there are no supplements to add up. Only add-ons show as “+ amount”.

Try It: the Pricing Playground

The playground below uses the same price editor and pricing engine as your product, loaded with demo products. Pick one, change a price or a rule, and the booking card next to it re-prices straight away. Nothing is saved.

Step 1: Options

Pax: who is going

The pax types are the people a booking counts: Adult, Child, Senior, Student, Couple, Group of 4… Each pax type has its own price (or, with a variant or package, a price for each item), and the shopper picks a quantity of each.

  • A product has one pax option. Its title is internal; shoppers see the pax types.
  • Persons per unit — how many people one unit stands for. A “Couple” is 2, a “Private group (up to 4)” is 4. Capacity, group-size rules and release allocations count persons, not units.
  • Min Qty / Max Qty, Min / Max Age and Gender are optional per pax type.

With no pax option, the product is sold by quantity (kayaks, parking passes, bikes) and has a single Base price per unit.

Variants and packages: the one choice that sets the price

A product can have one priced choice. Add it with Add variant or Add package:

  • Variant — a short choice: residency, duration, route, ticket class (“Egyptian resident / Foreign visitor”, “2 hours / 4 hours”).
  • Package — a bundle: “City tour”, “City tour + sunset cruise”. Packages are shown as bundles, with longer descriptions, and each item can list its locations and languages.

Both work the same way for pricing:

  • The shopper always picks one item; the top item is preselected.
  • Each item has its own price for each pax type (“Foreign visitor · Adult 1,500 · Child 750”). That price is the full price: the pax types have no separate price beside it. Without pax types, each item is the price per unit.
  • Each item is listed as its own option on Google Things to Do, unless you tick Don’t list on Google on the item (e.g. a residents-only price). Items named Domestic start with it ticked, since Google would show a residents’ price to everyone; untick it to list one.
  • A variant and a package are priced the same way. A package’s items can have longer titles and summaries, plus related locations and languages.

Two choices? Combine them into one: “Stalls · Matinee”, “Stalls · Evening”, “Balcony · Matinee”… Anything optional, or that a shopper can take several of, is an add-on.

Adding a variant or package to a product that already has prices copies each pax type’s price into every item, so nothing is lost. Then adjust the items that cost more or less.

Add-ons: extras on top

Add-ons are extras added to the price and never replacing it: meals, a guide, a car, photos, T-shirts, parking. Shoppers choose a quantity, and can take several items.

  • Charged — Per person (each person, optionally a different price per pax type; only on products with pax), Per unit (× its quantity) (per car, per bottle, per T-shirt) or Once per booking (a photo pack, a locker).
  • Required minimum — 1 or more makes the add-on required: the shopper must take at least that many (a car for a private tour). 0 or empty: optional.
  • Max per person — at most this many of the add-on’s items per person (one T-shirt each, any size).
  • People per unit — for per-unit add-ons such as cars or guides: suggests a quantity for the group (one guide per 10 people). It never blocks a booking.

Add-on prices are never multiplied by the number of units in the cart line: two kayaks with a photo pack pay for one photo pack.

Item settings

Open any item to edit it. Besides its title, note, description and translations:

Setting Where What it does
Disabled any item Shown to shoppers, but cannot be selected. Its prices are kept.
Availability variant and package items The weekdays the item can be booked.
Capacity per date / slot pax and variant items At most this many persons per date or time slot with this item (100 male, 90 female; 40 front-row seats).
Max per booking / Max per person add-on items Quantity limits for that item.
Seats add-on items Seats one unit gives (a 4-seater car). A shortfall shows a warning; it never blocks.
Draws stock from add-on items The code of a hidden product whose inventory the add-on uses (10 bikes a day).
Don’t list on Google variant and package items Bookable, but not an option on Google Things to Do. On by default for items named “Domestic”.

Step 2: Prices

Open the store’s default structure and its Prices tab. The grid is laid out as rows, so it fits a phone:

  • Price — one row per pax type (products with pax and no package).
  • Base — one row (products without pax). When there are no options at all, the Base is simply the price.
  • Each variant / package item — a row, with its pax types indented below it (products with a variant or package have no separate pax rows). An All pax types row is one price for every pax type, used unless a pax type has its own.
  • Add-ons — in their own section, the same way.

The price boxes

Box Meaning
List Price The “was” price, shown struck through when it is higher than the Selling Price. Optional.
Selling Price What the shopper pays. The only price rules change.
Cost Price What it costs you (bought in as a reseller, or produced as the owner), for margins. Only with Track Costs on (Configuration → Settings).
Reseller Price A reference price for partners and for ad and marketing return. Only with Track Costs on, and not on Limited products.

Shoppers never see the Cost or Reseller Price.

Empty is not free

  • An empty Selling Price means not priced. The editor marks it with an orange warning, and a booking that needs it is refused. It is never charged as 0.
  • Type 0 to make something free on purpose (a free infant, a free-entry ticket).
  • Turn on FREE for a free product or structure. Its main prices may stay empty; add-ons are still charged.
  • A product with no price above 0 anywhere, and not marked FREE, cannot be booked.
  • A flag icon marks a 0 entered by the pricing upgrade. Type the real price, or 0 if it is free, to confirm it.

How a booking is priced

Per person   = the chosen item's price for that pax type
               (no variant / package: the pax type's own price)
Line total   = Σ (quantity of each pax type × its per-person price)
             + add-ons

Without pax: quantity × the chosen item's price (no variant: quantity × Base) + add-ons.

Example. Residency variant: Egyptian resident (Adult 500, Child 250), Foreign visitor (Adult 1,500, Child 750); lunch add-on 300 per person. Two adults and a child, foreign visitors, with lunch: 2 × 1,500 + 1 × 750 + 3 × 300 = 4,650.

Under the grid, What shoppers see lists each pax type’s full price as the shopper will see it.

Editor warnings

Warnings appear above the grid. They never block saving:

  • Selling Price below Cost Price.
  • List Price not above the Selling Price (no “was” price will show).
  • A price far from the others in its group (a typo such as an extra 0).
  • More decimals than the currency allows (JPY has none).
  • A % rule changing a price by more than 100%.
  • Every item of a required option disabled.
  • A season whose dates overlap another, or a release that never ends.

Price Structures: Stores, Seasons and Releases

A booking is priced from one structure: the store it is booked through narrows the list, then:

  1. Events with releases — the first release on sale (see below).
  2. Seasons — a structure whose Applicable Dates cover the booked date.
  3. Default — everything else.

Removing a structure asks for confirmation. Bookings already taken keep the price they were sold at.

Default

Every store’s first structure is the Default (green chip). It cannot be deleted: use Make default on another structure first.

Seasons

Use Add a price structure in the store’s group, enter its prices, and set its Applicable Dates on the Settings tab. A season prices the booked date, not the day the booking is made. A structure with no dates is never picked over the default. For a weekend or time-slot difference inside a season, use a rule instead.

Another store

Use Price for another store to sell the same product on a second storefront, with its own currency, prices, taxes and rules.

Releases (events only)

Releases are ticket tiers that go on sale one after another: Early bird, General, Final. Each release is a full price structure (prices, add-ons, rules, taxes), so a release can change any price.

  • Add release (in the store’s group, events only) copies the latest release’s prices, rules and add-ons, optionally raised by a %. The new release comes last and becomes the default, so a booking is never priced below it.
  • Settings → Release — Code, Order, Sales open (the first release), and the end: days before the event or on a date.
  • Allocation — tickets sold at this release: a Total, a number per pax type (40 male / 30 female), or both. The tighter one applies. Blank: no limit.
  • A release is on sale from the previous release’s end until its own end or allocation, whichever comes first. Before the first one opens, the event is not on sale. When every allocation is gone and no release is open-ended, it is sold out.
  • When a booking asks for more than a release has left, it is limited to what is left, and the shopper adds the rest at the next release.
  • Show “N left” below — shoppers see “Only 12 left at this price” once fewer than this many remain (default 50). Counts and dates shown are always real.

The event page shows the releases as a ladder: ended (struck through), current, next.

Releases are for events only. Events are not published to Google Things to Do, so release prices never reach that feed. For an experience, use seasons and rules.

Rules

Rules change the Selling Price by group size, date, time slot, lead time or choice. Each price structure has its own rules. They are shown in the purple Rules banner above the prices; click Rules on the right to add, change or reorder them.

Adding a rule

In the Rules dialog, click + and give the rule:

  • A name — shown in purple above the prices and beside each value, e.g. Weekend, 4 to 8.
  • One or more conditions — all must match. Time Slot is Sunset; Schedule any of Weekend and Pax Quantity ≥ 4. A range is two conditions: Pax Quantity ≥ 4 and Pax Quantity ≤ 8.
  • Default for every price (optional) — the price used wherever you leave the rule’s box blank.

A rule sets the price. For a surcharge or a discount, type the price it comes to: “weekends +20%” on a 100 adult price is a Weekend rule with 120. New rules are added to every price structure of the product unless you untick Add new rules to every price structure; each structure keeps its own copy, so a season or a release can have different values.

What a rule can test

When Applies to What it holds
Pax Quantity products with pax Persons in the booking (a Couple counts 2).
Order Quantity products without pax Units in the cart line.
Option any The pax type being priced and the items chosen.
Schedule experiences A schedule covering the booked date or slot (weekends, peak months).
Time Slot experiences booked by date and time The booked slot.
Days Before Event events Days from today to the event.

Entering the values

Under every price, one purple row per rule holds that price’s value for it:

  • Type a value where the rule applies: “Adult 90, Child 60” for a 4–8 group.
  • Blank uses the rule’s default. With no default, blank means the rule does not change that price, and the next matching rule is tried.

How rules combine

For each price, the rules are tried in the order listed in the Rules dialog: the first matching rule with a value sets the price, and the result is rounded to the currency. Put combinations first: Weekend, 4 to 8 above Weekend and 4 to 8. Use the arrows in the dialog to change the order. A booking whose price would go below 0 is refused. Rules change the Selling Price only; the List Price stays as typed.

Rules on add-ons

The banner’s rules price the persons and the variant or package. An add-on price has its own rules instead: click Rules (n) under the add-on price. Each sets that add-on’s price when its conditions match — for example Option any of Child for a child meal, or Time Slot is Sunset. Its rules show in purple under the price, where you can change their prices. When several match, the highest price applies.

A condition using is not also matches when the fact is missing: a pass with no date matches “Schedule is not Weekend”. Use is not only for facts that every booking has.

Recipes

Every recipe has a demo product in the playground above.

You want How Demo
One price × quantity No options: the Base price. Phuket Festival Parking
Adult / child prices Pax types, each priced. Bohol Countryside Farm Day
A couple or private-group ticket A pax type with Persons per unit 2 or 4. Chao Phraya Dinner Cruise, Istanbul Private Tour
Resident / foreign-visitor prices A Variant (Resident / Foreign visitor) with a price per pax type. Not a rule. Tick Don’t list on Google on resident-only items. Giza Plateau Entry
Silver / Gold, or bundled tours A Package: each item has its price per pax type. Bangkok City Explorer
Two choices (seat and show, ticket and residency) One Package whose items combine them. Cairo Antiquities Museum
A car the group must book A Per unit add-on with Required minimum 1 and Seats. Chiang Mai Countryside Day Tour
Meals at an adult and a child price A Per person add-on priced per pax type. Bohol Countryside Farm Day
Group discount A rule on Pax Quantity (≥ and ≤ for a range), set per pax type. San Francisco Bay Cruise
Peak season A second price structure with Applicable Dates. Doi Inthanon Day Tour
Weekend surcharge A rule on Schedule (weekends) with the higher prices; with group sizes, a combined rule first. Venice Gondola Ride
Sunset slot premium A condition on Time Slot, Set per price. Dubai Sky Deck
Early bird and sell-out tiers Releases, with an end and an allocation. Bangkok Indie Night, Dubai NYE Beach Party
A free event with paid lunch FREE, plus a priced add-on. Manila Founders Meetup

Fees & Taxes

Taxes are created at the organization level first, then added here with Add Tax. For each:

  • Included in price — the Selling Price already contains the tax.
  • Per Order — a flat charge for the whole booking rather than per person.

Add-ons are part of the line: they carry the same taxes, discounts and partner commission.

Settings

  • Internal Name of Plan — up to 50 characters, for your team and reports. For a release, this is the name shoppers see.
  • Currency — the store’s currency.
  • Number of PAX per order — the Min and Max persons a single order may book.
  • Refundable — off by default (non-refundable). When on, attach a Refund Policy.
  • Payment Plan — optionally let buyers hold the booking with a deposit and pay the balance later. A plan is always an offer, never a restriction: the buyer can still pay in full. A flat-amount plan only fits a price in its own currency.
  • Description / Notes for users — up to 100 characters, shown near the Book Now button.
  • Applicable Dates — the dates a seasonal structure covers.
  • Release and Allocation — on releases (see above).

At the bottom of Settings, two fee lines are informational:

  • Order & Payment Processing Fees — defaults to 5% of order value; check your org settings.
  • Marketplace / Reseller Fees — set by your subscription; defaults to 30% of the margin spread, paid by the reseller.

What Shoppers See

  • The booking card — pax types first, then the variant or package, then add-ons, then the total. Variant and package items show their full price, per pax type where it differs; add-ons show “+ amount”.
  • Time slots — each slot shows its price when slots are priced differently.
  • “From” price on listings and in search — the cheapest bookable price for one person: the cheapest pax type with the cheapest item of each required choice, required add-ons at their minimum, at the current release.
  • Estimated prices in other currencies — list them under Show estimated prices in on your organization profile. Shoppers can pick one and see “≈” amounts. They are always charged, taxed and invoiced in the store’s currency.
  • Price changes — if a price changes between adding to the cart and checkout (a release ended, you edited a price), the cart shows the old and new price, and checkout asks the shopper to accept it. It never changes silently.

What Gets Refused

A booking is refused, with a message, rather than priced wrongly when:

  • a price it needs is empty (not priced);
  • an item is disabled, or was removed after the page loaded;
  • the variant or package, or a required add-on, is missing, or two items of the variant are chosen;
  • a quantity is below the minimum, above the maximum, or not a whole number;
  • a rule would take a price below 0;
  • the release is not yet on sale or sold out, or an item’s capacity is used up.