> For the complete documentation index, see [llms.txt](https://docs.loopit.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loopit.co/bookings/lifecycle-of-a-booking/pausing-a-booking.md).
# Pausing a Booking
The **Pause Booking** feature in Loopit gives you the flexibility to temporarily pause a customer’s active booking and resume it later—perfect for handling vehicle servicing, customer requests, or unforeseen events.
## What is a Paused Booking?
A **Paused Booking** is a booking that has been temporarily placed on hold. While paused:
* No invoices are generated
* No payments are processed
* The booking cannot be edited
* The customer retains their current booking arrangement
This is typically used when a customer plans to continue their booking, but a temporary interruption is needed—such as waiting for a vehicle replacement or resolving a mechanical issue.
***
## When to Pause vs When to End a Booking
Knowing when to pause a booking versus when to end it can help you keep your billing accurate and your operations running smoothly.
### **✅ When to Pause a Booking**
As a general rule, **pause a booking only if the booking is likely to continue**.
**Example scenarios:**
* The vehicle has a mechanical issue and the customer is waiting for a replacement.
* The customer has requested a temporary hold but intends to resume.
**Why pause?**\
Pausing stops invoicing and payments without closing out the booking, so the customer can easily pick up where they left off.
### **❌ When *****Not***** to Pause a Booking**
If the booking is **unlikely to continue**, it’s better to **end the Booking** rather than pause it.
**Example scenario:**
* A vehicle is returned with damage, and you're waiting for repair costs.
In this case, **don’t pause**—instead, end the booking. Loopit allows you to:
* Raise charges (e.g. for damage) even after a booking ends
* Retain credit notes and deposits on file
This approach keeps your records clean and avoids confusion in reporting or billing.
***
## How to Pause a Booking
1. Go to the booking you want to pause.
2. From the action menu, select **Pause Booking**.
3. Confirm the action.
{% hint style="info" %}
Only bookings with an **Active** status can be paused. Bookings with scheduled changes cannot be paused.
{% endhint %}
Once paused:
* The status will change to **Paused**
* Future invoices and payments will be suspended
* No further payments will be processed
***
## How to Resume a Booking
1. Open the paused booking.
2. From the action menu, click **Resume.**
3. Confirm the action.
Once resumed:
* The status will update to **Active**
* Invoicing and billing will resume based on the booking’s original configuration
***
## How Credit Notes and Pro-Rata Billing Work
When a booking is paused, Loopit calculates the unused portion of the invoiced period and issues a **credit note** accordingly. In some cases, a **prorated invoice** may also be generated when the booking resumes.
**Scenario 1: Pause and Resume Within the Same Billing Cycle**
* Example: A weekly booking from **12–18 May** is paused on **13 May** and resumed on **16 May**.
* Loopit will:
* Issue a credit note for 3 unused days (13–16 May)
* **Not issue a new invoice**, as the resume occurred within the same billing cycle
**Scenario 2: Pause Spans Across Billing Cycles**
* Example: The booking is paused on **13 May** and resumed on **22 May**
* Loopit will:
* Issue a credit note for the unused portion of the previous billing cycle (13–18 May)
* Generate a prorated invoice for 22–25 May (until the next full cycle begins)
* Resume regular billing from **26 May**
***
## Tracking Paused Bookings
To help you manage paused bookings effectively, Loopit provides clear visibility into how long each booking has been in a paused state.
* The **number of days paused** is displayed in both:
* The **booking action menu**
* The **booking table view**
This makes it easy to identify which bookings are currently paused and for how long—helping you avoid situations where a booking is unintentionally left paused and not collecting payments.
Additionally:
* All **pause and resume actions** are recorded in the **booking timeline**, showing:
* The exact date and time the pause or resume occurred
* The team member who performed the action
This ensures full transparency and accountability when managing paused bookings.