Skip to main content

Import a GloriaFood menu

Use the GloriaFood importer to bring an existing menu into the selected store only after you have confirmed the store, the approved integration owner, and the current provider instructions. The flow uses a Restaurant Key and Master Key; both are sensitive credentials and must never be copied into shared documentation, screenshots, tickets, chat, or an unapproved tool.

Import can change live catalog data

An import sends data to an external provider and can change the selected store’s menu or start a background job. Use only an authorized non-production store and approved credentials. A button response does not confirm provider completion, imported item counts, or the customer-facing menu result.

Before you start​

  • Confirm that the selected store is the intended destination for the menu.
  • Obtain the Restaurant Key and Master Key through the provider’s approved account workflow.
  • Confirm the current GloriaFood API setup instructions with the integration owner; provider navigation, API types, and endpoint requirements can change.
  • Keep the credentials in the approved secret-management process. Do not retain them in a browser note, spreadsheet, sample file, or support message.

Prepare the GloriaFood connection​

The documented provider flow is:

  1. Open the menu for the store that will receive the import.
  2. Open the menu-import action labeled Pull GloriaFood Menu when it is available for that store.
  3. In the GloriaFood account, open the online-ordering integration area and select the API configured for the restaurant.
  4. If the provider requires a new API, choose its menu-fetch API type, use the endpoint supplied by the approved integration flow, and supply the business contact email required by the provider.
  5. Generate the API and keep the Restaurant Key and Master Key in the approved credential store.
  6. Return to the importer and enter the credentials only in the dedicated fields for the intended store.
  7. Start the import through the approved workflow, then inspect the returned status and the resulting catalog before treating the menu as ready.

The recorded walkthrough is available as GloriaFood menu import video. It is a reference for the captured workflow, not proof that current provider controls, authorization, or menu data behave the same way.

Understand the credential boundary​

The current Dashboard source enables the GloriaFood action only when both key fields contain values. It removes the Master Key from the configured import-service request body, but an optional logging path can still submit both values for later prefill. Treat both keys and all prefilled values as secrets regardless of the request path shown by the client.

Do not assume that a successful client state means the provider accepted the credentials, that the import job completed, or that every category, product, modifier, price, image, or availability setting was transferred.

Review the imported menu​

After the approved import finishes, use a controlled review to compare the selected store’s catalog with the source menu:

  • Check categories, products, descriptions, prices, and modifier structures.
  • Check images and customer-facing presentation separately from the import response.
  • Confirm that the intended store, not another store with a similar name, received the data.
  • Record any provider error, missing item, credential problem, or unexpected overwrite through the approved support process without sharing keys or menu data unnecessarily.

Related guides: Importers · Products overview