RLX Marketplace

Solo or multi-tenant marketplace with vendor storefronts, scoped staff roles, polished listings, variants, inventory, licenses, entitlements, verified-purchase reviews, analytics, media, and extensible checkout.

Public marketplace directory with category filters, product filters, search fields, sorting, featured listings. Listing detail pages with Markdown descriptions, gallery images, lightbox-ready media, pricing, CTA links, seller. Admin listing manager for categories, item status, pricing, images, gallery uploads, product links, vendor.

RLX Marketplace can run as its own Commerce workflow. By itself, it focuses on Public marketplace directory with category filters, product filters, search fields, sorting, featured listings, card density sett, Listing detail pages with Markdown descriptions, gallery images, lightbox-ready media, pricing, CTA links, seller notes, specific, and Admin listing manager for categories, item status, pricing, images, gallery uploads, product links, vendor attribution, CTA links, so a customer can use the module without buying every related add-on first.

No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Marketplace should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.

When the customer also owns and activates related modules such as RLX Store, RLX Cart, RLX PayPal, RLX License Manager, and RLX Updates, RLX Marketplace can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.

RLX Marketplace commonly pairs with RLX Store, RLX Cart, RLX PayPal, RLX License Manager, RLX Updates. Active pairings depend on the package, customer workflow, and installed add-ons.

RLX Marketplace should be launched with its real data model and public routes in mind. Optional integrations: rlx-store, rlx-cart, rlx-paypal, rlx-license, rlx-updates, rlx-resources, rlx-membership, rlx-support, rlx-coins, rlx-wallet, rlx-coupons, rlx-affiliate, rlx-brands, rlx-teams, rlx-stats, rlx-changelog, rlx-gallery, rlx-defender, rlx-groups.

RLX Marketplace has a Access required Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.

Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.

Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.

Use Marketplace as the front door for products, addons, services, packs, and partner offers. Store can own orders, License can own entitlement, Updates can own downloads, Support can own help, and Resources can own supplemental files. Marketplace should make the offer easy to understand before the member enters the deeper workflow. For a Blender add-on shop, keep the product listing in Marketplace and set its Application to Blender. Use the listing gallery for preview images, specifications for compatibility, Store for orders, License for activation, Updates for downloadable releases, and Support for post-purchase help only when those add-ons are active. A separate shop add-on is unnecessary until a workflow needs ownership or permissions that Marketplace cannot provide.

No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.