For Joomla Developers
Extend the store without touching the core.
J2Commerce runs on Joomla’s own MVC, events and scheduler, so client work goes into your own extensions and the core files stay unpatched.
How J2Commerce Helps
Native MVC with documented events, a REST API and CLI.
A controller is a Joomla controller, a model is a Joomla model, and an event goes through the CMS dispatcher. Your code lives in its own extensions, so core updates install cleanly.
-
Native Joomla 6 Architecture
Extensions register a service provider and resolve from Joomla’s own container, like any Joomla 6 extension.
-
Documented Events
Plugins attach to the cart, the price, the checkout and the order. A payment plugin lists its method, shows its form before payment and records the result after.
-
A REST API on Joomla’s Web Services
Products, orders, customers, inventory and tax are served by Joomla’s API application, with a bearer token on every request.
-
A Plugin in One Command
The scaffolder writes the manifest, service provider, extension class and language files for a new payment or shipping plugin.
-
Seven Scheduler Tasks
Recurring work runs as Joomla Scheduler tasks, configured, logged and triggered the same way as everything else on the site.
-
Vanilla JavaScript, Two Frameworks
ES modules, fetch() and event delegation with no jQuery, and Bootstrap 5 or UIkit layouts with an override service.
Also Built In
Tools for test sites and stores upgraded from older versions.
- Sample data on demand. One command loads the sample store, and another backfills the order ledger from older payment records.
- Products in Smart Search. Products join Joomla’s Smart Search as soon as the J2Commerce Smart Search plugin is enabled.
- A repair command with a dry run. It fixes product option settings left by old installs, and changes nothing until you tell it to.
- A changelog grouped by type. Each version lists what was added, changed, fixed and secured.
Keep Going
