Glossary

What is a restaurant CDP?

A definition, and an honest note on when the answer is that you do not need one.

CDP stands for customer data platform. In a restaurant context it means software that reads the systems you already run — reservations, point of sale, reviews, email — and resolves what it finds into one record per actual human being.

That is the whole idea. The complexity is entirely in the word "resolves."

What it does

Three jobs, in order. Most of the value is in the first one, and most of the marketing is about the third.

  • Ingest. Pull guest records out of each system, on a schedule or on demand.
  • Resolve. Work out that the Sofia Martinez who booked on OpenTable, the phone number on a POS check, and the reviewer called S. Martinez are one person — or decide they are not, which matters just as much.
  • Activate. Let you build audiences from the unified record and act on them, usually by sending something.

What it is not

A CDP does not take bookings, does not run your floor, and does not process payments. It sits above the systems that do those things.

It is also not a loyalty program. A loyalty platform knows the guests who enrolled; a CDP works from every guest who has ever booked or dined, whether or not they signed up for anything. Those are different populations, and in full-service dining the gap between them is usually large.

When you probably do not need one

One location, a few hundred guests, one reservation platform and one POS: your reservation platform's own reporting is likely sufficient, and buying a CDP would be solving a problem you do not have yet.

The threshold is usually not guest count. It is systems count. The pain starts when the same guest exists in two places that cannot see each other — which is almost always the moment you open a second concept or acquire a site running different software.

What to ask before buying one

The category has a lot of similar-sounding marketing. These four questions separate the products quickly.

  • What happens when two guests share a name? Any product that merges them automatically will eventually destroy a guest history irrecoverably.
  • Which of my systems can it actually read today — not on the roadmap?
  • Can I see why a guest ended up in a given audience? If the answer is a number with no reasoning, you cannot check its work.
  • Who operates this in month six? The most common failure in this category is not a bad product. It is a good product nobody has time to open.

Related reading