By Supaorder Team — who we are
GloriaFood Shuts Down 31 March 2027
What Oracle has actually published about the GloriaFood shutdown — the date, the two dates in circulation, and what stops working when the service ends.
If you run ordering on GloriaFood, you have probably seen two different shutdown dates and no clear statement of which one is real. This post is the short version: what has actually been published, by whom, and what it means for a restaurant that has to plan around it. No speculation, and every claim linked to its source.
The date
31 March 2027. Oracle, which owns GloriaFood, states it on its own food and beverage page:
GloriaFood products and services are being discontinued, with full end of service scheduled for March 31, 2027. While we are no longer accepted signups, we are fully committed to supporting our existing customers throughout this transition.
That is quoted verbatim from oracle.com/food-beverage, checked on 2 September 2026.
Why you have also seen 30 April 2027
Because it circulated first. An earlier in-product notice carried that date, it was reproduced on third-party forums and blogs, and from there it spread across a lot of pages that never went back to check.
Oracle’s current, first-party statement supersedes it on both counts: it is published by the company that owns the product, and it is the more recent of the two. If you are planning around a date, plan around 31 March 2027 — and if you see 30 April quoted somewhere, that is the older notice being repeated rather than a second, later deadline you can rely on.
Worth being precise about what “supersede” means here: the earlier date was not wrong when it was published, and nobody was inventing it. It has simply been overtaken.
What GloriaFood’s own site says
Its home page carries a single line:
GloriaFood has been discontinued and is no longer accepting new signups.
Checked on 2 September 2026 — and note what is missing. No date appears anywhere on that page. That absence is a large part of why two dates have been circulating for months: the product’s own site confirms the discontinuation without timing it, so people went looking elsewhere and found whichever page they found first.
Two things that have not been announced
There is no export-and-migration tool. Oracle has not announced an export-and-move path. Menus, customer lists and ordering links have to be rebuilt on whichever platform you choose. That is the single most consequential fact on this page, because it converts “switch platforms” from a data-transfer task into a rebuild — and a rebuild is a thing you schedule, not a thing you do in the last fortnight.
No replacement has been named for GloriaFood customers to move to. Oracle’s statement commits to supporting existing customers throughout the transition, which is a real commitment and worth reading as one — but “supported through” is not “moved to”, and no destination has been published. Choosing where you go is your decision, on your timetable.
What actually stops working on the day
- Your ordering page and widgets. The embedded order button on your website, and the hosted ordering page behind it.
- Every link and QR code pointing at them. Bookmarks, the link in your social bios, the QR codes on tables and takeaway bags, the URL in the footer of every printed menu you have ever handed out.
- The order apps your customers may have installed.
The last of those is the one that catches people out, because it is the part with a human habit attached. A regular who has been reordering from the same bookmark for two years does not get an error message that tells them where you went. They get a page that does not work, and then they order from someone else. That is the actual risk in this shutdown — not data loss, but a silently broken path between you and people who already wanted to order from you.
A calendar, working backwards
There is no urgency today, and pretending otherwise would be dishonest — the service is running and Oracle says it is supporting customers through the transition. But the useful deadline is not the shutdown date. It is the date by which your regulars need to have learned a new link, and that is much earlier.
| When | What |
|---|---|
| Now → end 2026 | Choose a platform and rebuild the menu. No pressure, no dark days, and time to get modifiers and delivery zones right. |
| Around 6 months out (Q4 2026 – Q1 2027) | Run both in parallel. New links live, old links still working, nothing depending on the switch. |
| Around 3 months out (early 2027) | Move the QR codes, the social bios, the website button, the printed menus. |
| Final weeks | Point the last stragglers across. Nothing should be load-bearing on GloriaFood by now. |
| 31 March 2027 | The old links stop. Nobody notices. |
The whole point of starting early is that the deadline becomes uneventful. Restaurants that leave it until March will be doing a menu rebuild, a customer re-education campaign and a payment reconfiguration in the same month, in the run-up to a hard cutoff, with no fallback.
What to do next
Pick a replacement on its merits rather than on the deadline — you are choosing the system you will run for years, and the shutdown is just what set the timer. Things worth checking: whether your menu can be rebuilt for you or you are doing it yourself, whether the new channel gets branded iOS and Android apps in the stores that your regulars can install (GloriaFood does not include those, which is why the ordering habit lives in a bookmark), and whether your POS connects to it.
We keep a page with the migration path laid out step by step, both source links, and what it costs to move before the deadline: moving off GloriaFood. Menu setup and migration are done for you and included — send a link to your current menu and the rebuild is our job, not yours.
The practical sequence for the move itself — what to do in which order, and what breaks if you do it backwards — is the companion to this post.