> For the complete documentation index, see [llms.txt](https://www.oddle.me/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.oddle.me/docs/new-guests/check-in.md).

# Oddle Check-in

Your walk-in guests are your biggest blind spot. They dine, they pay, they leave — and unless they booked online or ordered through your shop, you have no idea who they are. Oddle Check-in changes that by turning every in-store visit into a known guest, captured in a database you can market to again and again.

Oddle Check-in is an in-store check-in programme. Guests tap an NFC block or scan a QR code at your restaurant, check in with their details, and start earning rewards for returning. Behind the scenes, every check-in builds your customer database — complete with contact details, visit history, and insight data that powers smarter marketing.

***

## Key Concepts

**Check-in** — The core action. A guest taps an NFC block or scans a QR code at your restaurant. First-timers check in by entering their details; returning guests are recognised automatically.

**Programme** — Your check-in rewards programme. One programme per brand. It defines what rewards guests earn, what questions they're asked on check-in, and how notifications work. Programmes are versioned — you can draft a new version while the current one is live.

**Rewards** — Incentives attached to check-in milestones. Four types: welcome reward (first check-in), milestone rewards (N check-ins within N days), welcome back reward (lapsed guests), and birthday reward. All rewards are powered by Redeemable campaigns.

**Insight questions** — Optional questions guests answer on their first check-in: whether they live or work nearby, and how they discovered your restaurant. These responses become targeting data in your customer database.

**Check-in methods** — Three ways to deploy check-in at your restaurant: NFC blocks on tables (preferred), printable QR codes, and a check-in kiosk on a dedicated device.

***

## Where to Manage What

| What                                        | Where                                                            |
| ------------------------------------------- | ---------------------------------------------------------------- |
| Programme setup, rewards, and settings      | **Engage > Loyalty** in Merchant Admin                           |
| Check-in method deployment (NFC, QR, kiosk) | **Engage > Loyalty > Manage Check-in Options** in Merchant Admin |
| Redeemable campaigns for rewards            | **Redeemables** in Merchant Admin                                |
| Checked-in guest profiles and segments      | **Customer Intelligence** in Merchant Admin                      |
| Marketing to checked-in guests              | **Marketing** in Merchant Admin                                  |

> **Note:** The Loyalty page in Merchant Admin requires a **Virtual Lounge** to be set up first — your check-in page is hosted through your Virtual Lounge. See **Virtual Lounge**.

***

## In This Section

* **What Your Guests See** — The guest check-in experience from first tap to milestone reward
* **Setting Up Your Programme** — Creating your programme, configuring rewards, and managing versions
* **Deploying Your Programme** — Check-in methods, placement best practices, and getting check-ins in front of guests
* **Make Every Check-in Work For You** — How check-in data feeds Customer Intelligence and Marketing to grow your remarketing database


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.oddle.me/docs/new-guests/check-in.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.