100%
Integrations › Email order import

How items are matched to your menu

Name matching, what happens to items and modifiers that do not match, and how to teach the matcher a name.

Nothing in a platform email identifies your menu items. All the email carries is the wording the customer saw, so matching is done on the printed name.

What happens to each line

  • A clear match becomes a normal ticket line, priced from the email.
  • No match, or two candidates too close to separate, becomes a misc line. The line keeps the customer wording as its name, so the kitchen still reads what the customer ordered.
  • Modifiers that do not match become notes on their line rather than misc lines of their own.
Image needed · mpemail-matching-02
Capture: A POS ticket detail showing one matched line and one misc line, where the misc line still carries the wording the customer saw on the platform.

Teaching it a name

The Menu mapping tab collects every name that failed to match, with the platform it came from and how often it has appeared. Pick the menu item it should have been and that name is matched from then on.

Work this list in order of how often a name has appeared. A name seen thirty times is worth mapping; one seen once was probably a discontinued special.

Image needed · mpemail-matching-01
Capture: The Menu mapping tab listing several unmatched names with their platform and how many times each has been seen, and one row with its menu item picker open.
Renaming a menu item to match the platform wording is usually faster than mapping the same name in three places, and it fixes the customer-facing wording at the same time.

Why an import is never rejected

An unmatched item could have failed the whole order instead. It does not, because there is no way to tell the customer why. The order was accepted on the platform tablet and the kitchen is waiting for it — a rejected import would simply vanish. A misc line is wrong in a way somebody can see at approval.