Revenue assignment for visits in Waitwhile can be managed in four different ways, depending on how your services are set up and how you interact with the system.
Revenue inherited from service prices
Internal revenue by service that overrides price
Fallback revenue per visit
API based revenue assignment
Here’s how each method works.
How to start tracking revenue in Waitwhile
Revenue inherited from service prices
If a visit includes one or more services, and at least one of these services has a price set, revenue can be automatically assigned by summing up the prices of all the selected services.
How to enable
All you have to do is make sure your services have a price set. You can manage this by editing any service and add a price.
Waitwhile will then calculate the total revenue for the visit based on the sum of the service prices.
Internal revenue by service that overrides price
If you do not want your guests to see a service price but you still want to track revenue for internal purposes, you can use Service revenue. This value will override any service price in internal reporting, but will not impact the price guests see.
How to enable
All you have to do is make sure your services have a service revenue set. You can manage this by editing any service and add a service revenue value.
Waitwhile will then calculate the total revenue for the visit based on the sum of the service revenue.
Fallback revenue per visit
If none of the assigned services have a price or service revenue, Waitwhile will look for a Fallback revenue per visit setting.
How it works
If a fallback value is configured, it will be used as the revenue for the visit.
If no fallback is set, and the service prices are not inherited (as described above), then no revenue will be assigned to the visit.
API-based revenue assignment
Revenue for a visit can also be updated programmatically through Waitwhile’s API. This approach allows you to integrate external revenue data sources into the system seamlessly.
Benefits of API integration
Connect revenue data from other systems or sources directly to visits in real time.
Ideal for businesses that need to consolidate data across different platforms.
Monitoring revenue generation
Waitwhile's extensive analytics allow business to monitor their revenue. To access this, go to Account overview > Analytics > Financials. You'll find data on Total revenue, Revenue by location, and Revenue by service.
Handling multiple currencies in Waitwhile
For accounts that require multiple currencies, here’s how Waitwhile manages revenue.
Default currency handling
By default, the currency assigned to a visit will always match the location’s currency.
Service currency and location mismatch
If revenue is inherited from services, but a service has a different currency than the location, Waitwhile will not include that service’s price or service revenue in the visit’s total revenue.
Best practice for multiple currencies
To avoid discrepancies, set up separate services for each currency. Ensure that each service’s currency matches the location’s currency to enable accurate revenue tracking.
Summary of revenue assignment workflow in Waitwhile
Inherit from services: Revenue is the sum of service prices if the configuration is enabled and currencies match.
Service revenue: If a service has service revenue set, it will override the price for internal reporting only.
Fallback revenue: If services do not have prices or service revenues the fallback revenue value will be applied to the visit if set.
API integration: Update revenue via the API to integrate external data.
Currency handling: Ensure that service currencies match the location’s currency for accurate revenue calculation.
By understanding these options, you can effectively manage how revenue is assigned within Waitwhile, ensuring consistency and accuracy across your business operations.