|
Setting Up Product Pricing & Plans
Setting Up Product Pricing & Plans

Overview

The Pricing section allows you to define how much customers pay based on who they are (Adult vs. Child), where they are buying from (Storefronts), and when they are attending.

Product Stores & The “Default” Requirement

Pricing in Spotinga is organized by Stores. This allows you to have different price points for different sales channels or brands.

  • The Default Store: You must have at least one store set as “Default” in your organization settings. The system requires a price plan for this default store before you can add overrides for others.
  • Store Overrides: Use the “Add” tab to select a specific storefront and create unique pricing for it. This is useful if you want to charge more or less on a premium storefront versus your main site.
  • Cloning: To save time, you can clone an existing price plan into a new one, which carries over all items and rules while letting you change the internal name.

Options and PAX Pricing

Pricing is driven by the Options associated with your product.

  • PAX Options: These are usually your “Base” prices (e.g., Adult, Child, Senior). The system identifies one option group as the primary passenger type. Each item in this group becomes a row in your price list.
  • Product Options: These are add-ons (e.g., “Lunch Included” or “Private Guide”).
    • Per-PAX Rules: If a product option is marked as “Per PAX,” the system can automatically generate price combinations (e.g., “Adult + Lunch”).
    • Base Price: If no options are defined, the system defaults to a single “Base” price item.

Managing Prices

Inside each Price Plan, you manage the actual currency and amounts:

  • List Price (LP): The “crossed-out” price shown to users to indicate a discount.
  • Selling Price (SP): The actual amount the customer pays.
  • Reseller Price (RP): (Visible only if not a limited product) The price offered to partners or marketplaces.
  • Free Products: Use the “FREE” toggle at the top of the Prices tab. This sets the product to 0.00 currency and bypasses payment requirements in the cart.
  • Rule Editor: For advanced setups, you can add rules to individual price items. This allows you to override prices based on:
    • Order Quantity: (e.g., “Buy 10+, get a lower rate”).
    • Schedules/Slots: Specific prices for weekend departures or sunset time slots.

Fees & Taxes

Taxes must be created at the Organization level before they can be applied here.

  • Adding Taxes: Click “Add Tax” to pick from your pre-configured list.
  • Included in Price: Check this if the Selling Price already accounts for the tax (tax-inclusive).
  • Per Order: Check this if the tax is a flat fee for the whole booking rather than per person.

Settings & Guardrails

The system includes several constraints to ensure data integrity and UI performance:

Guardrails

  • Base Price Protection: You cannot delete the “Base” price item or the primary PAX codes. These are core to the product’s existence.
  • Internal Naming: Plan names are limited to 50 characters.
  • Descriptions: User-facing notes are limited to 100 characters and appear near the “Book Now” button.

Limits

  • PAX Limits: Under the Settings tab, you can define the Min and Max number of passengers allowed per individual order.
  • Combination Limit: To prevent the interface from freezing, the system will only auto-generate rule combinations for option groups with fewer than 6 items.
  • Applicable Dates: For non-default plans, you can specify exactly which dates the pricing applies to using the calendar picker. If a date is not selected, the plan won’t be active for that period.

Understanding Fees

At the bottom of the Settings tab, you will see a summary of processing fees:

  • Processing Fees: Usually 5% of order value (check Org settings).
  • Marketplace Fees: Usually 30% of the margin spread for reseller transactions.

Always check the “Internal Name of Plan” in the Settings tab. While shoppers don’t see this name, it is what your team will see in reports and when managing inventory.

Loading...