Commerce Chain Optimization

Better Data is designed for real-world Commerce Chain Optimization, where a lead organization collaborates with subsidiaries, partners, distributors, and suppliers — without forcing everyone into the same heavy software experience.

CCO spans the full platform: Loop Engine (governance and audit), Commerce Gateway (LLM commerce tooling), SCM/DCM modules (inventory, procurement, orders, returns), and Signal Tags (physical authentication and compliance-triggering scans). Organization and billing models below describe how multi-party networks run on that stack.

The platform supports:

Multi-organization networks
Location-aware operations
Fine-grained access control
Flexible, network-friendly billing

All within a single, secure tenant.

Core Structural Concepts

Root Organization (Network Owner)

The Root Organization is the controlling entity for a commerce network. It typically represents the parent company, brand owner, or corporate operations/IT/finance.

The Root Organization:

Owns the master subscription
Controls which organizations are linked into the network
Assigns cross-organization administrators
Has visibility across its organizational hierarchy

Organizations (Business Entities)

An Organization represents a distinct business entity inside the network, such as:

Subsidiaries (manufacturing, distribution, retail)
Divisions or internal business units
Partners (marketplaces, retailers, 3PLs)
Suppliers and service providers

Organizations are linked together through Organization Relationships, forming a hierarchy.

Organization Relationships (Hierarchy)

Organizations are connected using explicit parent -> child relationships, each with a defined relationship type.

These relationships define visibility, administrative scope, billing inclusion, and collaboration boundaries.

sitemapExample: Luxe Bond Organization Hierarchy

LUXE BOND International Holdings (Root Organization)

SUBSIDIARY -> LUXE BOND Manufacturing LLC
SUBSIDIARY -> LUXE BOND Distribution LLC
SUBSIDIARY -> Luxe Bond, Inc
- SUBSIDIARY -> Salon Luxe Corporation
  - SUBSIDIARY -> Salon Luxe Distribution
PARTNER -> Amazon Fulfillment Services
PARTNER -> Sephora Inc.
PARTNER -> PackagePro Manufacturing (Upgraded)

Locations (Operational Context)

A Location represents where operations physically or logically occur, such as:

Warehouses and distribution centers
Amazon FBA centers
Retail stores
Manufacturing plants
Hospital wards (healthcare use cases)

Locations provide operational context:

Inventory is tracked per location
Shipments move between locations
Permissions can vary by location

Organizations may have many locations, and users’ permissions can differ by location.

Access & Administration Model

Organization Admin (`ORG_ADMIN`)

An ORG_ADMIN manages a single organization:

Users and roles within that organization
Locations and operational settings
Day-to-day administration

If an organization is a parent with subsidiaries, an ORG_ADMIN may also be granted visibility into its active subsidiary organizations, based on relationship rules.

Root-organization administrator (`ORG_SUPER_ADMIN`)

An ORG_SUPER_ADMIN is assigned at the Root Organization level. They can:

Manage the full organization hierarchy
Link or unlink organizations
Assign organization admins
Configure cross-organization collaboration
Manage billing configuration for the network

This role is typically held by corporate operations, IT, or finance teams.

Baseline Members

Users who are not administrators can still log in, participate in workflows, receive notifications, and manage their own preferences. They do not have administrative access unless explicitly granted.

Hybrid Billing Model (Network-Friendly)

Better Data uses a hybrid billing approach designed for multi-organization networks.

Billing Ownership

The Root Organization owns the master subscription and invoice.
Billing is consolidated at the network level.

Organization Billing Modes

Each linked organization can be configured with its own billing mode:

checkFREE

Lightweight participation for partners and small suppliers. Ideal for visibility, notifications, and limited collaboration.

buildingINCLUDED

Subsidiaries or internal organizations covered under the Root Organization’s plan.

plusADD-ON

Organizations that upgrade to a paid tier (e.g., PRO) and are billed as an add-on under the Root Organization’s subscription.

credit-cardSELF-PAY

(Future) Organizations that pay for their own subscription independently.

This model allows networks to grow organically: invite partners for free, upgrade organizations that need deeper operational capabilities, yet keep billing simple and centralized.

Luxe Bond Billing Example

"Partners join for free. As they grow and need autonomy, they upgrade — while billing stays consolidated under one network."