Skip to content

ELMNT HUB

Add what the business needs. Keep one platform.

HUB is the expansion layer for BOS. Add approved operating modules without creating another disconnected account, customer list, or reporting stack.

Approved launch modules

One-time platform expansions.

These are the approved public launch prices. Configuration or custom development outside the documented module scope is quoted separately before work begins.

01

Commerce

Products, categories, inventory, orders, checkout, shipping, taxes, coupons, gift cards, variants, digital products, and commerce reporting.

  • Product and inventory workflows
  • Orders and customer records
  • Supported payment and fulfillment setup
$499one-timePurchase Module
02

Booking

Appointments, services, staff, availability, buffers, customer scheduling, reminders, and supported payment workflows.

  • Service and staff setup
  • Availability and scheduling rules
  • Customer booking experience
$299one-timePurchase Module
03

Restaurant

A restaurant operating layer on Commerce and Booking for menus, ordering, reservations, fulfillment, and restaurant workflows.

  • Menus and ordering
  • Reservations and availability
  • Kitchen and fulfillment states
$499one-timePurchase Module
04

Membership

Members, protected content, subscriptions, courses, downloads, community, and the member-facing dashboard.

  • Member access and plans
  • Protected content and courses
  • Member-facing account experience
$299one-timePurchase Module
Reviews is released, but no standalone public price appears because the approved pricing source does not define one.

Activation path

Requested, reviewed, configured, confirmed.

A module is not called active because a button was clicked. Installation state and health remain visible in BOS.

  1. 01

    Request

    Choose the module from the authenticated HUB and review its published scope and one-time price.

  2. 02

    Review

    ELMNT checks account access, dependencies, data boundaries, and any required website connection.

  3. 03

    Configure

    The module is installed and configured against the existing BOS account and shared business records.

  4. 04

    Confirm

    Testing and provider-dependent work complete before the installation state moves to active.

Expand without fragmenting

Add the workflow. Keep the operating system.

Start with BOS, then activate the modules that fit the business. Custom requirements are scoped separately.

BillingOne-time module price
AccessBOS account
StateProvider-confirmed