← BuckThem

MenuTruthRestaurant pilot forming

The cross-channel menu-drift watcher for restaurants.

For restaurant owners and operators whose menus appear across multiple channels: MenuTruth keeps one approved master menu per location and compares it against listing snapshots you supply — the current listing for each channel, entered or pasted by you and labeled by date and source — for DoorDash, Uber Eats, Grubhub, Google, and your own site. Every difference the check finds opens a fix ticket in MenuTruth for you to act on. No platform is scraped or connected by MenuTruth, and MenuTruth corrects nothing on any platform.

How it works

  1. Approve your master menu, once per location — items, prices, descriptions, and modifiers, kept versioned as you revise it
  2. For each channel — DoorDash, Uber Eats, Grubhub, Google, and your own site — supply the current listing as it appears, entered or pasted by you as a snapshot labeled by date and source; MenuTruth scrapes no platform and connects to none
  3. Run the check — the snapshot is compared item by item against the master menu: a price that differs, an item missing, an unauthorized item, a description that differs, a modifier price that differs, or availability that differs
  4. Every difference opens a drift ticket in MenuTruth — its severity, the channel, and the master value against the channel value — and tickets flow Open, then Fixed, then Verified when a later check shows no drift
  5. Work your tickets — you make each correction yourself on the channel where the drift appeared; MenuTruth corrects nothing on any platform and contacts no platform; a location and channel reads Clean only when its latest check found zero drift, and check history is kept per channel with drift counts and aging in view

One approved master menu — per location

The master menu is the one menu you approve for a location: its items, prices, descriptions, and modifiers. It is kept versioned as you revise it, so a check always runs against the menu you approved.

Every location carries its own master menu, because locations do not all list the same menu. A check for a location runs against that location's master, and against nothing else.

Snapshots — supplied by you, labeled by date and source

A check does not run against a platform. It runs against a listing snapshot: the current listing for a channel, as it appears, that you enter or paste into MenuTruth. Every snapshot is labeled by the date it was taken and the source it came from, so a result can always be traced back to the listing you supplied.

The channels a snapshot can come from are the channels your listings appear on: DoorDash, Uber Eats, Grubhub, Google, and your own site. Naming a channel here names the source of a snapshot you supply — nothing more. MenuTruth has no connection to any of them.

No one collects snapshots for you today. A managed snapshot service — someone gathering your listings for you — is one of the later, gated steps toward the full product; it is not a service MenuTruth offers today, and no snapshot arrives on its own.

No platform is scraped or connected — the settled rule

This is settled, and it is stated plainly: MenuTruth scrapes no platform, and it is connected to no platform. DoorDash, Uber Eats, Grubhub, Google, and your own site are never reached by MenuTruth — not to read a listing, and not to change one.

Every check runs on the snapshots you supply, labeled by date and source, compared against your approved master menu. If you have not supplied a snapshot for a channel, there is nothing for that channel to check.

The check — item by item against the master

When you run a check, the snapshot is compared item by item against the master menu for that location. The check looks for exactly these differences:

Each difference the check finds opens one drift ticket, carrying its severity, the channel it was found on, and the two values side by side — the master value and the channel value from your snapshot.

Fix tickets — opened here, acted on by you

A fix ticket sits in MenuTruth, and it is yours to act on: you make the correction yourself, on the channel where the drift appeared. MenuTruth corrects nothing on any platform, and it never contacts a platform about a listing.

A location and channel reads Clean only when its latest check found zero drift. Check history is kept per channel, and drift counts and how long tickets have been open stay in view, so an old drift is not lost behind newer ones.

Where it stands — the honest state

MenuTruth is forming its first restaurant pilot group now. The door below is a restaurant pilot application — applying starts a pilot conversation; it does not create an account, and it is not a sign-up for a running service.

No platform is scraped or connected, and none is claimed to be: checks run on listing snapshots you supply, each labeled by date and source. Platform and listing data connections, and a managed snapshot service, are later, gated steps toward the full product — they are not part of today's product, and no one is collecting snapshots for you today.

There is no nightly automatic watching today. Checks run when you supply a snapshot and run the comparison; the nightly scheduler has not been built, and nothing watches your listings on its own, overnight or otherwise.

Fix tickets are opened in MenuTruth for you to act on. MenuTruth corrects nothing on any platform and never contacts a platform.

No price has been set for this door. Prices exist in our market research as hypotheses; they have not been validated and they have not been decided, so no price is shown here and there is nothing to buy on this page.

Restaurant pilot application

This is a restaurant pilot application — an application to join MenuTruth's first restaurant pilot group, not an account sign-up and not a purchase. Tell us who to reach, your restaurant or group, and how many locations you have. If you like, tell us which ordering channels you list on, in your own words, and how you keep your menus consistent today. We will be in touch about the pilot group.

Application saved — thank you. Your restaurant is in the pilot application queue, and we will be in touch about the pilot group. No account was created.