Product case study · Pricing and payments
Integrating flexible pricing into the booking flow
Anolla allows service providers to set prices based on the actual booking context: duration, date, time, day of the week, service, customer group, and resource. The same flow can display a discounted price alongside the previous price and require up to 100% online prepayment before confirming the booking.
This technical overview describes how Anolla combines pricing rules, the final price displayed to the customer, and, where necessary, online prepayment into a single controlled workflow.
Pricing conditions can be linked to the service, time, customer, and resource context.
Product configuration capabilityThe final price is calculated and displayed within the same booking flow.
Product design principleA full prepayment requirement can be used as a condition for confirming a booking through online payment.
Optional payment methodWhy is a single static price list not always enough?
A static price list works when the same service always costs the same amount. However, the actual value of a service business may depend on demand, time, duration, the customer relationship, and which specialist, room, or other resource provides the service. Anolla treats pricing as part of the booking logic rather than as a separate price tag.
Challenge
A single base price does not always reflect the actual value of a service. Peak hours, seasonal demand, membership discounts, and specialists with different levels of experience may require different prices or durations.
Design decision
Pricing rules are linked to controlled conditions, and the application selects the price that matches the booking context.
Platform outcome
The customer sees the final price before confirming and paying. The discounted price, previous price, and prepayment requirement can all form part of the same purchase decision.
Why does flexible pricing quickly become difficult to manage?
A service provider may want to fill quieter periods with lower prices, charge a different price during periods of higher demand, reward loyal customers, or link the price to the experience and value of a specific resource. If every situation is handled using a separate service or a manually adjusted price, the administrative workload and risk of errors increase.
Pricing also affects the booking duration, availability, and payment. Promotional pricing must be clear to the customer, and when advance payment is required, the booking should not be confirmed until the payment has been successful.
Time and demand
The price may vary by date, time, day of the week, or season.
Customer relationship
Pricing for members, VIPs, or other customer groups can reflect the value of a long-term customer relationship.
Resource
The selected specialist, room, or other resource may affect both the price and the duration of the service.
Payment method
The payment terms determine whether the booking is confirmed immediately or only after a successful advance payment.
Dynamic pricing does not have to mean an opaque algorithm. In Anolla, it means rules that are defined and controlled by the service provider.
Which principles keep flexible pricing manageable?
Flexibility should not make the final price unpredictable. The pricing engine must be based on a clear base price, controllable conditions, an unambiguous rule order, and a result that is visible to the customer.
01 · A base price provides a clear starting point
Every service or offer has a baseline from which special prices and discounts are derived. This keeps pricing manageable and easy to explain to the customer.
02 · Conditions link the price to its context
A rule may take into account the duration, date, time, day of the week, service, customer membership, or selected resource.
03 · Rule ordering produces a single result
If several special prices could apply to a booking, the system follows a predefined priority rather than producing a random result.
04 · The final price is displayed before confirmation
The customer sees the price at which they are booking, whether a discounted price has been applied, and whether online advance payment is required for confirmation.
How does the pricing context flow into the final price and payment?
The conditions defined by the service provider feed into a unified pricing logic that calculates a single verifiable final price. The customer sees the result before confirming, and the confirmation can be linked to an online prepayment if required.
Pricing inputs
Pricing rules
Conditions · priorities · final price
Rules are evaluated in a defined order so that the same booking produces a single, controllable result.
Customer outcome
The conceptual diagram illustrates the pricing decision flow, not the complete technical architecture of Anolla's internal systems.
Which pricing scenarios can be supported by the same engine?
The service provider does not have to choose a single universal pricing method. Different rules can be created around the same service or resource depending on the demand, customer relationship, or value to be managed.
| Scenario | Pricing condition | Result shown to the customer | Business objective |
|---|---|---|---|
| Off-peak special price | A specific time, day of the week, or date range. | A special price based on the booking time without manually changing the price list. | Direct demand toward periods with lower occupancy. |
| Seasonal or event pricing | A promotion, holiday, season, or specific event period. | A temporary special price available only during the specified period. | Align the offering with demand or campaign objectives. |
| Member or VIP pricing | Customer membership or another specified customer group. | A special price applied to eligible customers. | Reward loyal customers and reinforce the value of membership. |
| Resource-based pricing | The selected specialist, room, device, or other bookable resource. | A price suited to the resource and, if necessary, a different duration. | Reflect differences in experience, equipment, or demand. |
| Visible discounted price | A discounted price activated by the service provider. | Discounted price displayed alongside the crossed-out previous price. | Make the savings clearly visible at the moment of purchase. |
| Online prepayment | A provider-defined prepayment share of up to 100%. | The booking is confirmed only after a successful Stripe payment. | Link booking confirmation to the actual receipt of payment. |
How does the base price lead to a confirmed and paid booking?
Pricing is determined through a sequential and controlled decision flow that the service provider can configure according to its business model.
Set the service's base price and duration
The base configuration defines the price and duration used when no special pricing rule applies.
Select the context that affects pricing
A rule can be linked to a date, time, duration, customer membership, service, or resource, for example.
Set a special price or discounted price
The service provider decides which price applies to the customer when specific conditions are met.
Set clear priorities for overlapping rules
A predefined order results in one clear final price even when multiple conditions apply.
Display the price before confirmation
Before making the purchase decision and payment, the customer sees the final price and, when a discount applies, the previous price as well.
Verify the prepayment and confirm the booking
If online prepayment is required, the final confirmation is issued only after successful payment.
What exactly do the claims in this case study mean?
This is a product case study, not a customer story or evidence of guaranteed revenue growth. The page describes the configuration logic of Anolla's pricing module and how pricing, discount display, and online prepayment can form a single booking flow.
Basis of capability
Anolla's pricing settings, resource and service logic, discounted price display, and Stripe-enabled online prepayment flow.
Functional evidence
Example scenarios for time-based, customer-group-based, resource-based, campaign-based, and prepayment-based pricing.
Use of data
The case study does not use any customer's price list, revenue, conversion rate, or other identifiable business information.
Interpretation
Here, “dynamic” refers to a rule-based price that changes according to context, not an autonomously determined algorithmic price or one that predicts demand.
Limitations. The quality of pricing rules depends on the service provider's configuration. Overlapping rules or rules with unclear priorities may result in unintended pricing. The service provider is responsible for complying with requirements concerning taxes, pricing information, promotional terms, consumer protection, and refunds. The availability of Stripe and online payments may depend on the country, account, and payment service provider's terms.