Requirements

RCA Storefront adds a module and library on top of an existing J2Commerce shop. Requirements split into mandatory stack, optional companions, and honest limits about what display lock means versus cart enforcement.

Joomla and PHP

Joomla 4, 5, or 6 with PHP 8.1 or newer is required for the documented 1.2.5 package line. The Product Catalog module manifest targets the same Joomla range and declares PHP 8.1 minimum.

J2Commerce

J2Commerce must be installed with published products you intend to show. You need Super User access or equivalent rights to install packages and publish modules. The package installer hard-fails with a clear reason when J2Commerce is missing so you do not get a silent half-install.

Mandatory for all Storefront use

You need the Storefront package itself: library plus Product Catalog module. You need at least one selection source populated in module options, whether manual product IDs, J2Commerce categories, content categories linked to shop articles, or a Conditional Products rule when that mode is selected.

Optional RCA Conditional Products

RCA Conditional Products is required only when you use product source Conditional Products rule or when you turn eligibility mode on for lock styling aligned with rules. Rule selection reads enabled rules from the Conditional Products component database table. Without CondProd installed, those module options cannot function as designed.

Optional OS Services Booking and Bridge

OS Services Booking plus RCA OSB to J2C Bridge is required only when you enable Show OSB duration or Show OSB availability on cards. Bridge sid_map must map service IDs to J2Commerce product IDs. No map means no duration from that path, even if the module toggles are on.

What Storefront will not enforce

Display lock is not cart enforcement. Shoppers can still add a locked-looking product unless RCA Conditional Products is installed, enabled, and configured with the J2Commerce Conditional Products plugin active. Storefront will not become a cart firewall no matter how convincing the CSS looks.

Template and builder notes

Storefront enqueues CSS through the library Web Asset Manager so template custom.css can override without fighting !important wars. SP Page Builder pages required explicit CSS fallback fixes in package 1.2.4; keep Storefront updated if builder pages are primary catalog hosts.