Skip to main content
Coming Soon — The Theoretical Reporting Setup Service will be available once PMIX Mapping and Theoretical Usage features launch in Garde. Contact contact@garde.app to be notified when it becomes available.

​
Overview

​
What will be included

​
Overview

​
What Is the Theoretical Reporting Setup Service?

Let’s be honest — PMIX mapping is important, but it’s also time-consuming. And if you’re running a restaurant, “time-consuming” usually means “not getting done.” That’s exactly what this service is for. With the Theoretical Reporting Setup Service, one of our industry experts works directly with your team across three 45-minute sessions. They’ll walk you through everything: PMIX mapping best practices, how to connect your POS buttons to products and recipes, and how to actually turn your theoretical reports into actionable results. By the end, you’ll be set up and confident enough to manage it going forward.

​
What Is PMIX Mapping?

Before you can run theoretical reports, you need to map your product mix (PMIX). This means connecting your POS buttons to the products or recipes in Garde. It’s the bridge between “what you sold” and “what you should have used.” Once your PMIX is mapped, you unlock two powerful tools:
  • Menu Analysis — Engineer your menu for maximum profitability.
  • Theoretical Usage Reports — Quickly spot variances and reduce food costs.

​
How Much Does It Cost?

$250 for three 45-minute sessions. That’s it.

​
When Will I Be Billed?

After you schedule your first call, we’ll ask you to confirm the service via email. You’ll be billed on your next Garde billing cycle (typically the following month). If you pay annually, the charge hits about 30 days after confirmation.

​
Logistics

​
Are There Set Topics for Each Session?

Roughly, yes — but we tailor things to where your team is at. Here’s the general flow: Session 1 covers the foundations:
  • How to connect products and recipes to your POS in Garde
  • Setting up customizations — what’s sold, added, removed, substituted, doubled, halved, etc.
  • Understanding the relationship between parent items and modifiers
  • Linking modifiers and menu items for granular detail on customizations and a la carte purchases
  • Best practices so you get the most benefit for the least amount of work
Session 2 is a working session. Your team will have started mapping between calls, so we’ll spot-check your progress and troubleshoot anything that came up. Session 3 is where it all comes together. You’ll learn how to use the Theoretical Usage and Menu Analysis reports to actually drive results — not just look at numbers.

​
Is There Anything I Should Know Before We Start?

Two things:
  • Bring the right person. Grab whoever on your team knows your POS button setup best, and make sure they’re available for all three calls. This works best when the person doing the mapping is on the line.
  • Get your recipes into Garde first. We need recipes in the system before we can map buttons to them. If you need help with that, we have a Recipe Setup Service.
If you’re part of a restaurant group, start with the location that has the most complete POS setup. That becomes your model for the other locations.

​
How Long Does the Process Take?

That depends on your team’s pace and how many products you’re mapping. We give you three 45-minute calls, but you decide the spacing. Some teams knock it out in a week. Others spread it over a month. Whatever works for your operation.

​
Once We Start, How Long Until I See My Theoreticals?

Once your PMIX mapping is done, you’ll need to take and close two inventories in Garde before theoretical data starts showing up. If you need a refresher on inventory, we have a reference guide for that.

​
What If I Have Multiple Locations?

The three setup sessions apply to one location. You can use what you learn to map additional locations yourself. If some or all of your locations share the same menu, we offer a PMIX copying service — we’ll copy the mappings from your source location to others for $250 per location. This only works when the menus are virtually identical across locations.