Quandoo's official notice, "An Important Update on Quandoo Services", sets out the wind-down. The two dates most restaurants need in front of them: 30 September 2026 is the last day a diner can make a new reservation, and 31 December 2026 is when the website, app and all remaining infrastructure are permanently taken offline (checked 2026-07-24 against Quandoo's official update).
The gap between those dates is a working window, not an extension. This guide turns it into a dated checklist a restaurant can actually run: what to export, how to verify it, what consent law allows, where Quandoo links hide on your website and Google profile, and what to sweep up after the lights go out. Official deadlines and restaurant actions sit in separate rows throughout — one set is fixed, the other is yours to move earlier.
TableSpark builds restaurant websites and direct-booking tools, so our commercial interest is plain. The checklist should be useful even if we never make your shortlist.
The official timeline, verified
Quandoo's notice contains five dated milestones, not two. All five were re-verified against the official page on 24 July 2026:
- 24 March 2026 — the closing-down announcement, with Quandoo remaining fully available for discovery, reservations and dining until 30 September 2026.
- 30 June 2026 — the last day to earn loyalty points; eligible points remain redeemable until 30 September 2026.
- 30 September 2026 — the last day to make a new reservation, the last dining date that can be selected when booking, and the final day to redeem loyalty points.
- 1 October 2026 — all consumer services will have ended. The official wording is worth reading closely: the website and app "may remain accessible in a limited, static form until fully taken offline, but no reservations, loyalty point redemptions, or account activity will be possible."
- 31 December 2026 — the website, app and all remaining infrastructure are permanently taken offline.
Two further official statements are easy to miss. First, reservations that already exist with a dining date after 30 September remain valid, and Quandoo says it "will provide the restaurant with all the necessary details for your visit". Second, anyone can request a copy or deletion of their personal data at any time via dataprotection@quandoo.com.
For planning, the migration-critical subset is three dates: 30 September (bookings stop), 1 October (services have ended) and 31 December (everything goes offline). The March and June milestones are already behind us; they are included so you see the complete official timeline, not a curated slice. Recheck the official update on the day you act — this is a dated guide, not a substitute for the current notice or your contract.
The migration checklist at a glance
Every row below is either an official deadline (fixed by Quandoo's notice, checked 2026-07-24) or a restaurant action (a recommendation you can and should schedule earlier rather than later).
- Now — this week · restaurant action — Export guest records and future bookings as CSV from your Quandoo business account, then verify the files (Step 1).
- Now — this week · restaurant action — List every place a Quandoo link or widget lives: website, Google Business Profile, social bios, QR codes, email signatures, printed cards.
- By late August 2026 · restaurant action — Shortlist replacement routes and test them with real operating scenarios (Step 6).
- By mid-September 2026 · restaurant action — Replacement booking route live on your own website, tested end to end from a phone.
- By mid-September 2026 · restaurant action — Point your Google Business Profile booking link at your own site (Step 5). No reason to wait for the deadline.
- 30 September 2026 · official deadline — Last day for new reservations, last selectable dining date, last loyalty-point redemption (checked 2026-07-24).
- 1 October 2026 · official deadline — All consumer services have ended; the site and app may linger in a limited, static form (checked 2026-07-24).
- First week of October 2026 · restaurant action — Logged-out link sweep from a phone; replace or remove every route that still lands on Quandoo.
- First week of October 2026 · restaurant action — Reconcile every booking with a dining date after 30 September into your replacement diary.
- By 30 November 2026 · restaurant action — Make and verify a final export after reconciling late changes; keep both untouched originals.
- 31 December 2026 · official deadline — Website, app and all remaining infrastructure permanently offline (checked 2026-07-24). Platform data access ends with it.
- January 2027 · restaurant action — Post-shutdown sweep: dead links, redirects, third-party listings (final section).
The rest of this guide works through the rows that need more than one line.
Step 1 — Export and verify your data while the tools still work
Do not begin by comparing replacement homepages. Begin with the information that becomes harder to recover once a service winds down: your guest records and your future bookings.
Use the export in your Quandoo business account, or ask support which route applies to your account — accounts differ, and the official notice sets deadlines without promising every dashboard an identical button. Export guest data and future-booking data as CSV.
Then verify the export. A file that exists is not yet a migration backup:
- 1 — Open every CSV in a spreadsheet application.
- 2 — Confirm the header row is readable and the columns have not collapsed into a single field.
- 3 — Check that booking dates extend past 30 September 2026 where you expect them to.
- 4 — Compare a small sample against what your business account currently shows.
- 5 — Keep the untouched original and make a separate working copy.
- 6 — Store the original somewhere secure that is not one employee's laptop.
- 7 — Record who can access it and the date it was exported.
Useful fields, where your export contains them: guest name, contact details, booking date and time, party size, status, notes, and any recorded marketing-consent status. Treat that as a verification checklist, not a promise that every export carries every field. If a field you rely on is missing, ask support now, while support still exists.
Export early and export twice. The first export protects against delay and surfaces gaps while there is still someone to ask; the final one — by the end of November, after late changes are reconciled — captures the last verified state before the 31 December switch-off.
Step 2 — Reconcile the bookings that outlive the platform
Quandoo's notice says that existing reservations with a dining date after 30 September 2026 remain valid, and that it will provide restaurants with the necessary details for those visits (checked 2026-07-24).
Take the reassurance, but do not build your autumn service on it. Those bookings were made on a platform that will have ended consumer services, guests can no longer manage them there, and your team needs one authoritative diary. So:
- Cross-check every post-30-September booking in your export against whatever Quandoo passes to you.
- Enter each one into the replacement diary — even if that is, for now, a well-kept book by the phone.
- Give front of house a written rule for which system is authoritative from 1 October.
- Where you have contact details and a lawful basis, confirm the booking directly with the guest. A short service message about an existing reservation is operational, not marketing.
A double-booked Saturday in October because two diaries disagreed is the most avoidable failure of this whole migration.
Step 3 — Consent and GDPR: what the export does and does not permit
The CSV you exported contains personal data, and UK GDPR applies to it in your hands just as it did in Quandoo's.
The safe operating rules:
- Limit access. The export lives in one secure location, with a named list of who can open it.
- Retain with a reason. Keep what the restaurant has an operational or legal reason to keep; delete the rest. "We might want it someday" is not a retention policy.
- Check the lawful basis before contacting anyone. Servicing an existing booking is operational. Adding every exported guest to a marketing list is not — that needs consent or another lawful basis you can point to. If the export records a consent status, respect it; if it records nothing, do not assume consent existed.
- Honour requests. If a guest asks what you hold or asks you to delete it, you now hold the record, so you answer.
One useful official detail: diners can ask Quandoo directly for a copy or deletion of their data at dataprotection@quandoo.com — the address to give a guest who asks about Quandoo's copy.
A migration does not convert an operational booking record into marketing permission. Restaurants that treat the export as a ready-made mailing list tend to learn the distinction the expensive way.
Step 4 — Remove the widget from your own website
If your website carries a Quandoo widget or "Book now" link, it has a hard shelf life. After 30 September it can no longer take a booking; after 31 December the script or page behind it no longer exists. A button that opens a dead page is worse than no button — it tells the guest your information cannot be trusted.
The sequence matters:
- 1 — First make the replacement route live — your own booking form, your new provider's widget, or a clearly-worded enquiry route.
- 2 — Then remove the Quandoo embed code, buttons and links from every page. Check the obvious booking page, and then the footer, the contact page, the menu page and any landing pages an agency built years ago.
- 3 — Test from a logged-out phone: search your restaurant by name, open your site, and follow every booking prompt to its destination.
If your website itself is the problem — old, agency-locked, or unable to take a booking route at all — that is a separate, solvable job. Our guide to building a restaurant website covers it from domain to launch.
Step 5 — Update your Google Business Profile booking link
For many restaurants, more guests reach the booking route through Google than through the website itself. A Google Business Profile can carry Quandoo in several places: the reservation link, a "Book a table" action, or a URL a well-meaning manager pasted into the description years ago.
- Sign in to the Google account that manages the profile and open the links section.
- Replace any Quandoo reservation URL with your own site's booking page.
- Check the website field, the description and any posts for stray Quandoo URLs.
- If a booking link was placed by a third-party integration rather than by you, you may not be able to edit it directly — flag it and check again in October, when the integration should have been withdrawn.
Do this in September, not December. Every week the profile points at a closing platform is a week of guests hitting a dead end at the exact moment they were trying to give you their custom.
Step 6 — Choose and test the replacement route
Quandoo may have been doing two different jobs for you, and they need separate decisions. The first is the booking route — the widget or form that captures the reservation and feeds the diary. The second is marketplace discovery — diners finding a restaurant they did not already know. Replacing the first does not replace the second, and paying for the second is wasteful if most bookings already arrive by name.
Before reporting access disappears, pull the numbers: how many reservations came from the marketplace, and how many started on your own site or by phone? Then write the requirements list with the people who run service:
- Confirmed reservations, or enquiries a person reviews and accepts?
- Table allocation, combined tables, floor-plan views during service?
- Deposits or no-show protection?
- Automatic reminders?
- A diner marketplace for discovery?
- CSV export of guest and booking data without support tickets?
- Minimum term, notice period, full pricing model — and what a fully-booked Saturday costs compared with a quiet Tuesday?
That last question is the one platforms least like answering; our guide to cutting booking commission works through the maths. Test the shortlist with real scenarios — a deuce, a large party, a change, a cancellation, a date after 30 September — and do not call the migration complete until the person who runs the door can find a future booking and say which system is authoritative.
What TableSpark replaces — and what it does not
Stated plainly, because a migration guide with a hidden sales pitch is just a sales pitch.
TableSpark can replace today: your owned website on your own domain (50 finished templates, SSL on the relevant plan); a live structured menu — photograph the printed menu, the AI drafts the site, and you review every line before it goes live; direct booking enquiries landing in one inbox and building your own guest list; CSV export of guests and enquiries whenever you want it; and first-party, cookieless analytics with one-click erasure. An existing reservation provider's widget can be linked or embedded instead.
TableSpark does not replace: live table inventory, floor plans, automated table assignment, deposits, no-show protection, automated reminders, instant confirmation, or Reserve with Google. Direct reservations here are enquiries — a person reviews and replies; the form does not show availability or confirm automatically. Nor does it replace Quandoo's marketplace: we do not bring you diners who have never heard of you. Restaurants that depend on those capabilities should choose a suitable specialist system, and we will say so if asked.
Building is free until you publish — no card, no clock. Published plans are £19 / £39 / £69 per month, excluding VAT; details on the pricing page. On bookings taken through your own site: 0% TableSpark commission · Stripe's standard card-processing fees apply.
If Quandoo's closure is the push, the switch-from-Quandoo page covers the managed migration — we take your Quandoo export and your menu, build the site, and you review everything before it goes live. Or start building free and see the site before you commit to anything.
After the shutdown: the January 2027 sweep
Once the infrastructure goes offline on 31 December 2026 (checked 2026-07-24), a final pass catches what the autumn missed:
- Dead links. From a logged-out phone, search your restaurant by name and follow every booking prompt — site, Google profile, Instagram bio, Facebook button, TripAdvisor listing. Anything still pointing at quandoo.co.uk now fails.
- Redirects you control. If your site ever had a
/bookor/reservationspath forwarding to Quandoo, point it at the new route rather than deleting it — old bookmarks and printed materials still use it. - Third-party listings. Directories, food blogs, round-ups and local news pieces sometimes link a Quandoo booking page. You cannot fix them all, but claimable listings should carry your own URL.
- Physical materials. QR codes on tables, window stickers and loyalty cards outlive every digital deadline. Scan each one.
- The archive. File both exports and a dated note of what was done. If a guest or regulator asks a question in 2027, that folder is your answer.
Frequently asked questions
When does Quandoo stop taking new reservations?
30 September 2026 is the last day to make a new reservation and the last dining date that can be selected when booking (checked 2026-07-24 against the official update). All consumer services will have ended on 1 October 2026, and the website, app and remaining infrastructure go permanently offline on 31 December 2026.
What happens to bookings with dining dates after 30 September?
Quandoo's official notice says existing reservations with later dining dates remain valid and that it will provide the restaurant with the necessary details. Treat that as a helpful backstop, not a plan: reconcile every such booking into your own replacement diary and, where you have a lawful basis, confirm directly with the guest.
What exactly should I export before the deadline?
Your guest records and future-booking data, as CSV, from your Quandoo business account — then open the files, verify a sample against the live account, and preserve an untouched original. Export once now and again by the end of November after reconciling late changes. If the export route is unclear, ask Quandoo support while support still exists.
Can I use the exported guest list for marketing?
Only where you have a lawful basis — typically recorded consent. Servicing an existing booking is an operational communication; adding every exported guest to a mailing list is marketing, and an old booking record is not consent. If the export carries a consent field, respect it; if it carries nothing, do not assume.
What should I do about the Quandoo widget on my website?
Make your replacement booking route live first, then remove the widget, buttons and links from every page — including the footer and any old landing pages — and test from a logged-out phone. After 31 December the widget's infrastructure no longer exists, so anything left behind becomes a dead end.
Is TableSpark a complete replacement for Quandoo's reservation system?
Not yet, and we will not pretend otherwise. TableSpark replaces the owned website, the structured menu, direct booking enquiries and your guest data ownership. It does not provide live table inventory, floor plans, deposits, no-show protection or instant confirmation — restaurants that need those should choose a specialist reservation system.
What should I check after Quandoo goes offline?
Run a logged-out sweep in January 2027: every booking link on your site, Google Business Profile, social bios and QR codes; any redirects you control; and claimable third-party listings that still point at Quandoo. Then archive your exports and a dated record of the migration.
Start with the export
The calm order is the useful order: export and verify, reconcile the bookings that outlive the platform, fix the consent question before it becomes a complaint, replace the widget and the Google link before 30 September, and sweep the long tail in January. None of it requires choosing TableSpark; all of it is easier with the CSV safely in hand.
Review this guide against Quandoo's official update on the day you act, and again in January 2027 — when it becomes a historical record rather than a live deadline notice.