How-to guideGet a task done

Check menu copy with the Menu Copy Checker Agent

Agent Console is in private preview: it’s available to selected customers, and its agents and features may change before it’s generally available.

This page explains how to check menu artwork against your pricing data with the Menu Copy Checker Agent. The agent compares the product names, descriptions, prices, and calorie information in a pricing spreadsheet with what appears on each menu, and lists every mismatch for you to review.

Prerequisites

Before you begin, ensure you have:

  • The Member or Manager role for the Agent Console module. Each role’s permissions are listed in Agent Console permissions.

  • The Menu Copy Checker Agent on your Agent Console dashboard.

  • The pricing spreadsheet in Agent Storage, as an XLSX file. A Manager adds it, as described in Add a pricing spreadsheet.

  • The menus to check, as PDF or MP4 files, each smaller than 200MB.

Add a pricing spreadsheet

The agent checks menus against pricing spreadsheets kept in Agent Storage. You need the Manager role to add or change them.

  1. Open Agent Console from the application switcher at the top left, or navigate to https://app.storyteq.com/agent-console/<client-handle>;.

    <client-handle> is your organisation’s handle: the same name that follows /portals/ in your Content Portal address.

  2. Select Agent Storage, then select the Menu Copy Checker Agent.

  3. Select Upload file, then choose the XLSX spreadsheet.

    The agent ignores hidden tabs in the spreadsheet.

When prices change, upload the new version of the spreadsheet in the same way. Archive or delete versions that are no longer needed: archived files don’t appear when someone runs the agent, so nobody can check a menu against out-of-date prices.

Check a menu

  1. Open Agent Console from the application switcher at the top left, or navigate to https://app.storyteq.com/agent-console/<client-handle>;.

  2. Select the Menu Copy Checker Agent tile.

  3. Upload the menus you want to check.

  4. Select the pricing spreadsheet to check them against.

  5. If this is the first time anyone has used this spreadsheet in a run, map its data in the Column Mapping section:

    1. Select the tabs of the spreadsheet to import.

      Import only the tabs that hold the pricing data you need.

    2. For each tab, check the columns the agent has matched to each piece of product data, using the preview.

    3. To change a match, select a different column.

      Each tab has its own mapping, so tabs laid out differently can still be imported.

  6. Wait while the agent checks the spreadsheet data against the menus.

Review the results

When the check finishes, the agent sorts its findings into three sections. Each finding shows the value from the spreadsheet next to what appears on the menu, so you can compare them.

  • Failed: every price that differs between the spreadsheet and the menu, and every major difference in a product name.

  • Warning: minor differences in a product name.

  • Reviewed: the items the agent checked.

    1. Review each item in Failed and Warning.

    2. If an item isn’t a real problem, pass it.

    3. To keep a record of the check, download the spreadsheet of errors and checks.

    4. Correct the menu artwork for any items that remain.

What the agent can check

The agent checks product names, prices, sizes, price bands, and calories. Each check has limits that affect how many findings you get, so a finding isn’t always an error in the artwork.

Check What to expect

Product name

Names must match exactly, including spelling, grammar, and case, to pass. Pricing data often names products differently from the artwork, so expect name findings that aren’t real problems.

Product price

The size on the menu must match the size in the spreadsheet: for example, an espresso listed as single on the menu and small in the spreadsheet won’t match. The agent compares the value stored in the spreadsheet, not the formatted value: a price stored as 2.4999 and shown as £2.50 doesn’t match a menu price of £2.50. It checks individual prices only, not bundle prices, such as 2 for £5, or category prices, such as one price for all beers.

Product size

Works best when prices are in a table with the sizes in the column headers. The agent expects sizes in the same order as the data, and doesn’t work well when a menu shows sizes as icons.

Price band

The agent can map several price bands to the artwork, such as a different band for each product category.

Calories

If the pricing spreadsheet includes calories, the agent checks them against the artwork. If it doesn’t, the agent reads the calories from the artwork and shows them, without checking them.