Is GloriaFood shutting down? What's confirmed, and what isn't

Short answer: yes, and it is not a rumour. GloriaFood’s own website says so.

What is harder to establish is when, and that turns out to be the interesting part.

What GloriaFood confirms itself

On gloriafood.com, the vendor now states, verbatim:

GloriaFood will reach end of life on April 30, 2027. We remain committed to supporting existing customers through this date.

Checked September 9, 2026.

Two things follow immediately. The date is official, from the vendor’s own homepage rather than from anyone selling you a migration. And existing accounts are still being supported, so nothing you have breaks today.

This page used to say the opposite, and that is worth explaining

Until early September 2026, this guide argued at length that the April 2027 date was not published anywhere public — that it came only from the retirement notice inside the admin panel and from partner emails, and that every public page carrying it was a competitor selling migrations. That was accurate when we wrote it, and we checked it more than once.

It is not accurate now. GloriaFood changed its homepage: the old discontinuation sentence has been removed and the date is up.

Worth noting what did not change with it. Removing that sentence did not reopen signups — there is no signup control anywhere on the homepage, and gloriafood.com/signup returns 404. The page simply stopped saying so, while a stale “How to get started” section still tells you to create an account you cannot create.

We are leaving this note here rather than quietly editing the page, for one reason: it is the same discipline we are asking you to apply to everyone else’s claims, including ours. A page about a moving situation is only as good as its last check, and you should trust a source that tells you when it was wrong over one that never mentions it.

Check it yourself. Everything below is on gloriafood.com and takes about thirty seconds.

Oracle has named a company — and carefully not recommended it

The same Service Update continues:

While Oracle does not offer a direct replacement for GloriaFood products and services, we would like to make you aware of FoodAmigos, a restaurant technology provider that offers online ordering and related solutions.

That link goes to a FoodAmigos landing page built for GloriaFood customers, and you will shortly see a great many articles upgrading that sentence into an endorsement.

Read the sentence again. Oracle says it does not offer a direct replacement, and that it wants to make you aware of a provider. There is no statement that Oracle evaluated FoodAmigos, compared them to anyone, or stands behind the outcome. It is a signpost at a fork in the road, not a review of what is down that road.

This is not a criticism of FoodAmigos, who may well suit you. It is a caution about what the referral proves, which is less than it looks. If you take the signpost as a vetting, you will stop comparing at the exact moment comparing matters most — when you are moving a business you built onto a platform you will be on for years.

What to ask them, and us

Three questions worth putting to any platform courting GloriaFood’s leavers, ourselves included:

1. What will I actually pay per order? FoodAmigos does not publish prices — you book a demo — and commission per order is one of the models they offer. Ours are on our pricing page and we do not take a cut of your orders.
2. What exactly migrates? Several migration pages, theirs included, imply customer data comes across. GloriaFood’s only documented export is the menu, via the Fetch Menu API. Ask precisely how customer records, photos and settings arrive, and what you rebuild by hand. Our own answer is line by line, including the parts that do not transfer.
3. What happens if I want to leave you? The whole reason you are reading this is that a platform you relied on is closing. Ask what you can export on the way out, before you need it.

What that means for your timeline

Take the date as real — it comes from inside the product, and it has been consistent across every partner report. But plan against the crowd, not the deadline.

The failure mode is not GloriaFood switching off early. It is everyone moving at once. If a large share of a six-figure restaurant base migrates in the final quarter, every ordering platform’s onboarding queue, support desk and migration team is saturated at exactly the moment yours is urgent. Your own move gets slower precisely when you have least room.

Moving early costs nothing. Your GloriaFood page keeps working right up to the cutoff whether or not you have set something else up, so there is no window where you are between systems.

What happens to your data

Not all of your GloriaFood setup can be exported, even today while the platform is healthy — and there is no single “download everything” button. It is piecemeal, and the parts that hurt most to rebuild are the ones that do not come out at all.

No data retention past the retirement date has been reported consistently, and GloriaFood publishes no retention commitment. Treat anything you have not pulled out yourself as gone when the service goes dark.

Your menu structure — this part exports cleanly

GloriaFood publishes a Fetch Menu API that returns your whole menu in one call: categories, items, descriptions, prices, sizes, and modifier groups with their min-max rules.

You generate a key per location in the Restaurant Admin Panel — the “…” (Others) menu → 3rd party integrations → Enabled integrations → the “Fetch Menu” template. Running a chain? Nine branches means nine keys.

This is the hard part of any migration, and it is the part that does come out cleanly.

Your dish photos — the real gap

Photos are not in the menu payload, and there is no bulk download. The Menu Editor is the only place to save them, one at a time. Budget a couple of hours if you have 80-plus items.

Two things worth knowing. Restaurants that relaunch with placeholder images feel it in orders during the first week. And a fair chunk of GloriaFood’s item images are their own stock photos anyway — which makes this a good moment to shoot your real dishes.

Your customers and orders — CSV from the admin

Exportable yourself, under Marketing → Customers → Export. Pull these while the platform is still up; you will want them for reactivation and for your own records.

Your settings — screenshot and rebuild

Your delivery zones, opening hours, prep times, fees, taxes, payment configuration and promotions export nowhere, and no import tool can invent them. That is setting-by-setting reconstruction: not hard, but fiddly and easy to get wrong under deadline pressure, which is exactly what spring 2027 will be.

Screenshot every settings page now, while you can still read them side by side with the new setup.

That is the real deadline. Not “the site goes dark on a date”, but “the settings you have tuned over years exist only inside a product that is winding down”.

The full line-by-line list of what transfers and what doesn’t →

What to do about it, in order

1. Read the Service Update on gloriafood.com yourself, so the date and the FoodAmigos referral come to you from the vendor rather than from anyone selling you a migration.
2. Export what GloriaFood lets you, now, while it is up: your Fetch Menu key, your customer and order CSVs, and your dish photos out of the Menu Editor.
3. Screenshot every settings page — delivery zones, hours, fees, taxes. These are the ones nothing can import for you.
4. Move when it suits you, not when the queue forms.

If it helps, we wrote the export instructions so they work whether or not you come to us, and an honest comparison of what to look for in a replacement.

→ Or see how migration to Ontabee works. Most single-location restaurants are live again the same day.