In the Pricing settings page create conditions to automatically calculate the price for a booking, or series of bookings.
If you're looking to set up online payments or manage the payment status of your bookings, check out this article!
Pricing rules intro
Skedda'a pricing rules are per booking and can be based on which space(s) is selected, duration, time of the day, day of the week and user tag. If you have another pricing structure such as memberships, banked time, monthly payments, or discount codes check out the FAQs section at the bottom of this article.
Pricing rules can be set up even if you don’t plan on enabling online payments.
For simplicity, we omit the Price and Payment status fields from the booking form when there are no pricing rules configured. To allow System users to manually set pricing for all bookings, enable these fields by creating an no charge pricing rule.
Non-admins cannot edit the price and payment status of their bookings.
Create a pricing rule
Under the pricing conditions area, click + Add condition and select a template that best matches what you're trying to do.
Order matters! If multiple conditions match a booking, the first one in the list will be used to price the booking. For example, if you have a general price for everyone and a discounted price for certain user tags, put the discounted condition at the top. If you need to reorder your pricing rules, use the up/down arrows on the condition number label.
If a booking doesn't match any of your rules, it will be no charge.
Skedda does not add tax to the booking price, so please remember to set pricing based on the final amount the user should pay.
Here's an example of conditions for meeting rooms with a rate of $10/hour, a fixed rate of $40 for bookings over 4 hours, and only $5/hour for members!
Create up to 1000 pricing rules!
How users will see their booking price
If you have pricing rules configured, users will see the price of their booking when they click on the scheduler, as well as in the new booking modal/form and in the booking-confirmation email.
It’s also important to include your venue pricing, booking policies, cancellation policies, and conditions for damages and no-shows in your venue’s terms and conditions. We encourage you to also include this information in the booking confirmation email!
Test out your conditions with our various testing options. Additionally, for a quick test attempt to make a booking whilst logged in as a System user. The general (no user tag) pricing will be shown, and if you select a user to be the booking holder, you'll see the pricing change to respect that user's tags.
How can I change the currency?
You can change your currency under Settings > Basics.
Does Skedda take a cut from my booking price?
No! Skedda does not collect any percentage fee for priced bookings. If you have Online Payments enabled, the payment-processing service (Stripe) may collect a transaction fee.
Can I set up voucher / discount / coupon codes?
We don't currently have a feature that allows users to apply a discount code that would automatically alter the price of their booking. We have two workaround options, though!
Create a discounted pricing rule based on a user tag, and assign that user tag to a user before they make a booking! This discount will remain in place until you remove the user tag.
Using our BNPL ('book now, pay later') payment approach, you can allow users to make bookings without paying upfront. Then, if you want to give a user a discounted rate for their booking, you can go in and manually update the pricing of the specific booking. From there, you can charge the user's card for that discounted rate.
If these won't work for you and you really need a discount code feature, please reach out to us!
How can I set up membership payments?
This will be done using User tags, Quotas, and someway of collecting recurring payments from your users (we suggest Stripe!). Below is a video showing how to set up a recurring subscription / membership in Stripe for your Skedda users. Note: The Skedda and Stripe interface has been updated a little bit since this video was recorded, but the idea is the same!
Email Template to share with new members (change the text in bold!)
Hi name / everyone / all / there / members,
We're delighted to have you join us as a member! Your unique invitation link to Skedda, our scheduling system is: copy and paste the invitation link here
Click on this link and register with your preferred name and email address. You’ll then access our booking system and receive an email to complete your login. You can create a password or create a social login (with Google, Facebook, Microsoft and Twitter).
Please add your card details to your new Skedda account, under the My Profile area. They will be securely synced to our payment processing platform, Stripe, where we will set up your recurring monthly membership subscription. You'll be able to update your card details and personal information directly from Skedda.
Our venue URL address is https://yourvenuename.skedda.com. Save it to your desktop bookmarks download the Skedda app for easy access to your bookings at all times!
Any questions? Contact us at add your phone or email contact.
Your Venue Name
Can I invoice / charge my users monthly / weekly for their bookings?
Sure! This involves a little bit of manual work, but you should be able to do this pretty quickly every time you'd like to charge your users. If you've enabled Online Payments, select the Book now, Pay later approach. When you're ready to charge your users head to the list view, select the time range you'd like to charge for with the date picker, and filter for a specific user. See in the top right their total! Charge your user for this and then mark those bookings as paid.
Here we see that Tom Tested owes us $180 for the month of June:
Can I charge my users for overages on their memberships? Once a user reaches their membership limit, can they pay for one-off bookings?
We really don't recommend this set-up as it can quickly introduce integrity issues with your billing if you consider the lifecycle events that can happen with bookings - namely cancellations and changes. The optimal solution is if you have different "tiers" of membership plans (e.g. Basic with 5 hours per month, Premium with 20 hours per month). If people wish to book above their quota, you would require them to upgrade their membership plan. This avoids integrity issues and gives you a mechanism for gaining more revenue!
There are also two other solutions. Neither of these would solve the integrity problem though:
The user can use a separate email/account for creating their "overage" bookings. This separate account wouldn't have any quotas associated with it and would have pricing applied.
You can setup a linked "paid" variant of each of your spaces (e.g. Room 1 - Quota and Room 1 - Pay per use). Once a user has exhausted their quota for the "quota" variant of the space a System user can remove their "member" tag and they can book for the pay-per-use variant. Then once they are in the next quota period this tag can be re-added.
Can users pre-purchase a certain amount of time ie. banked time ?
We don't have a feature to do this within Skedda. However, this could be done if you manage bookings manually (no self-service bookings) and track how much time a user has booked. We don't recommend this! In most cases our per-booking pricing structure works just as well as banked time. The optimal solution for you could also be subscriptions/memberships. Read more about this option in the FAQs above!
We specifically decided not to implement banked time or credits because it's not convenient or scalable. Such a feature would imply a lot of "snowballing complexity":
Users would want to be able to view/manage their credit balance, “top them up” in the app and get notified if their balance is low. Actively “topping up” such a “credit” is inconvenient.
Users would hope that their credits would last forever, but admins probably wouldn't want this. Having this "use-by-date" configurable would increase complexity.
Admins and users would probably need a way to closely track the history of credit changes over time - some kind of “audit trail”.
Admins may want to “override” the credits of a user (perhaps as part of a promotion or similar).