Bookings
Let visitors request appointments and keep every request in one queue.
- Version
- 1.1.1
- Released
- 20 October 2026
- Requires
- Customer Portal
- Licence
- Commercial
Price £99.00
Check access and installationOn this page
- Price and access
Review the price, licence and availability before deciding what to adopt.
- Your workflow
Read how the package is used and what your application needs to provide.
- Product captures
Review the available captures and see which part of the workflow each screen demonstrates.
- Capabilities
See which jobs this extension supports and which parts it adds to your site.
- Project fit
Decide what this removes from your workload and what your application still needs to supply.
- Installation
Check the setup steps before adding the package to a project.
- Release evidence
Review the available release, maintenance and package-review information.
Check your application before checkout
Use it in your project
Set up services, staff, locations and availability, then let visitors submit requests from the public booking form. Operators confirm or cancel requests and can add reminders, reviews and waitlists as the operation grows. Bookings requires the paid Customer Portal extension, which is licensed separately.
Picture it on your site
For an appointment service, model one service and its real availability first, then try a request through confirmation or cancellation. Agree who handles requests and what customers see in their account. Include the separately licensed Customer Portal in the adoption decision; a booking form alone does not define how your staff will run the service.
Support the customer journey
- Manage services, staff, locations and availability windows.
- Review, confirm or cancel appointment requests with an audit trail.
Is this right for your project?
Fit the customer journey
Map the step this extension supports before connecting it to your checkout or account area. Be explicit about which system owns the customer, product, payment and fulfilment records. A focused package can remove work from that step without becoming your whole commerce platform. The application remains responsible for connecting the supported workflow to its own customer and order rules.
Test more than the happy path
Use test data to check an ordinary customer journey, a rejected input and an interrupted or repeated action. Review the resulting records and the message shown to the customer. Where an external provider is involved, its credentials, sandbox and operational requirements are separate setup work; a package installation is not evidence that the complete commercial journey is ready.
You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy
Your renewal price stays locked while you renew continuously, including during the grace period. After a full lapse, renewal uses the current list price.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Explore the available extensions on the demo site.
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/bookings -
02
Install the extension
php artisan capell:extension-install capell-app/bookings
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.1 Oct 20, 2026
- Recent activity
- 7 approved releases in the last 12 months
Review evidence for this release
Appointment booking package reviewed: public submissions are validated and throttled, provider webhooks require both a shared token and a payload signature, and no defects were found.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.1
- Approval date
- Oct 19, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Customer portal pages (proposals, reviews, consent, lesson lists) are reached by unguessable link tokens rather than a login, which is deliberate for customers who have no account.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
7 releasesv1.1.1Oct 20, 2026v1.1.0Oct 17, 2026v1.1.0-beta.46Oct 9, 2026v1.1.0-beta.45Oct 8, 2026v1.1.0-beta.44Oct 8, 2026v1.1.0-beta.43Oct 7, 2026v1.1.0-beta.42Oct 4, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.