> ## Documentation Index
> Fetch the complete documentation index at: https://docs.9pic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Offline Buyers

> Give 9Pic photos to people who paid you directly, one at a time or from a CSV.

## Overview

Some events sell photo packages themselves, for example on the registration form or at the venue desk. Add those buyers in **Checkout → Transactions** and they get the same photos as someone who bought through checkout. No payment goes through 9Pic.

> [!NOTE]
>
> You need to be a team admin, your plan must include Checkout, and the event needs checkout set up (a payment account chosen in **Configuration**) and at least one photo package. Buyers can only claim and download once original photos are enabled for the event.

## Add one buyer

**1. Open Transactions**

Open the event, choose **Checkout**, then the **Transactions** tab, and click **Add offline buyer**.

**2. Fill in the buyer**

Enter the **Buyer email** and choose a **Package**. Name, bib, amount, payment method and reference are optional.

**3. Choose whether to email them**

Tick **Email the buyer now** to send them a link to their photo pass. You can send it later from the order page instead.

**4. Save**

Click **Add buyer**. The order appears in the list with an **Offline** badge.

| Field | What it does |
| - | - |
| **Buyer email** | Required. The buyer must sign in with this email to see their photos. |
| **Package** | Required. One of the event's photo packages. Its photo count is how many photos the buyer can claim; "All photos" has no limit. |
| **Bib** | Optional. Fixes the buyer's photo search to this bib. They can add a selfie but can't use another bib. |
| **Amount received** | Optional. Counted in your revenue only when entered. |
| **Payment method** | Bank transfer, Cash or Other. |
| **Payment reference** | Optional, such as a registration ID. Shown to the buyer in the email. |

Adding the same email with the same package twice is rejected.

## Import from a CSV

**1. Prepare the file**

Use the columns `email, name, package, bib, amount`. Only `email` and `package` are required, and you can import up to 500 rows at a time. Write the package name exactly as the dialog lists it, or click **Download a template**.

**2. Check the file**

Click **Import offline buyers** and choose the file. Nothing is saved yet: every row shows **Ready**, **Duplicate** or **Needs fixing** with the reason.

**3. Import**

Pick how they paid and whether to email them, then click **Add N buyers**. Only the ready rows are added, a batch at a time. If a batch fails, the rows already added stay added and the rest show **Not added**.

> [!TIP]
>
> Fix the rows that need it and import the same file again. Buyers already added are skipped as duplicates.

## What the buyer does

1. They open the link in the email, or **My purchases** from your event page, and sign in with the email you entered.
2. The pass appears in their purchases. Before photos are live, they see it but can't claim yet.
3. They find their photos (by bib, or bib and selfie when you set a bib), choose up to the package limit and claim them.
4. They download originals like any other buyer.

If they sign in with a different email, nothing appears and they're asked to use the email they gave you. Accounts that only sign in with a phone number can't be matched.

## Fix or remove an entry

Open the order from the list. Until the buyer claims photos you can:

* **Edit buyer email** to fix a typo, then resend the access email from the order page.
* **Remove buyer** to delete the entry. The change is kept in your activity log.

After the buyer claims, the entry can no longer change. To add or correct an amount later, use **Edit amount** on the order.

## Reporting

Offline buyers show the gateway **Offline** and their claim progress in **Items**. An entry without an amount counts as a completed order but is left out of the average order value. **Download CSV** includes `offline_buyer` and `offline_buyer_bib` columns.

## Related

> **[Transactions](/dashboard-guide/checkout/transactions)**
>
> Review orders, revenue and claim progress.

> **[Order Detail](/dashboard-guide/checkout/transaction-detail)**
>
> Resend access emails, correct amounts and download originals.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.