Restaurant Reservations, Deposits, Cancellations and No-Shows
Share
A useful reservation policy tells customers what they are agreeing to before they confirm, gives staff one consistent process, and records enough evidence to resolve changes or disputes. It should cover party size, arrival time, deposits or card details, cancellation deadlines, late arrivals, no-shows, venue cancellations, refunds or credits, privacy and decision authority.
There is no universal deposit amount or cancellation fee that suits every Australian restaurant. Build the policy around real loss and capacity, use clear terms, check Australian Consumer Law and contract requirements, and obtain legal advice before relying on a fee in disputed or unusual circumstances.
Map the reservation journey
List every booking channel:
- phone and walk-in;
- venue website;
- email or enquiry form;
- third-party reservation platform;
- social messages;
- hotel, concierge or event partner;
- group and function enquiry; and
- staff-created or owner-created bookings.
For each channel, confirm what customers see, what they accept, what payment is collected, what confirmation is sent and where the record is stored. A carefully written website policy does not help if staff take phone deposits without explaining the same conditions.
Use one approved policy and adapt its presentation to each channel. If a third-party platform adds its own terms, clearly identify which terms apply and who handles changes, charges and refunds.
Decide when a deposit or guarantee is justified
Consider the operational risk rather than copying a competitor.
- How much capacity is held?
- Is the booking during a limited or high-demand service?
- Is the venue buying special stock or adding staff?
- Is there a set menu or minimum spend?
- How late can the table realistically be resold?
- Is the customer committing to a function rather than an ordinary meal?
- What does the platform agreement permit?
Possible controls include a confirmation only, card guarantee, per-person deposit, fixed booking deposit, prepayment, or a signed function agreement. Each creates different customer, accounting, privacy and chargeback implications.
Document why the chosen control is proportionate. Review actual no-shows and unrecovered costs instead of treating a fee as automatic revenue.
Write terms customers can understand
The Australian Competition and Consumer Commission explains that contracts include terms and conditions, but they cannot remove consumer rights that exist under law. Price displays must also be clear about mandatory fees.
State:
- venue name and contact;
- booking date, time, duration and party size;
- amount and purpose of any payment or card guarantee;
- cancellation and change deadline;
- what may happen after the deadline;
- treatment of reduced numbers;
- late-arrival and table-release approach;
- process when the venue cannot provide the booked service;
- how refunds, credits or rescheduling requests are assessed;
- whether third-party terms also apply;
- how personal and payment information is handled; and
- where the customer can ask a question.
Avoid vague statements such as “all deposits non-refundable in all circumstances”. The actual legal outcome can depend on the contract, who cancels, the service failure, the amount retained and other facts. Ask an Australian consumer-law adviser to review the final terms.
Capture informed agreement
Give the customer the terms before confirmation or payment. Do not hide a material fee in a link shown only after the booking is complete.
Retain suitable evidence:
- time and channel of booking;
- policy version shown;
- customer acknowledgement;
- payment or token reference, not unnecessary card data;
- confirmation sent;
- later changes and who approved them; and
- communications about cancellation or no-show.
For phone bookings, train staff to summarise the material terms and send them in the confirmation. A tick box that says “terms accepted” is useful only if the terms were accessible and the accepted version can be identified.
Protect personal and payment data
Collect only what the venue needs. A typical reservation may require a name, contact method, date, time, party size and relevant service information. Do not put full card details, sensitive medical information or unrelated personal notes into an open diary or group chat.
Use the booking or payment provider’s approved process for card handling. Restrict staff access by role, remove accounts promptly when people leave and avoid shared logins. Record dietary or accessibility information respectfully and only where operationally necessary.
Privacy Act coverage is not identical for every small business. Check the Office of the Australian Information Commissioner’s small-business guidance and any obligations created by the venue’s activities or providers. Sound minimisation, access control and secure disposal remain useful practices regardless.
Assign staff authority
| Decision | Suggested owner |
|---|---|
| Ordinary booking and permitted change | Trained booking staff |
| Late-arrival table release | Duty manager |
| Deposit collection or approved refund | Manager with payment authority |
| Exception for hardship or unusual circumstances | Owner or senior manager |
| Disputed fee, chargeback or legal concern | Owner plus adviser or provider |
| Suspected data or payment incident | Privacy/security incident lead |
Write limits into the procedure. A junior host should not have to negotiate a disputed group deposit while greeting customers.
Use a consistent booking workflow
Take the reservation
Confirm the date, time, party size, contact details, booking type, service duration and relevant accessibility or dietary information. Explain the material terms and payment requirement.
Send confirmation
Include the booking details, location, arrival instruction, cancellation link or contact, material terms and a way to correct an error. Avoid putting unnecessary personal information in the message.
Review ahead of service
Check large parties, deposits, special requirements, duplicate bookings, unconfirmed changes and tables with operational dependencies. Escalate uncertain allergen requests through the venue’s food-allergen process rather than promising suitability in a booking note.
Send reminders
A reminder can reduce mistakes and give the customer a clear way to cancel or update numbers. Confirm that automated messages display the correct venue, time zone, date, contact and current policy.
Prepare the service
Brief the team on covers, table timing, deposits already paid, authorised package inclusions and matters requiring discreet handling. Do not announce sensitive customer information to the whole room.
Handle late arrivals
Define:
- when the venue contacts the customer;
- any grace period or manager discretion;
- when the table may be released;
- whether the service end time changes;
- how a prepaid or set-menu booking is handled; and
- what is recorded.
Apply the policy consistently while considering the facts. If the venue caused confusion through an incorrect confirmation or unreachable entrance, do not treat the issue as an ordinary customer no-show.
Process cancellations and reduced numbers
When a customer contacts the venue:
- Confirm identity without collecting excessive information.
- Record the time, channel and requested change.
- Retrieve the policy version and booking terms.
- Check the cancellation deadline, payment and costs already committed.
- Ask for manager review where the decision is outside staff authority.
- Confirm the outcome in writing.
- Process any authorised refund, credit or adjustment through the approved payment method.
- Release capacity promptly.
Do not promise a refund or refuse one before checking the contract, service circumstances and consumer rights. If the venue cannot supply the booked service, escalate immediately; the situation is not simply a customer change of mind.
Record and review no-shows
Before marking a no-show:
- confirm the correct date, time and venue;
- check whether the customer cancelled through another channel;
- check messages, platform updates and call records;
- attempt the approved contact where appropriate; and
- have the duty manager confirm the status.
Record the booking, confirmation and reminder status, contact attempt, capacity impact, payment decision, dispute and outcome. Do not create judgemental notes about the customer.
Review monthly or at a frequency suited to volume:
- bookings by channel;
- cancellations by notice period;
- no-shows;
- disputed or refunded charges;
- tables successfully resold;
- booking errors caused by the venue;
- platform failures; and
- customer feedback.
The aim is to improve policy, reminders, availability and staff practice—not build a blacklist without a clear, lawful and fair basis.
Test the policy before launch
Run realistic tests through every channel. Ask a person who did not write the policy to make a standard booking, reduce numbers, cancel inside and outside the stated period, arrive late and dispute a charge. Check whether staff and automated messages give the same answer.
Review:
- whether the customer sees the material term before confirming;
- whether the amount and timing are clear on a mobile screen;
- whether the booking record identifies the accepted version;
- whether a phone staff member can explain the policy without improvising;
- whether a manager can find the evidence quickly;
- whether a refund or credit can be authorised and reconciled;
- whether third-party wording conflicts with the venue’s terms; and
- whether personal and payment data stay inside approved systems.
Record the test and correct the source policy, training and channel configuration together. Repeat the test after a platform, payment-provider or policy change.
Communicate without escalating the dispute
When a customer objects, separate explanation from judgement. Confirm the facts, explain the term and decision, provide the record the customer is entitled to receive, and offer the venue’s complaint pathway. Avoid statements that the fee is lawful merely because “the system charged it”.
Give frontline staff a calm handoff phrase and manager contact. Record abusive conduct separately under the venue’s aggression procedure; a customer’s disagreement about a fee does not by itself justify treating them as aggressive.
Worked scenario: group booking reduces on the day
A restaurant accepts a Saturday booking for 12 with a per-person deposit and clear terms about final numbers. The customer confirms 12, then calls at 11 am to reduce to eight.
The host records the request and does not improvise. The manager checks the accepted terms, timing, special stock and whether the table can be reconfigured or resold. They explain the decision and any adjustment in plain language, then send written confirmation. The POS and run sheet are updated, and the briefing reflects eight covers and the deposit already held.
If the customer disputes the outcome, the manager provides the relevant booking evidence and follows the complaint process. The venue does not argue at the host stand.
Common mistakes
- Copying a fee without assessing actual operations.
- Showing material terms only after payment.
- Using different terms by phone, website and platform.
- Storing card details in notes or messages.
- Promising allergen suitability during booking without verification.
- Letting every staff member negotiate exceptions.
- Charging automatically when the venue caused the problem.
- Marking a no-show without checking other channels.
- Keeping vague or judgemental customer notes.
- Reviewing no-show counts without venue-caused booking errors.
Reservation and cancellation checklist
- ☐ Map every booking channel and third-party term.
- ☐ Decide which bookings need a deposit, prepayment or guarantee.
- ☐ Draft clear terms and obtain Australian legal review.
- ☐ Display mandatory amounts and material conditions before confirmation.
- ☐ Record customer acceptance and policy version.
- ☐ Use approved payment handling and minimise personal data.
- ☐ Assign staff authority for changes, refunds and disputes.
- ☐ Send accurate confirmations and reminders.
- ☐ Review large or unusual bookings before service.
- ☐ Define late-arrival contact and table-release steps.
- ☐ Record cancellations, reduced numbers and no-shows consistently.
- ☐ Escalate venue cancellations and service failures.
- ☐ Review disputes, recoveries and venue-caused errors.
Take the next useful action
Make the same test booking through the website, phone and any third-party platform. Compare the price, deposit, cancellation wording, confirmation and contact path. Record every mismatch and assign one person to reconcile them.
Use the Free Hospitality Checklists to support consistent records. The Restaurant Operations Pack provides editable service controls. For difficult outcomes, use the process in How to Handle Customer Complaints.
General-information limitation: General operational information only. Obtain Australian legal, consumer-law, accounting, privacy and payment-provider advice for the venue’s exact booking terms, deposits, cancellation charges, refunds, credits, chargebacks and record retention. A published policy cannot remove consumer rights.
References
- Contracts, Australian Competition and Consumer Commission. Accessed 25 August 2026.
- Price displays, Australian Competition and Consumer Commission. Accessed 25 August 2026.
- Consumer rights and guarantees, Australian Competition and Consumer Commission. Accessed 25 August 2026.
- Small business privacy checklist, Office of the Australian Information Commissioner. Accessed 25 August 2026.
Source review date: 25 August 2026