# How bookings work (/help/vendors/getting-started/how-bookings-work)



You get booked on bzar by creating a package and sharing its booking link: a customer requests or books it, and each request becomes a booking where the quote, contract and payments happen. Four ideas cover it:

* A **package** is something customers can book from you, with its own price, booking mode and **booking link**.
* A **request** is a customer asking to book one of your packages.
* A **booking** is one client's event with you, from the first request until it's done. Everything about it lives on one page.
* Quotes, contracts and payments are steps inside a booking, not separate places you go.

**Where to find it:** packages live in **Storefront → Packages** (`/dashboard/storefront/packages`). Requests and bookings live in **Bookings** (`/dashboard/bookings`).

## Two questions set up every package [#two-questions-set-up-every-package]

You never pick a "booking mode". You answer two questions about each package, and bzar sets up the rest.

### How do you price this package? [#how-do-you-price-this-package]

| Answer                      | Use it when                                                                                                                                                     | Customers see                      |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
| **One price**               | It costs the same every time. Add extras if longer or bigger events cost more: "Covers up to 2 hours and 75 guests, $175 each extra hour, $3 each extra guest." | "$650", or "From $650" with extras |
| **Per person**              | The total grows with the guest count. You can set a minimum guest count and a minimum total.                                                                    | "$35 per person"                   |
| **Per hour**                | The total grows with the hours booked. You can set minimum hours.                                                                                               | "$150 per hour"                    |
| **It depends on the event** | You can't price it until you hear about the event. Add a start price if you like.                                                                               | "From $800", or "Custom pricing"   |

### Do you approve each booking? (only when you have a set price) [#do-you-approve-each-booking-only-when-you-have-a-set-price]

| Answer                         | What the customer does                       | What you do                                                                      |
| ------------------------------ | -------------------------------------------- | -------------------------------------------------------------------------------- |
| **Yes, I review each request** | Sends a request and sees an estimated price. | Accept, adjust the price, or decline within 48 hours. Once you accept, they pay. |
| **No, confirm automatically**  | Picks an open time and pays.                 | Nothing. It's booked. Best for packages you run the same way every time.         |

A package priced **It depends on the event** is always reviewed: the customer sends their details, and you reply with a price.

Customers see one button on each package: **Book now**, **Request to book**, or **Get a quote**. Confirming automatically needs your weekly hours and connected payouts. See [getting paid](./getting-paid).

## Answering a request [#answering-a-request]

Every request opens to one screen with the event details, the customer's answers and the estimate line by line.

* **Accept**: the customer pays the deposit (or the full amount) to lock the date.
* **Adjust price**: change any line, add one (a longer trip, a bigger setup), and add a note. The customer sees the new price and pays when they accept.
* **Send price**: for a package priced **It depends on the event**, price it in the same screen.
* **Send a full quote**: when you want to give options, a payment schedule or a contract. Packages with a contract are always answered with a quote so the client signs before paying.
* **Decline**.

You have 48 hours to answer. We remind you after 4 hours and again when 24 hours are left.

If someone answers or changes the booking while you have it open, your action may be refused. The message stays on screen and the booking reloads its current status. Check that status before taking another action; do not assume your acceptance, decline or cancellation went through. A refund that already went through is not undone by a later status-update failure.

## Get booked by sharing a package link [#get-booked-by-sharing-a-package-link]

The fastest way to your first booking:

1. Add a package in **Storefront → Packages**.
2. Click **Copy link** on the package to copy its booking link.
3. Share it anywhere: your Instagram bio, a text, an email reply.

Customers who open the link land on that package and book it the way you set it up. You can also share your whole storefront with **Copy my booking link** on Home.

## When someone just sends a message [#when-someone-just-sends-a-message]

A customer can also write to you without picking a package. That arrives in your [Inbox](../messaging/inbox) as a plain **message**, tagged **From your storefront**. Reply, or use **Send a booking** to offer them a booking yourself. It becomes a quote on its own when it needs one.

## Whose move is it [#whose-move-is-it]

Every booking shows one status and one line that says whose move it is, for example "Your move: send a price" or "Waiting on Sam to pay the deposit". **Needs action** in Bookings lists only the bookings waiting on you. See [booking stages](../clients/pipeline) and [bookings and the client page](../clients/projects-and-portal).

## Good to know [#good-to-know]

* Payment changes are checked against the current booking and card attempt. An old card failure cannot overwrite a switch to Zelle, a received payment or a cancelled booking.
* When a customer accepts your counter-proposal with Zelle, they see the deposit or full amount without card fees, then the Zelle instructions. Accepting does not send the money or confirm that you received it.
* The customer summary uses each recorded payment's actual fee. A Zelle deposit followed by a card balance includes a service fee only on the card balance; unpaid payments use a card estimate only when paying by card.
* If a report, payment-method change or manual receipt is refused, its explanation stays on screen. Refresh the booking to review its current payments before acting again; a refused action does not send a new payment notification.
* The same applies to checking that Zelle did not arrive and marking or issuing a refund: the explanation stays visible while the booking refreshes, and old payment controls are removed until the current payment is shown.
* Money arriving after a booking hold expires follows the existing automatic-refund flow. It does not reopen the booking.
* A refund reserves its amount while Stripe confirms it. Only confirmed refunds count as money returned. A failed refund releases its reservation; an uncertain connection result keeps it until reconciled, so check the current payment before requesting another refund.
* Stripe dashboard refunds are recorded once and split proportionally between price and fees. Manual refunds are owed against the actual payments received; marking each one sent is your confirmation that you returned that money.
* Older recorded refund totals without matching refund records are preserved as legacy cap adjustments, not presented as new Stripe refunds. They still reduce what remains refundable.
* Your availability, inquiry form, questionnaires, deposit, cancellation policy and contracts all live in **Booking setup** (**Bookings → Setup**).
* **Get started** in the sidebar footer is your setup checklist. It is not the same as Booking setup.
