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

# List Reservations

> Reserving list items to indicate intent to purchase or gift.

List Reservations allow items on a shared list to be "reserved", indicating that someone intends to purchase that item. This is particularly useful for gift registry scenarios where multiple people are shopping for a single customer.

## How reservations work

1. A customer creates a list (e.g., a wedding registry) and shares it via a shareable link
2. A gift-giver views the shared list and selects items they intend to buy
3. The gift-giver creates a reservation on those items
4. The registry owner's list shows those items as reserved, preventing duplicates

## Reservation fields

| Field           | Description                                                           |
| --------------- | --------------------------------------------------------------------- |
| `list_item_id`  | The list item being reserved                                          |
| `quantity`      | Number of units being reserved                                        |
| `reserver_name` | Optional name of the person reserving (for display to the list owner) |
| `status`        | Reservation status (`pending`, `purchased`, `cancelled`)              |

## Reservation lifecycle

* **Created**: a reservation is placed on a list item
* **Purchased**: the reserver confirms they completed the purchase
* **Cancelled**: the reservation is released (item becomes available again)

## API

Reservations are managed via the List Reservations API. Staff can view and manage reservations in Clienteling.

## Related

* [Product lists](/concepts/lists/overview)
* [List reservations API](/api-reference/product-list-reservations)
* [Working with product lists](/dev-guides/lists/working-with-product-lists)
* [Clienteling](/concepts/platform-surfaces/clienteling)
