TagPipes Companion for Chrome Add to Chrome →

Analytics

The Catering Order Nobody Counts: Measuring a Restaurant's Biggest Ticket

Why catering is a blind spot

Catering is often the largest order a restaurant website produces. It's also the one least likely to be tracked. Everyday online orders usually run through an ordering platform with a purchase event already wired up. Catering rarely takes that path.

Big ticket, low volume, a different journey. Put those together and a broken catering conversion can go unnoticed for months, because nobody studies a report with a handful of rows. That's our framing from practice. We haven't measured how often catering goes untracked.

The three common paths

When we reviewed restaurant chain sites in August 2026, catering often ran through a different vendor from everyday ordering. In practice we see three paths:

  • A form on the brand site. The guest enters a date, a headcount and contact details, and someone calls back.
  • A third-party catering platform on another domain. The guest leaves your site to build and pay for the order.
  • A phone call that started on the website. The guest reads the catering menu and calls the store or a catering line.

Plenty of brands run more than one, and the website doesn't always make clear which is the real one. Your Restaurant Website Is Not One Website maps how those vendors stack up.

The walk-through test

Before you change anything, place a test catering request on every path you offer. Write down each page and each domain the guest passes through, and where the journey ends: a thank-you page, a confirmation screen on another domain, an email, or nothing at all.

Keep your browser's developer tools open if you can, so you can see whether any analytics or ad tag fires at the end. Often the end screen exists and nothing marks it.

What should record completion on each path

  • Form: a completion event that fires on a successful submit, not on the button click, so failed submissions don't count. A thank-you page works too, as long as the only way to reach it is by submitting.
  • Third-party platform: check whether the platform can load your analytics on its confirmation step or send a confirmation back to you. If it can't, its order export or confirmation emails become your record, and you match them to campaigns later.
  • Phone: call tracking by source where you use it. Where you don't, count clicks on the catering phone number as a separate, lower-value event, and be honest that a click isn't an order.

If you use Google Analytics, a completion event only counts as a conversion once it's marked as a key event. Google's help center describes doing it in Admin, under Data display, then Events, by clicking the star next to the event, and notes that marking an event doesn't change historic data (Mark events as key events). So mark it as soon as the event exists.

Catering as its own conversion

Give catering its own conversion, and don't let it share an action or a value with everyday online orders. One catering ticket averaged in with everyday orders makes both look wrong: average order value jumps, and the campaigns that drive catering look like they drive small orders.

Separation matters for ad bidding too. If catering and everyday orders share one primary conversion, bidding can't tell them apart. One Order, One Conversion covers primary and secondary actions in a restaurant Google Ads account.

The source check

Pull last month's catering orders from the catering platform or the POS. For each one, ask whether it carries any source at all: a campaign, a referral, even just website versus phone.

Your own catering flow is the one place you can fix this. Orders placed through a marketplace rarely come back with a source you control, as Your Own Orders vs Marketplace Orders explains.

If most rows are blank, the campaigns that drive catering get no credit, and the budget conversation goes to whatever can show results. That isn't a demand problem. It's plumbing. While you're in the export, check whether each order carries the store's location key (One Store, One Key).

What to fix first

  1. Record completion on every path, even roughly.
  2. Give catering its own conversion with its own value.
  3. Carry campaign source across the handoff to the catering platform, so it survives the change of domain.
  4. Report catering monthly, by source and by store.

Catering also skews store reports in busy weeks. Holiday Weeks Break Store Reports shows how to pull large orders out before ranking stores.

If you want help walking every catering path and wiring the conversions, book a data and tracking audit. To see what loads on your site before a guest makes a choice, request a free privacy scan; we review each request within 48 hours.

Rawsoft provides technical implementation and analysis, not legal advice. Please confirm any regulatory interpretation with your counsel.

Get new research by email

New posts and Website Privacy Index findings, sent to your inbox. No spam, unsubscribe anytime.

We only use your email for this list. See our Privacy Policy.

About Rawsoft

Rawsoft is an Atlanta-based digital data agency specializing in analytics implementation, privacy and consent management, and media tracking for enterprise brands.

Add Rawsoft as a preferred source on Google

More from the blog

Media Tracking

Your Restaurant Website Is Not One Website

A restaurant site hands visitors to ordering, loyalty, gift card and catering vendors on different domains. What that does to tracking, attribution and privacy.

August 2026Read

Analytics

Your Own Orders vs Marketplace Orders: The Guest Data You Never Get Back

A marketplace order and an order on your own site can be the same meal. Only one of them leaves you a guest you can market to.

November 2026Read