GloriaFood Is Discontinued. Here Is What to Do Next.

GloriaFood says it plainly

The notice on gloriafood.com reads, in full: “GloriaFood has been discontinued and is no longer accepting new signups. We are fully committed to supporting our existing customers throughout this transition.” That is the whole first-party statement. Signups are closed, existing accounts still work for now.

There is no replacement product

Oracle acquired GloriaFood and has not announced a successor for it. This is a wind-down, not a migration to another Oracle product, so nobody is going to move your menu for you.

• -Most competitor pages say April 30, 2027. At least one attributes March 31, 2027 to Oracle instead. They cannot both be right.
• -Neither date appears on gloriafood.com's notice, which gives no date at all.
• -Oracle's own GloriaFood support page carries no retirement notice and no date either; it only says the same support channels continue.
• -Several sources describe an in-app banner naming a date. We cannot see inside your account, so if there is a banner in yours, that is better evidence than any article — including this one.

• -Your customer list — names, phones, emails. This is the asset that took years to build and the one nobody can rebuild for you.
• -Your menu, in whatever form it exports: items, prices, modifier groups, photos.
• -Order history, for your own records and for anything your accountant needs.
• -Delivery zones, opening hours, and any promotions you would otherwise have to reconstruct from memory.
• -Screenshot anything that will not export. An imperfect record beats none — we have rebuilt a restaurant's gift cards from photographs of a screen before.

Your own ordering site, and nothing to rip out

We build the site and the ordering portal, and ship one Ginger Box and one iPad. The Box plugs into your router and prints every order twice, on the printers you already own: a ticket to the kitchen and a copy at the front counter, at the same moment the customer finishes ordering. Nobody re-keys anything into anything, and the customer pays on the site, so every ticket that prints is already paid for. Your current POS is not touched, not integrated with, and not replaced — which is why it does not matter how old it is.

$1 an order, paid by the diner

No monthly fee and no contract. The platform fee is $1 per order and the customer pays it, not the restaurant. On a $35 order that is under 3%, against the 15–30% a delivery marketplace takes from you for the same sale.

Small tickets get a different number

On a $6 boba order a flat $1 is a sixth of the ticket, and we are not going to pretend otherwise. High-volume, small-ticket shops negotiate it down to $0.25 or $0.50 an order depending on volume — tell us your numbers and we will quote it.

It is a whole POS you are not obliged to use

The Box running your ordering is the same Box that runs the full Ginger POS — floor plan, checks, reporting, the lot. It simply sits dormant until you want it — though the reporting is live from day one, so your online orders come with itemised sales, daily and custom ranges, category and hourly breakdowns, card against cash, discounts and refunds. If you ever want the rest, there is nothing to install and nothing to migrate; you switch it on.

Two systems means two sets of numbers

If you keep your existing POS for the dining room and run Ginger Direct for online, your online sales report in Ginger and your in-store sales report in your old POS. They do not add themselves together. For a lot of restaurants that is fine — online was already a separate line in the books. But you should know it before you start, not after.

Switching everything later is the fix, if you want it

The single-set-of-books version is the full POS, which is already on the Box. That is an option, not a requirement, and not something we will push you into on a timetable that belongs to Oracle rather than to you.