Frontend

Shoppers experience Conditional Products as refused add-to-cart attempts, checkout blocks, messages when ineligible behavior is set to message, and optional booking route blocks when the OSB gate plugin is enabled. They do not see rule admin screens. Enforcement happens inside J2Commerce cart flows and OS Services Booking POST paths the plugins subscribe to.

Cart and checkout refusal

When a shopper tries to add a dependent without satisfying qualifiers per rule design, J2Commerce - RCA Conditional Products blocks or removes the line according to plugin logic and ineligible behavior. When qualifiers are satisfied through cart contents or order history per toggles, dependents behave like normal products. Clear cart between tests or you will chase ghost state.

Messages versus hidden dependents

Message behavior surfaces your ineligible message text when shoppers attempt too early. Hide behavior reduces visibility of dependents in contexts that honor hide mode. Disabled behavior may show products but prevent purchase. Align these choices with RCA Storefront locked modes if you run both products so shoppers are not told three different stories.

Booking gate behavior

System - RCA Conditional Products OSB applies rule checks when someone attempts booking POST or Bridge slot select before a hold is created, when enabled and targeting the routes your site actually uses. Without this plugin, OS Services Booking can remain bookable even when cart rules are strict. That surprises shops that assumed one rule silenced the entire funnel.

Storefront card appearance

RCA Storefront may show locked dependents, prerequisite links, or eligible-only filtering when eligibility mode integrates with the same rules. Card appearance can update when cart refresh is enabled and shoppers add qualifiers. Visual unlock is not proof of enforcement if the J2Commerce plugin is disabled; it only reflects module eligibility calculations.

Logged-in versus guest testing

Order history eligibility requires customers with past orders in the configured states. Guest sessions never magically gain history. Test with accounts that represent real customer journeys, not only Super User admin browsing.

What shoppers never see

Qualification logic any versus all, order state multiselect, and OSB service ID textareas are administrator concerns. Do not expose internal rule IDs in public copy unless you enjoy support email.