Shopify Commerce
Find your Shopify catalogue inside Capell.
- Version
- 1.1.4
- Released
- 10 November 2026
- Licence
- Commercial
Price £39.00
Check access and installation
Check your application before checkout
What it solves
The problem
Our team cannot see the latest synchronised Shopify catalogue inside Capell.
What your site gets
The site has a local copy of Shopify catalogue data with sync history.
Questions buyers ask
- Where is Shopify catalogue data stored?
- Products, variants and customers are synchronised into local records for Capell-side use.
- Can staff refresh the catalogue?
- Admins can re-sync products from the Shopify Commerce page.
- How can teams check sync freshness?
- The admin shows sync state and when the local catalogue was last synchronised.
Use it in your project
Connect a store and synchronise its products and customers into local records. Review sync status before relying on the local copy.
Picture it on your site
For a catalogue-led site, choose the Shopify store and review one product through synchronisation into the local record before relying on it publicly. Agree how the team notices and resolves stale sync data. The connection keeps a local catalogue available; your application still determines how that catalogue is presented and used.
6 captures
Support the customer journey
- Manage a separate Shopify connection for each site.
- Search cached products and request a fresh synchronisation.
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.
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.
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.
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.
This listing has no page of its own in the demo. Open the demo to see Capell running.
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
- The package declares: administration screens, command-line operations, public routes. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. May connect configured Capell content, media, or integration metadata to the named service boundaries for this package.
- Background work
- Scheduled background work is declared. Keep the host scheduler running and check the release documentation for queue workers, frequencies and pruning configuration.
- Access controls
- Package access controls are declared. Review role grants and the host authorisation configuration before allowing users into the new workflow.
- 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.
-
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
-
02
Require the package
composer require capell-app/shopify-commerce -
03
Install the extension
php artisan capell:extension-install capell-app/shopify-commerce -
04
Activate the package licence
In this site’s Admin, open Marketplace, find Shopify Commerce (capell-app/shopify-commerce), 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.
-
05
Report the installed package
php artisan capell:marketplace:heartbeat
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.4 Nov 10, 2026
- Recent activity
- 14 approved releases in the last 12 months
Review evidence for this release
Shopify integration reviewed with no defects found; webhooks are signature-verified, matched to an active connected store, rejected when stale and de-duplicated so a replayed delivery cannot repeat a destructive change.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.4
- Approval date
- Nov 9, 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
- Webhook writes use deliberate forced assignment of server-derived fields rather than mass assignment. Cross-package integration was not exercised by this per-package review; the local suites used SQLite, and live browser flows and server-database behaviour were not exercised. The MySQL/MariaDB-specific timestamp-repair branch was reviewed in source but was not executed by this SQLite attestation run.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
Version history
Showing the 10 most recent of 14 approved releases-
v1.1.4Nov 10, 2026 -
v1.1.3Nov 2, 2026 -
v1.1.2Oct 28, 2026 -
v1.1.1Oct 20, 2026 -
v1.1.0Oct 17, 2026 -
v1.1.0-beta.46Oct 9, 2026 -
v1.1.0-beta.45Oct 9, 2026 -
v1.1.0-beta.44Oct 8, 2026 -
v1.1.0-beta.43Oct 8, 2026 -
v1.1.0-beta.42Oct 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.