LifeRaft OSTM
← All add-ons

Commerce

RLX Store

Reusable digital order, entitlement, checkout, PayPal handoff, and protected download processor for commerce add-ons.

ProductionVersion 1.0.0
Product images coming soonA closer look at RLX Store.

What it does

Features at a glance

  • Generic order and order item tables for digital goods and add-on-driven purchases
  • Entitlement records with source add-on, item type, item id, title, license label, download URL, and download count
  • Optional PayPal checkout handoff when rlx-paypal is active
  • Manual admin actions for paid, fulfilled, and canceled orders
  • Free item auto-fulfillment when enabled in add-on settings
  • Integration hooks for order creation, order fulfillment, and downloads

Built for your workflow

Who it’s for

  • Businesses and creators organizing customer-facing workflows
  • Site owners adding focused sales or membership capabilities

Setup and fit

Compatibility

Requires a valid LifeRaft OS core license and a supported installation.

No additional add-on is listed as a required dependency.

Optional connections

From setup to everyday use

A straightforward starting point

  1. Free orders can auto-fulfill immediately
  2. Fulfillment grants one entitlement per order item
  3. Confirm rlx-store is active and the Store library nav setting is correct

Before you choose

Common questions

What does RLX Store do?

Reusable digital order, entitlement, checkout, PayPal handoff, and protected download processor for commerce add-ons.

What does RLX Store need to run?

RLX Store runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.

How ready is RLX Store for deployment?

Production is this add-on’s declared release stage. The V5 platform is a development build; review the workflows, hosting, and integrations you plan to use.

Review the launch checklist
  • Admin setup — Confirm settings, navigation placement, permissions, and any required starter content before launch.
  • Public QA — Review the public page, empty states, mobile layout, and activated/deactivated states.
  • Payment QA — Test provider setup, order states, entitlements, refunds, and failed-payment recovery.
  • Docs and support — Add customer-facing notes, admin setup instructions, and known limitations for the module.

Make RLX Store part of your build.

Discuss the fit, requirements, and next steps for your project.

Let’s talk