Booking (Reservations) Add-on Guide for Larapen

Add multi-day reservation booking to your Larapen site. Manage bookable services with per-night pricing, handle guest reservations with check-in and check-out dates, and view everything on an interactive calendar, with optional payment integration.

Use Cases

The reservation system is designed for any business that accepts multi-day bookings:

• Hotels & B&Bs: Room reservations with per-night rates, minimum stay requirements, and guest limits.
• Venue Rental: Event spaces, conference rooms, or halls booked by the day with capacity enforcement.
• Equipment Rental: Multi-day rental of vehicles, tools, or other gear with date-range selection.
• Vacation Properties: Holiday homes or apartments with seasonal pricing and minimum night rules.
• Campgrounds & RV Parks: Campsite or RV spot reservations with maximum guest counts.

Requirements

Installation

Step 1: Upload the Add-on

In the admin panel, go to Admin → Extensions → Add-ons and click the Upload Add-on button. Select the add-on’s ZIP file: the system extracts it automatically and the add-on appears in the installed add-ons list.

Step 2: Activate the Add-on

Find Booking (Reservations) in the list and click Activate. Its migrations, seeders (if any) and permissions are set up automatically.

Step 3: Configure

Navigate to Admin → Booking → Settings to configure bookable services, opening hours, reservation rules, and notifications. See Configuration.

Purchase Code (License Key)

Booking (Reservations) is sold as a separate product, so it has its own purchase code (license key), distinct from the purchase code of the main application and from the one of every other add-on. You are asked for it when you activate Booking (Reservations) in Admin panel → Add-ons.

Our products are sold on three platforms. The way you receive a purchase code depends on where you bought the product.

1. bedigit.com Store (in-site purchase)

• As soon as the order’s payment status becomes Paid, a license key is generated automatically for every licensed item in the order (one key per purchased unit: buying 3 units gives 3 distinct keys).
• It is emailed to the address used on the order, either in a dedicated license email or inside the order confirmation email. Check your inbox and your spam / junk folder.
• The key stays available in your account under My Account → My Licenses. Keys are masked in the list; open the license detail page to reveal and copy the full key, see the domains it is activated on, and deactivate a domain to free an activation slot.
• The matching invoice is under My Account → My Orders.

2. Gumroad

• A Gumroad purchase produces two separate emails: the Gumroad receipt (sent by Gumroad, giving access to the files) and a license key email (sent by bedigit.com) that contains your purchase code.
• The license key email is generated as soon as Gumroad notifies us of the sale, so it normally arrives within seconds of the payment. Here too, check your inbox and your spam / junk folder.
• When the Gumroad product uses Gumroad’s own license-key feature, the same key also appears in your Gumroad receipt and under Library → your purchase on gumroad.com.
• Use the same email address on bedigit.com as on Gumroad: your keys are then linked to your account automatically and listed under My Account → My Licenses, even if you register after the purchase. You can also add a Gumroad key manually from My Account → My Gumroad Licenses.

3. Envato Market (CodeCanyon)

• Envato purchase codes are issued and delivered by Envato Market, never emailed by us, so there is nothing to look for in your spam folder: you retrieve the code from your Envato account.
• Log in to your Envato / CodeCanyon account, open the Downloads page, find the item, and choose License certificate & purchase code from the Download dropdown. The code is written in that certificate.
• An Envato purchase code looks like 12345678-90ab-cdef-1234-567890abcdef (8-4-4-4-12 characters). It never changes, and renewing item support does not issue a new one.
• Official Envato article: Where Is My Purchase Code?

Configuration

All settings are managed from /admin/booking/settings.

General Settings

Notification Settings

Notification toggles are managed from the centralized notification settings page at /admin/settings/notifications. The booking add-on registers 3 notification types:

Admin: Services

Manage bookable services at /admin/booking/services. The list view displays services in a sortable table with the following columns:

Create & Edit

The service form includes the following fields:

Service Images

When booking_service_images_enabled is turned on, each service supports image management via the HasMedia trait and the admin media picker:

• Featured image: The primary image shown in service cards on the booking page and at the top of the service detail.
• Gallery images: Additional images displayed in a lightbox gallery on the service detail view.

Admin: Reservations

Manage all reservations at /admin/booking/reservations. The list view includes status filter tabs and summary stats cards:

• Total Reservations: All-time count of reservations.
• Active Reservations: Currently confirmed and in-progress reservations.
• Check-ins Today: Reservations with today's date as check-in.
• Check-outs Today: Reservations with today's date as check-out.

Reservations can be filtered by status using the ReservationStatus enum:

Detail & Status

The reservation detail view shows:

• Guest information: Name, email, phone number, number of guests, and any notes.
• Reservation dates: Check-in date, check-out date, and total number of nights.
• Service details: Selected service name, price per night, and total price.
• Payment information: Payment status, gateway used, and transaction reference (when payment is required).
• Admin notes: Internal notes field for staff use.
• Status management: Dropdown to change the reservation status. Changing status triggers a notification email to the guest (if enabled).

Calendar View

Access the calendar at /admin/booking/reservations/calendar. Reservations are displayed as multi-day horizontal spans on a calendar grid, with each reservation color-coded by its status. The calendar fetches data from the calendar-events endpoint and supports month navigation.

Admin: Settings

Configure the booking system at /admin/booking/settings. Settings are organized into the following groups:

General

• Enabled (booking_enabled): Master on/off toggle for the booking system.
• Services per row (booking_services_per_row): Grid columns on the booking page.

Display Settings

• Service images (booking_service_images_enabled): Toggle image uploads and galleries for services.
• Service step title (booking_service_step_title): Custom translatable heading for the service selection step in the booking wizard.

Payment

• Require payment (booking_require_payment): When enabled, reservations must be paid at checkout to be confirmed. Requires at least one payment gateway add-on (Stripe, PayPal, Paddle, or MoMo).

Scheduling

• Advance days (booking_advance_days): How far into the future guests can book.
• Minimum advance hours (booking_min_advance_hours): How many hours before check-in a reservation can be placed.

Cancellation Policy

• Policy text (booking_cancellation_policy): Translatable text displayed to guests during the booking process. Supports separate content per language.

Notifications

Notification toggles are managed centrally at /admin/settings/notifications. See the Configuration section for the 3 notification types registered by this add-on.

CAPTCHA

• Enable CAPTCHA (booking_captcha_enabled): Adds CAPTCHA verification to the booking form to prevent automated spam submissions.

Front-end: Booking Page

Routes

Booking Wizard

The front-end booking page uses a multi-step wizard:

1. Step 1: Service Selection: Browse available services displayed as cards in a grid (configurable columns via booking_services_per_row). Each card shows the featured image (if enabled), service name, price per night, and guest capacity. Clicking a card selects the service and advances to the next step.
2. Step 2: Date Selection: An interactive calendar for choosing check-in and check-out dates. The calendar enforces the service's minimum and maximum night rules, advance booking limits, and availability based on remaining capacity. Unavailable dates are grayed out.
3. Step 3: Client Details, A form collecting guest information:
   • Full name (required)
   • Email address (required)
   • Phone number
   • Number of guests
   • Special requests / notes
   The cancellation policy is displayed here if configured. CAPTCHA is shown if enabled.

Front-end: Availability API

Two GET endpoints provide availability data consumed by the booking wizard's calendar:

Front-end: Confirmation

After a reservation is successfully submitted, the guest is redirected to /booking/confirmation/{reservation}. This page displays a summary of the reservation including the service name, dates, number of nights, total price, and a confirmation reference. If payment is required and has not yet been completed, a link to the checkout page is shown.

Front-end: Payment Checkout

When booking_require_payment is enabled, guests are directed to /booking/checkout/{reservation} to complete payment. The checkout page displays the reservation summary and a payment gateway selector showing all active payment gateways (Stripe, PayPal, Paddle, MoMo) installed on the site.

The Reservation model implements the Payable interface, allowing it to work with any payment gateway add-on. After successful payment, the reservation status is automatically updated to Confirmed.

Front-end: My Reservations

Authenticated users can view their reservation history at /booking/my-reservations. This page is accessible from the user menu under "My Reservations" and displays a list of the user's past and upcoming reservations with status, dates, and service details.

Notifications

The booking add-on defines 3 notification types, managed via the centralized notification system:

Toggle each notification on or off at /admin/settings/notifications. Individual users can also manage their notification preferences from their account settings.

Updating

1. Back up: Back up your database and the extensions/addons/booking directory before updating.
2. Replace files: Overwrite the extensions/addons/booking directory with the new version.
3. Run migrations: Execute php artisan migrate to apply any new database changes.
4. Clear caches: Run php artisan optimize:clear to clear all application caches.

Uninstallation

Switching an add-on off without losing anything is a deactivation: go to Admin panel → Add-ons, find Booking (Reservations) and click Deactivate.

• Its routes, views, admin menu entries and permissions stop being registered, and its front-end pages stop answering.
• Its database tables and all the data they hold are kept, and its files stay under extensions/addons/booking/. Nothing is deleted.
• The purchase code recorded at activation is kept too, so activating the add-on again does not ask for it.
• Deactivation is refused while another active add-on depends on this one: deactivate that add-on first.

Click Activate on the same card to switch it back on. Pending migrations are re-run, assets are republished, and the add-on picks up exactly where it left off.

Removing

Removing is permanent and destroys the add-on's data. The Remove button only appears on a deactivated add-on, so removal is always two steps:

1. Deactivate Booking (Reservations) (see Uninstallation).
2. Click Remove on its card and confirm the prompt.

The admin panel then, in one pass:

• runs the add-on's uninstall hook, if it ships one, while its code is still on disk;
• revokes the permissions declared in its addon.json;
• rolls back its migrations (this drops its database tables and every row they hold) and purges its entries from the migrations table, so a later reinstall migrates from scratch;
• deletes its published assets: public/addons/booking/, public/vendor/booking/ and storage/app/public/addons/booking/;
• deletes the add-on directory extensions/addons/booking/;
• deletes its row in the addons table (the recorded purchase code goes with it) and clears the application cache.

Removal is refused, with an explanatory message and before anything is destroyed, when the add-on is still active, when another active add-on depends on it, or when the web server (PHP) user cannot delete extensions/addons/booking/. In that last case, give that user write permission on the directory and on its parent, then try again.

Deleting the folder over FTP or SSH is not equivalent: the add-on's tables, its entries in the migrations table and its addons row are all left behind, and its card stays in the list. Use Remove in the admin panel instead.

Troubleshooting

No availability showing on the calendar

• Verify the service has is_active set to true.
• Check that max_capacity is greater than zero.
• Ensure booking_advance_days covers the dates you are trying to book.
• Confirm booking_min_advance_hours is not preventing near-term check-in dates.

Calendar not loading in admin

• Clear browser cache and check the browser console for JavaScript errors.
• Verify the calendar-events endpoint returns valid JSON by visiting /admin/booking/reservations/calendar-events directly.
• Ensure the admin user has the booking.reservations.view permission.

Payment errors at checkout

• Confirm at least one payment gateway add-on is installed and activated.
• Verify the payment gateway API keys are correctly configured in the gateway's settings.
• Check Laravel logs at storage/logs/laravel.log for detailed error messages.
• Ensure the Reservation model's Payable interface methods return correct values (amount, currency, description).

CAPTCHA not displaying

• Ensure booking_captcha_enabled is set to true in booking settings.
• Verify the global CAPTCHA driver and API keys are configured at /admin/settings/security.

Service images not showing

• Confirm booking_service_images_enabled is set to true.
• Check that images were uploaded through the admin media picker.
• Verify the storage symlink exists (php artisan storage:link).