If you run a restaurant on GloriaFood, the email from Oracle was not a drill. GloriaFood is shutting down on April 30, 2027. The in-app banners say the same thing, new signups have already closed, and Oracle has not named a successor product. After that date, your menu, your customer list, your delivery zones, your order history — all of it stops being reachable.
This post is the calm version of the news. What's actually happening, what stops working, what you lose, and the migration window you have left. No panic, no upsell ladder. Just the facts and a plan that fits around dinner service.
What "GloriaFood is shutting down" actually means
Oracle acquired GloriaFood in 2020 and quietly let it run on its existing roadmap. In early 2026 the in-app banner went live: "This offering will be retired on April 30, 2027." New signups are closed. Partner emails have gone out citing end-of-life status. There is no Oracle replacement coming — this is a wind-down, not a migration to a new product.
That makes it different from a Toast outage or a Square pricing change. You are not switching tiers. The lights are turning off. Every part of the GloriaFood stack — the ordering widget on your site, the Facebook order button, the FoodBooking reservation app, payment processing, POS integrations, marketing campaigns — all of it goes dark on the same day.
Roughly 123,000+ restaurants in 50+ countries are affected, mostly in the US, UK, Canada, Australia, and Latin America. Independents on the free tier and web agencies running the "WordPress + GloriaFood" stack are hit hardest. White-label resellers — agencies that ran a private-labeled version of GloriaFood — lose the entire product.
What dies at cutoff on April 30, 2027
Here's the list that matters, the one you should print and hand to your manager:
- Website ordering widget — every site running the GloriaFood embed shows nothing on April 30, 2027.
- Facebook ordering button — your Page's order CTA stops working.
- FoodBooking reservation app — table reservations route nowhere.
- Payment processing — Stripe / payment connections inside GloriaFood are cut at the platform level.
- POS integrations — every existing GloriaFood ↔ POS bridge (SambaPOS, Squirrel, custom) stops syncing.
- Marketing and promo campaigns — coupon codes, automated promos, loyalty triggers all go offline.
- Admin dashboard — you can't even log in to look at history after cutoff.
This is not a "read-only mode" sunset. There is no archive button. There is no "view your past orders" page that survives.
What data you actually lose
This is where most owners are underestimating the risk. Oracle has confirmed no data retention beyond April 30, 2027. That means the following becomes permanently inaccessible:
- Your menu — every item, modifier group, size, photo, description.
- Your customer records — names, emails, phone numbers, addresses, order frequency.
- Your order history — every ticket, with totals, dates, dishes, and notes.
- Your delivery configurations — zones, fees, minimum orders, prep times.
- Your marketing campaigns — coupon codes, promo schedules, audience segments.
If you've been running GloriaFood for three years and you have 12,000 customer emails sitting in there, that list is your business. Not Oracle's. You need to export it before April 30, 2027 — and there is a real, low, but non-zero chance the export tools get rate-limited or pulled in the last 30 days as the wind-down accelerates. Don't wait.
If you're migrating off GloriaFood, you can set up a Fleksa restaurant for free — branded domain, real ordering, your own customer list. No commissions on pickup or delivery.
Why this hurts independents and agencies the most
The owners on the SambaPOS forums and Capterra reviews put it plainly. GloriaFood was the free, good-enough ordering layer for restaurants that couldn't justify Toast or ChowNow. It worked. Then it stopped getting features. And now it's gone.
"Features requested for almost five years that never shipped."
"Free model only applies to pickup — delivery requires $30/month."
"Limited to one tablet only — no front-of-house + kitchen split."
The pattern matters because it tells you what to look for next: a tool with an active roadmap, a real free tier you can stay on, and a multi-device setup that doesn't break the moment two people are taking orders.
Agencies have it worse. If you built five WordPress sites for clients and dropped the GloriaFood embed into each one, you have five clients calling you in January 2027 asking what happens to their ordering. Restolabs, OlaClick, Foodhub, Hyperzod and a few others are already pitching white-label replacements. The serious ones to evaluate are in our GloriaFood alternatives comparison — start there before you commit anyone to a 12-month contract.
Sunsets you've seen before — and what to learn from them
If this feels familiar, it should. Google Reader. Google+. Inbox by Gmail. Microsoft's Wunderlist. Each one was a free, beloved tool with no commercial pressure on its parent company to keep it alive. Each one wound down on a published date. Each one left users scrambling in the last 30 days because they assumed the export tools would keep working until the very end.
The lesson is boring and correct: migrate when the announcement lands, not when the cutoff approaches. Tools degrade as teams get reassigned. Exports get rate-limited. Support tickets stop getting answered. The earliest movers got their data out cleanly and never thought about it again.
The 6-week migration window that actually works
You have roughly 11 months from the time this lands in inboxes. You do not need 11 months — you need six weekends. Here's the shape:
Weekend 1 — Export. Pull your menu (every item, modifier, photo), your customer list, your order history (last 24 months is enough for most), and your delivery zone config. Save them locally. Don't trust the cloud copy.
Weekend 2 — Pick the replacement. Spend a Saturday with two coffees and shortlist three options. Use our 7 best GloriaFood alternatives comparison — it has commission %, branded domain support, POS integrations, and real-tier breakdowns. Pick on fit, not features.
Weekend 3 — Set up the new ordering stack. Most modern systems (Fleksa included) can rebuild a menu in 30 minutes if you have the export from week 1. Connect your domain. Connect Stripe. Test on your phone.
Weekend 4 — Run both in parallel. Keep GloriaFood live for one more month. Switch the order CTA on your homepage to the new system. Watch what breaks.
Weekend 5 — Migrate customers. Send one email: "We're updating our ordering. Same restaurant, same menu, new link." Don't apologize. Don't explain Oracle. Customers don't care.
Weekend 6 — Turn GloriaFood off. Pull the widget. Update Facebook. Update Google Business Profile. Done.
Six weekends. The owners who do this in summer 2026 will never think about Oracle's deadline again. The owners who wait until March 2027 will be the ones in the Reddit threads asking if anyone has a CSV exporter that still works.
While you're at it, run a free SEO scan — most GloriaFood-stack sites have major on-page gaps that Oracle never cared about. The audit takes 10 seconds and tells you what to fix on the new site before you even launch it.
What to look for in a replacement
A few non-negotiables, learned the hard way by the early movers:
- Your own branded domain. Not a
yourshop.platform.comsubdomain. If the next vendor sunsets, you keep the URL and just swap the back end. - Multi-device ordering. The #1 GloriaFood complaint was the one-tablet limit. Make sure front-of-house and kitchen can both see incoming orders.
- Real free tier or transparent commission. GloriaFood's "free for pickup, $30/month for delivery" model is what got people stuck. Either truly free, or a flat predictable fee.
- Owns the customer list. You should be able to export your customers in a CSV any day of the week, not just during a sunset.
- POS integration with the ones that matter in your country (Toast, Square, SambaPOS, Lieferando in DACH, Wolt in Northern Europe).
Whatever you choose, run the export-test on day one. If you can't get your data out in week one, you'll never get it out in year three.
A note on Lieferando and Wolt (for EU readers)
If you're in Germany, Austria, the Netherlands, or anywhere Lieferando dominates, GloriaFood was rarely your primary ordering layer — it was the cheap direct-order widget on your own site, running alongside the marketplaces. The shutdown still matters: direct orders are commission-free and the marketplaces aren't. Replace the widget, keep the marketplaces. The Fleksa setup runs natively alongside Lieferando and Wolt for exactly this reason.
Ready to move?
Start free on Fleksa — we'll help you import your menu from GloriaFood before it goes dark on April 30, 2027. Branded domain, commission-free pickup and delivery, multi-device kitchen view, your customer list in your account from day one.
FAQ
When exactly is GloriaFood shutting down?
April 30, 2027. The in-app banner reads "This offering will be retired on April 30, 2027." New signups are already closed as of early 2026. Existing accounts continue to work until cutoff, after which the website ordering widget, Facebook ordering, FoodBooking reservation app, payment processing, and POS integrations all stop.
Will I be able to recover my menu and customer data after April 30, 2027?
No. Oracle has confirmed there is no data retention beyond April 30, 2027. Menus, customer records, order history, delivery configurations, and marketing campaigns all become permanently inaccessible. Export your data well before the deadline — ideally within the next few months, while the export tools are still running smoothly.
Is Oracle launching a GloriaFood replacement?
No. Oracle has not named a successor product. The shutdown is a wind-down, not a migration to a new platform. You need to pick a third-party replacement and migrate independently.
What's the easiest GloriaFood alternative for an independent restaurant?
It depends on whether you need just a website ordering widget or a full branded ordering setup with your own domain. We've ranked the seven serious options in our GloriaFood alternatives comparison, with commission rates, branded domain support, and free-tier details for each.
Should I migrate now or wait until late 2026?
Migrate now. Tools degrade as the cutoff approaches — support response times slow, exports get rate-limited, and engineering teams get reassigned. The owners who migrated in the first six months of the announcement got clean exports and never thought about it again. The ones who waited are now stuck inside the last-30-days rush.
