How to export your GloriaFood menu, customers and order history

GloriaFood reaches end of life on 30 April 2027. Oracle says data can be retrieved for 30 days after a service expires or is cancelled, and that’s it (Oracle EOL FAQ). Everything you have built up in GloriaFood should be safely in your own hands long before then: the menu you have tweaked for years, the regulars’ details, the order history that shows what sells on a Friday. For the wider deadline, read GloriaFood is shutting down.

This guide covers three exports:

1. The menu, using GloriaFood’s official Fetch Menu integration
2. Clients and orders, using Reports, then List View
3. How to use that customer data lawfully in the UK

Then it covers how to check the export, and how to move the menu without retyping it.

1. Export the menu with Fetch Menu

GloriaFood publishes a Fetch Menu API for exactly this. It returns your menu as structured data instead of screenshots (GloriaFood integration docs).

What you get

The documentation says the export contains:

• Categories, each with its items and any option groups attached to the whole category
• Items: name, description, price, sizes, option groups, and tags such as VEGETARIAN, VEGAN, GLUTEN_FREE, HALAL, NUT_FREE, DAIRY_FREE, HOT and RAW
• Sizes: name, price, whether it is the default size, and size-specific option groups
• Option groups (your extras): name, whether a choice is required, minimum and maximum selections, and whether quantities above one are allowed
• Options: name, price and whether it is the default
• Extras data: allergen names, nutritional values, which order types an item is available for, and kitchen internal names used on tickets

That is far more than screenshots capture. The option-group rules matter most. “Choose 1 to 3 toppings” and “Choose exactly one sauce” are the details that cause wrong orders when a menu is retyped by hand.

Step by step

1. Log in to your GloriaFood Restaurant Admin Panel.
2. Open Others. Look for the … icon.
3. Go to 3rd party integrations, then Enabled integrations.
4. Add an integration and choose the template Fetch Menu.
5. Generate the key. It is a short string. The key is unique to each restaurant location, so if you have two shops you need two keys.
6. Request the menu. On a Mac, Linux, or Windows 10/11 machine with curl, open a terminal and run the following, replacing YOUR_KEY:

curl "https://pos.globalfoodsoft.com/pos/menu" \
  -H "Authorization: YOUR_KEY" \
  -H "Accept: application/json" \
  -H "Glf-Api-Version: 2" \
  -o gloriafood-menu.json

To get XML instead, use Accept: application/xml. JSON is the default.

7. Check the file opened. gloriafood-menu.json should start with { and contain "categories". If you see an error, the key is usually wrong, or it was created with a different template.

If you are not comfortable running a command, give the key to whoever is rebuilding your menu. When you switch to Chefzi, we do this step for you. Treat the key like a password. Share it only with that provider, and remove the integration once the move is finished.

Turn it into a spreadsheet

A JSON file is hard to read. This short Python script flattens it into menu.csv, with one row per item and size, so you can check prices in Excel or Google Sheets. It uses only the fields GloriaFood documents. Download menu_to_csv.py.

import csv, json, sys

menu = json.load(open(sys.argv[1], encoding="utf-8"))
rows = []

def groups_text(groups):
    out = []
    for g in groups or []:
        opts = ", ".join(
            f"{o.get('name')} (+{o.get('price', 0):.2f})" for o in g.get("options") or []
        )
        rule = f"min {g.get('force_min', 0)} / max {g.get('force_max', 0)}"
        out.append(f"{g.get('name')} [{rule}]: {opts}")
    return " | ".join(out)

for cat in menu.get("categories", []):
    for item in cat.get("items", []):
        extras = item.get("extras") or {}
        allergens = ", ".join(
            a.get("name", "") for a in extras.get("menu_item_allergens_values") or []
        )
        sizes = item.get("sizes") or [{"name": "", "price": None, "groups": []}]
        for size in sizes:
            rows.append({
                "category": cat.get("name"),
                "item": item.get("name"),
                "description": item.get("description") or "",
                "size": size.get("name") or "",
                "base_price": item.get("price"),
                "size_price": size.get("price"),
                "tags": ", ".join(item.get("tags") or []),
                "allergens": allergens,
                "option_groups": " | ".join(filter(None, [
                    groups_text(cat.get("groups")),
                    groups_text(item.get("groups")),
                    groups_text(size.get("groups")),
                ])),
            })

with open("menu.csv", "w", newline="", encoding="utf-8") as f:
    w = csv.DictWriter(f, fieldnames=list(rows[0].keys()) if rows else ["category"])
    w.writeheader()
    w.writerows(rows)
print(f"Wrote {len(rows)} rows to menu.csv")

Run it with python3 menu_to_csv.py gloriafood-menu.json. The same conversion is on the GloriaFood menu converter. It runs in your browser and does not upload the file.

One caution, from testing the script against GloriaFood’s own sample file: in that sample, size prices look like additions to the item’s base price. For example, a pizza with base price 7 has Small at 0 and Large at 2. That’s why the script keeps base_price and size_price as separate columns. Check a few rows against what customers actually pay on your live ordering page before trusting the totals.

Check the menu export

Before you move anything, check these against your live menu:

• Every category is there, including ones that are hidden or only shown at certain times
• Items with sizes have every size
• Every option group has the right minimum and maximum
• Paid extras have the right price, size by size where it differs
• Allergen values are present where you set them. Your allergen information is your responsibility, so correct it now rather than copying an error across.
• Items only available for collection or delivery are marked that way

2. Export your clients and orders

GloriaFood’s reporting module includes Lists for exporting client contact details and order details (GloriaFood). Later updates added an orders list under Reports, List View, Orders, and promotion stats that can be exported as CSV or XLS (GloriaFood).

1. In the admin panel, open Reports.
2. Choose List View.
3. Select Clients and export.
4. Select Orders, set the widest date range available, and export. If a very long range fails, export year by year.
5. Export any promotion stats you want to keep.
6. Name the files clearly, for example yourshop-clients-2026-11-02.csv, using your shop name and the date, and store them in one access-controlled folder.

What the order history is good for

Order history is not just a record. Before you switch, use it to answer a few practical questions:

• Which items actually sell? Put those at the top of each category on the new menu.
• Which delivery areas order most? Check that the new zones and fees cover them properly.
• When are your peaks? Don’t plan the switch for a peak night. Switch on a quiet weekday.
• How many customers order more than once? That tells you how much a message to regulars is worth.

3. Use customer data lawfully

Your client list contains personal data: names, phone numbers, email addresses and delivery addresses. You collected it as the restaurant, so the rules apply to you.

• Keep it secure. Use one folder, limit who has access, and don’t email the file around.
• Use it for marketing only if the rules allow. Under PECR, the ICO’s soft opt-in can let you email or text your own previous customers about similar products and services. This only applies if they were given a simple chance to opt out when you collected their details, and again in every message. It does not cover prospective customers or bought-in lists (ICO).
• Respect earlier opt-outs. Anyone who unsubscribed in GloriaFood stays unsubscribed.
• Only import what you need into the new system. If you have no reason to keep an old record, delete it.
• Update your privacy notice to name your new ordering provider.

If you’re unsure, read the ICO guidance in full or get advice. A short, honest message such as “We have moved online ordering. Same menu, same prices, new link.” is usually all you need to send.

4. Move the menu without retyping it

Once you have the export, a new provider can rebuild your menu from it. With Chefzi, the menu move is included in the product, with no setup fee. Send us your Fetch Menu file, or screenshots if that is all you have, and we rebuild the categories, items, sizes and extras. You then check it. We don’t invent dishes or copy a marketplace menu that isn’t yours, and photos come across only if they are yours.

After the rebuild, run four test orders on a phone before you change any public links:

1. An item with paid extras. The ticket must show every extra.
2. An address inside a delivery zone. The fee and minimum must match.
3. An address just outside a zone. Checkout must refuse it.
4. A sold-out item. It must not be possible to pay for it.

The full switch, including links, QR codes and switching GloriaFood off, is in the GloriaFood migration checklist. The product comparison is on the GloriaFood alternative page and in Chefzi vs GloriaFood.

Do it this month, not in April

Exports take minutes. Discovering in April that a key no longer works, or that your paid period ended earlier than you thought, takes much longer to fix. Export now, keep the files safe, and repeat the export just before you switch so that you have the latest menu.

Chefzi is £0 for the first three months, then £19 a month for cash or no-card payments, or £29 a month with online card payments through Stripe per location excluding VAT, with 0% commission. Book a free switch and we’ll take it from your export.

Questions

Sources

Accessed 19 October 2026.

• GloriaFood, Fetching the restaurant’s menu API (Version 2): key creation path, endpoint, headers and field definitions.
• GloriaFood sample menu payload, used to test the script and observe the size-price behaviour.
• GloriaFood reporting module (client and order lists).
• GloriaFood November 2023 updates (Reports, List View, Orders; promotion stats CSV/XLS).
• Oracle, Oracle GloriaFood EOL FAQ, v1.0, March 2026 (end-of-life date; 30-day data retrieval).
• ICO, electronic mail marketing (soft opt-in).

Related guides

• GloriaFood shutdown guide
• Reduce delivery app commission
• Delivery fees and minimum orders
• Tablet for restaurant orders
• GloriaFood alternatives
• Delivery app commission
• What a restaurant website needs
• Christmas opening hours
• Order link on Google
• GloriaFood alternative
• Migrate before 30 April 2027
• Tools
• Commission calculator
• GloriaFood menu converter
• Pricing