One commerce core
Catalog, cart and orders share a common foundation. Payment and delivery services connect to that foundation.
Joomla
Nexus — a store built around your business
The functions you need. Your own design. One commerce foundation.
Your customer wants to find a product, place an order and pay. You need a store you can develop with a clear understanding of its parts. Nexus brings the commerce core, store design and service integrations into a defined structure. We develop it through our own working stores.
When the store grows, complexity should not grow unchecked
Over time, a store can accumulate extensions, template overrides and one-off fixes. A small change then becomes a search for what depends on what. Extra scripts and oversized images can also burden the page. The useful question is not how many features a platform has, but which ones your store needs and how they work together.
How we build Nexus
Integrations selected for the store
Payment, delivery and marketplace connections are separate modules. Their availability and settings depend on the project.
A design of your own
The storefront’s appearance is separate from the commerce core. Different stores can have different identities on the same foundation.
Shared development
We maintain one common core across our projects, so each store does not need its own independent version of the platform.
A technical SEO foundation
Nexus includes support for canonical URLs, language alternatives and product structured data. Implementation depends on the store’s content and configuration.
Experience from real stores
We use Nexus in our own projects with different catalogs. The examples below show the stores themselves, not concept screens.
Considering an alternative to JoomShopping?
JoomShopping is an established Joomla shop system with an extension ecosystem. A well-working store does not need to be replaced just because another platform exists. Nexus is our approach when a project needs a clearly defined commerce foundation and individually composed storefront.
If this is your problem
Changes depend on many separate customizations.
Our approach in Nexus
A shared core with defined boundaries for design and integrations.
If this is your problem
Several stores have drifted into separate codebases.
Our approach in Nexus
One core, with configuration and appearance owned by each store.
If this is your problem
The store’s interface has become crowded.
Our approach in Nexus
Design the customer journey around the catalog and actions that matter to that business.
Speed comes from the whole page
A platform name alone does not make a site fast. Images, scripts, hosting and connected services all matter. Our approach is to control the store’s composition and measure the actual result. We have not published a like-for-like speed comparison with JoomShopping.
Nexus in our projects
Nexus is already used in our own commerce projects. Each site has its own design, product range and configured integrations.
HIDPLANET
Automotive diagnostics and accessories.
Endoskops
Endoscopes and inspection cameras.
Armikus
Home and pet products, plus mobile accessories.
Thunder
Active sound systems for cars.
OBDMarket
OBD interfaces and vehicle diagnostic equipment.
Aquapel
Automotive glass treatments. A project using the Nexus commerce engine.
Nexus integrations
Developed by
Integration with
EveryPay for Nexus
The EveryPay payment module for our Nexus stores.
Developed by
Integration with
Omniva for Nexus
The Omniva delivery module for our Nexus stores.
Developed by
Integration with
DPD for Nexus
The DPD delivery module within Nexus.
Developed by
Integration with
Swedbank Pay for Nexus
Swedbank Pay integration in development for Nexus.
Developed by
Integration with
eBay for Nexus
eBay integration tools in development for Nexus.
These integrations are for Nexus. They are separate from our JoomShopping products. The enabled services and settings vary by project.
Before you consider Nexus
Can I buy or download Nexus now?
Not yet. Nexus is used in our own projects; the public version is in preparation. A release date and commercial terms have not been announced.
Is it a replacement for every JoomShopping store?
No. Nexus is a Joomla-based commerce platform, but suitability depends on your catalog, workflows and required integrations. We do not claim universal feature parity.
Can an existing store move to Nexus?
A migration needs an assessment of products, customers, orders, URLs and custom functions. We are not offering an automatic migration service at this stage.
Does it guarantee better Google positions?
No. Technical preparation supports a site’s search visibility, but no platform can promise indexing dates or search positions.
Would Nexus fit your store?
Tell us what you sell, which platform you use and which payment or delivery services you need. These requests help us understand demand and set priorities for a public version.
An enquiry is not an order or a subscription. We will use your message to respond to your request.