Skip to main content
Capell home
Live demo
Released

Shop

Build commerce features on a shared Capell engine.

Version
1.0.9
Released
10 November 2026
Licence
Commercial

Check your application before checkout

Outcome

What it solves

The problem

Our developers need a commerce foundation without installing an admin or storefront.

What your site gets

The project has a commerce engine for headless or physical-retail work.

Questions buyers ask

Does the engine include a storefront?
The kernel adds no Shop-only public render transport. Later storefront packages can use the shared engine.
Can it support headless commerce?
Teams can install the commerce engine for headless or physical-retail work without admin or frontend packages.
How do extensions share commerce capabilities?
Typed scoped capability contracts provide shared lifecycle boundaries for later commerce surfaces.
Usage

Use it in your project

Use Shop as the foundation for commerce packages or a headless application. It supplies commerce contracts and lifecycle boundaries; a storefront is a separate concern.

Picture it on your site

For a commerce integration, identify the contracts and lifecycle events your application needs before choosing the packages above Shop. Build a representative purchase flow in the consuming application and test its boundaries. Shop is a foundation for that work, not a complete storefront, checkout design or ready-made operational process for selling products.

No workflow evidence published yet

No workflow screenshots are published. Use the demo or documentation to understand the extension before installing.

Included

Support the customer journey

  • Share scoped commerce capabilities across packages.
  • Connect provider-specific operations through common lifecycle contracts.

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.

Licence £59.00 / 12 months

One customer organisation; up to 5 named users. Each entitlement covers one production website or application and up to two non-production environments, with a maximum of three active installations.

12 months of protected downloads, updates and included standard support.

+ VAT where applicable

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

Renewal is charged at the price current when you renew. The price is shown before you pay.

Review site impact

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. Review compatibility and site impact, then follow the installation steps for this package.

Open the Capell demo

This listing has no page of its own in the demo. Open the demo to see Capell running.

Installation impact

Before you install

Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.

Admin and public surfaces
Surface impact is not declared in this listing. Ask the publisher which administration and public screens or routes it adds.
Data and migrations
Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. Uses package-local configuration and Capell metadata needed to enable the feature.
Background work
A complete jobs and scheduler assessment is not available here. Confirm background processing and worker requirements with the publisher.
Access controls
Access-control changes are not described here. Confirm the required roles and grants with the publisher.
Removal and retained data
A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
  1. 01

    Prepare protected Composer access

    Sign in to the account with active package access. Open its generated installation instructions and configure the protected Composer repository before running the commands below. Keep access credentials private. Open my package installation instructions

  2. 02

    Require the package

    composer require capell-app/shop
  3. 03

    Install the extension

    php artisan capell:extension-install capell-app/shop
  4. 04

    Activate the package licence

    In this site’s Admin, open Marketplace, find Shop (capell-app/shop), and activate its licence using the purchase licence key if requested. This activates the package you have already installed. Wait for the Marketplace operation to succeed before continuing; keep its queue worker running.

  5. 05

    Report the installed package

    php artisan capell:marketplace:heartbeat
Release and review evidence
Maintenance

Release activity stays visible

These dates come from approved package releases, so you can see the release trail before installing.

Latest approved release
v1.0.9 Nov 10, 2026
Recent activity
14 approved releases in the last 12 months
Capell reviewed

Review evidence for this release

Commerce foundation package reviewed with no defects found; it is a contracts and capability registry layer with no routes, models or stored data of its own.

Review reduces risk, but it is not a permanent security guarantee.

Automated checks passed
AI-assisted analysis completed
Human sign-off completed
Reviewed version
1.0.9
Approval date
Nov 8, 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

  • A site with no registered commerce extension gets contracts and health reporting only.

Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.

Changelog

Release notes and maintenance evidence

Version history

Showing the 10 most recent of 14 approved releases
  1. v1.0.9
    Nov 10, 2026
  2. v1.0.8
    Nov 2, 2026
  3. v1.0.7
    Oct 28, 2026
  4. v1.0.6
    Oct 20, 2026
  5. v1.0.5
    Oct 17, 2026
  6. v1.0.4
    Oct 9, 2026
  7. v1.0.3
    Oct 9, 2026
  8. v1.0.2
    Oct 8, 2026
  9. v1.0.1
    Oct 8, 2026
  10. v1.0.0
    Oct 7, 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?

There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy

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.