Integrations

Three RCA pieces often sit on the same site and do different jobs. Swap their responsibilities in your head and you will debug the wrong plugin with confidence.

What is Bridge responsible for?

Bridge maps OS Services Booking service IDs to J2Commerce product IDs through sid_map. After a valid hold on a mapped service, it adds the mapped product to cart and shows Continue to Checkout. It hardens embedded osbtable calendars on modern PHP and Joomla. Bridge equals booking to cart map.

What is RCA Storefront responsible for?

Storefront is Pro display. It draws product catalog modules and shared card layouts. It can show locked dependents and optional OSB duration on cards when a Bridge sid_map exists. Display lock is not cart enforcement. Storefront does not replace sid_map or hold logic.

What is RCA Conditional Products responsible for?

Conditional Products is Pro rules. Qualifying products unlock dependents. Cart and checkout enforce those rules through J2Commerce - RCA Conditional Products. An optional OSB route gate through System - RCA Conditional Products OSB can keep booking closed until the shopper qualifies. Bridge never reads those eligibility rules.

Can I run Bridge alone?

Yes. OS Services Booking plus J2Commerce plus Bridge with sid_map is enough when anyone who can hold may buy the mapped product. Add Storefront when you want a catalog presentation layer. Add Conditional Products when purchase or booking must wait for a qualifier.

How do vendor extensions fit?

OS Services Booking owns services, slots, and holds. J2Commerce owns products, cart, tax, coupons, and payment plugins such as RCA Stripe for J2Commerce. Bridge does not replace either vendor stack; it connects them with explicit IDs you maintain.

What about images and documentation assets?

Marketing PNGs live at https://recreatinganew.com/images/rca/osbj2c/ and copy into the plugin media folder after install. Use them in articles explaining your booking-plus-shop flow; they are not required for cart behavior.