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
Fallback revenue per visit
API based revenue assignment
Manual revenue entry in the Staff experience
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.
Fallback revenue per visit
If the Inherit from services checkbox is not selected, or if none of the assigned services have a price, 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.
Edit revenue in the Staff experience
Staff members can manually edit the revenue value directly within the Waitwhile UI. Here’s how to do it:
Click on a visit in the board view to open the visit pane.
In the visit pane, find the Revenue field.
Click the field to enter or edit the revenue value.
After updating the revenue, click Save to apply the changes.
Note: Manually editing revenue will override any previous values, including those inherited from services or set via the fallback or API.
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 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.
Fallback revenue: If services do not have prices, or the option is disabled, use the fallback value if set.
API integration: Update revenue via the API to integrate external data.
Editing revenue in the staff experience: Revenue for any visit can be updated directly in the Waitwhile UI, overriding any previous 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.