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

# Guest checkouts

> Adoptions away from the shelter: a link for a pet store, an adoption event or a foster home, where whoever is there picks the animal and the adopter is sent the contract to sign and the fee to pay.

A guest checkout is for adoptions that happen somewhere else: a pet store, an adoption event or a foster home. You make it with its animals and share its link, or its code to scan. Whoever is there (a volunteer, a foster, the store's staff) opens it on a phone or tablet with no sign-in, picks the animal and enters the adopter. RescueConsole approves the adoption and emails the adopter the contract to sign and the fee to pay, exactly as if you had [sent it from home](https://docs.rescueconsole.com/animals/application-contract.md#signing-from-home) yourself.

Open it from **Adoptions** in the sidebar, then **Guest checkouts**. Anyone whose role can **See** Animals can open the list. Making, changing and closing one needs **Change** on Animals.

## Making one

Press **New guest checkout**.

| Field | What it is for |
| - | - |
| **Name** | The store, the event or the foster home. The contract says the adoption was completed there. |
| **Where** | **A store or other location**, **An adoption event** or **A foster home**. |
| **Adoption contract** | The [contract template](https://docs.rescueconsole.com/settings/contract-templates.md) its adopters sign. The rest of what the contract asks is answered by the checkout: who approved it, where it was completed, and how the fee is paid. The adopter answers the media release. |
| **The fee** | **By card, with the link sent when they sign** (the fee is paid by card as soon as they sign), or **The adopter chooses from your ways to pay**. |
| **Last day** | It closes the day after, at midnight in your organization's time zone. Leave it empty to keep it open until you close it. |
| **Access code** | Optional, 4 to 40 characters. Anyone sending a contract through it must enter the code, so somebody with only the link can look at the animals but cannot send anything. You see whether a checkout has a code, never the code itself: give a new one, or tick **Take the code off**. |
| **Its income goes to** | The [fund](https://docs.rescueconsole.com/fundraising/funds-and-appeals.md) its adoption fees go to. Shown to those who can see Fundraising. |
| **An adopted animal** | **Is hidden from the guest**, or **Shows as adopted**. |
| **Who approves its adoptions** | The member of your team the contract names as approving them. You, unless you choose someone else. |
| **Its animals** | Animals in your care, added with **Add an animal**. Take one off with the cross beside it. |

Press **Make the guest checkout**.

## Sharing it

The checkout's page has its link to copy and a code to scan, with **Download the code** to print it for a table or a kennel card. Your public site needs an address for there to be a link.

## What the guest sees

The page on your site shows the checkout's name and its animals, each with its photo and adoption fee. An animal whose contract has been sent and not yet signed shows **Contract sent, waiting to be signed** and cannot be chosen again. An adopted animal is hidden, or shown as **Adopted**, as you chose.

The guest picks the animal and enters the adopter's first and last name, email (where the contract is sent), and phone and address if they have them, then their own name and the access code if there is one, and presses **Send the contract**. The page says it was sent, or what was wrong.

A checkout takes ten wrong access codes an hour from one device's address, 20 contracts an hour from one address and 100 a day in all, and nothing is made if its contract has been taken out of use or your site has no address yet.

What happens then:

1. The adopter is found in People by their email, or added.
2. Their application is made with the animal and approved, as the person who made the checkout, with a note saying where and by whom.
3. The contract is emailed to them to sign. Signing records the adoption, and with the fee by card they go straight on to pay.

The demo sends no contracts, so the button on the demo's checkout says so.

## What happened

The checkout's page lists everyone sent a contract through it, for which animal, when and by whom, and where each stands: **Sent, not signed yet**, **Signed, not paid yet**, **Went home** with what was paid, **Link expired** or **Canceled**. Above them it counts who went home, what was received, and who is still to sign.

## Closing it

**Close it** stops the link working at once. A checkout with a last day closes on its own the day after. Either way, whoever made it gets the summary on their bell: who went home, what was received, and who is still waiting. Anything still waiting carries on as it would have: the contracts stay open to sign until their links expire.


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