Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    1. Docs
    2. /Features
    3. /Ring ERP
    Updated Jul 23, 20263 min listen
    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    1. Docs
    2. /Features
    3. /Ring ERP
    Updated Jul 23, 20263 min listen
    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    1. Docs
    2. /Features
    3. /Ring ERP
    Updated Jul 23, 20263 min listen
    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Ring ERP

    Ring ERP is the operator cockpit over the multi-vendor store: warehouse stock, checkout holds, paid-sale commit, and the vendor settlements ledger. It does not invent a second stock system — it extends ERPStockService, inventory-sync, and PaymentConductor paid handlers.

    Use the docs sidebar Founder / Developer tabs to filter this page. Affiliate token minting stays on Affiliate enablement / Refcodes — ERP owns stock + the settlements ledger + hub UI.

    Inventory & stock

    Locked invariant, checkout reserve, commitSaleForOrder, cancel/refund restore.

    Commissions & settlements

    Settlements ledger, hold/release, dry-run payouts, referral rates.

    Vendor management

    Vendor lifecycle, stock ownership, earnings surfaces.

    Multi-vendor store

    Catalog, cart, checkout — ERP reacts after payment.

    What you get as an operator

    SurfaceRouteDay-1 job
    Store hub overview/admin/storeStock summary + pending settlements at a glance
    Products / Orders/admin/store/products, /admin/store/ordersCatalog approval and fulfillment status
    Stock/admin/store/stockLow-stock filters, reason-coded restock, movement timeline
    Commissions/admin/store/commissionsHold/release, dry-run due payouts, then process
    Vendor stock/vendor/stockOwn-product restock (bulk), low-stock badges
    Vendor earnings

    Architecture (verified)

    Checkout reserve → paid commit → settlements
    ModulePathRole
    Constantsfeatures/store/constants/stock.tsZERO_WAREHOUSE_ID, DEFAULT_INVENTORY_STORE_ID
    ERP stockfeatures/store/services/erp-stock-service.tsRestock/adjust; levels-aware getStockLevel
    Inventory syncfeatures/store/services/inventory-sync.tsReserve, fulfill, commitSaleForOrder, restore
    Settlementsfeatures/store/services/settlement.ts + settlement-pipeline.tsLedger + referral assists

    Roadmap phases

    1. Surface enablement (shipped) — Thin /admin/store tabs + vendor pages + EN ERP docs.
    2. Hub P0 (shipped 2026-07) — Invariant + paid commit + reverse paths + hub depth.
    3. Expansion waves — Cart soft-holds, transfers UI, RMA, Greenfood lots/FEFO (see empire plan; not clone-docs fiction).

    Related documentation

    Inventory & Stock

    Deep-dive: stock invariant, reserve, commitSaleForOrder, cancel/refund.

    Commissions & Settlements

    Same-workflow: settlements ledger after paid commit.

    PaymentConductor

    Depends-on: PaymentConductor remains payment SSOT; ERP reacts to paid/refund.

    Multi-Vendor Store

    Prerequisite: multi-vendor catalog and checkout before ERP ops.

    Ring ERP

    Ring ERP is the operator cockpit over the multi-vendor store: warehouse stock, checkout holds, paid-sale commit, and the vendor settlements ledger. It does not invent a second stock system — it extends ERPStockService, inventory-sync, and PaymentConductor paid handlers.

    Use the docs sidebar Founder / Developer tabs to filter this page. Affiliate token minting stays on Affiliate enablement / Refcodes — ERP owns stock + the settlements ledger + hub UI.

    Inventory & stock

    Locked invariant, checkout reserve, commitSaleForOrder, cancel/refund restore.

    Commissions & settlements

    Settlements ledger, hold/release, dry-run payouts, referral rates.

    Vendor management

    Vendor lifecycle, stock ownership, earnings surfaces.

    Multi-vendor store

    Catalog, cart, checkout — ERP reacts after payment.

    What you get as an operator

    SurfaceRouteDay-1 job
    Store hub overview/admin/storeStock summary + pending settlements at a glance
    Products / Orders/admin/store/products, /admin/store/ordersCatalog approval and fulfillment status
    Stock/admin/store/stockLow-stock filters, reason-coded restock, movement timeline
    Commissions/admin/store/commissionsHold/release, dry-run due payouts, then process
    Vendor stock/vendor/stockOwn-product restock (bulk), low-stock badges
    Vendor earnings

    Architecture (verified)

    Checkout reserve → paid commit → settlements
    ModulePathRole
    Constantsfeatures/store/constants/stock.tsZERO_WAREHOUSE_ID, DEFAULT_INVENTORY_STORE_ID
    ERP stockfeatures/store/services/erp-stock-service.tsRestock/adjust; levels-aware getStockLevel
    Inventory syncfeatures/store/services/inventory-sync.tsReserve, fulfill, commitSaleForOrder, restore
    Settlementsfeatures/store/services/settlement.ts + settlement-pipeline.tsLedger + referral assists

    Roadmap phases

    1. Surface enablement (shipped) — Thin /admin/store tabs + vendor pages + EN ERP docs.
    2. Hub P0 (shipped 2026-07) — Invariant + paid commit + reverse paths + hub depth.
    3. Expansion waves — Cart soft-holds, transfers UI, RMA, Greenfood lots/FEFO (see empire plan; not clone-docs fiction).

    Related documentation

    Inventory & Stock

    Deep-dive: stock invariant, reserve, commitSaleForOrder, cancel/refund.

    Commissions & Settlements

    Same-workflow: settlements ledger after paid commit.

    PaymentConductor

    Depends-on: PaymentConductor remains payment SSOT; ERP reacts to paid/refund.

    Multi-Vendor Store

    Prerequisite: multi-vendor catalog and checkout before ERP ops.

    Ring ERP

    Ring ERP is the operator cockpit over the multi-vendor store: warehouse stock, checkout holds, paid-sale commit, and the vendor settlements ledger. It does not invent a second stock system — it extends ERPStockService, inventory-sync, and PaymentConductor paid handlers.

    Use the docs sidebar Founder / Developer tabs to filter this page. Affiliate token minting stays on Affiliate enablement / Refcodes — ERP owns stock + the settlements ledger + hub UI.

    Inventory & stock

    Locked invariant, checkout reserve, commitSaleForOrder, cancel/refund restore.

    Commissions & settlements

    Settlements ledger, hold/release, dry-run payouts, referral rates.

    Vendor management

    Vendor lifecycle, stock ownership, earnings surfaces.

    Multi-vendor store

    Catalog, cart, checkout — ERP reacts after payment.

    What you get as an operator

    SurfaceRouteDay-1 job
    Store hub overview/admin/storeStock summary + pending settlements at a glance
    Products / Orders/admin/store/products, /admin/store/ordersCatalog approval and fulfillment status
    Stock/admin/store/stockLow-stock filters, reason-coded restock, movement timeline
    Commissions/admin/store/commissionsHold/release, dry-run due payouts, then process
    Vendor stock/vendor/stockOwn-product restock (bulk), low-stock badges
    Vendor earnings

    Architecture (verified)

    Checkout reserve → paid commit → settlements
    ModulePathRole
    Constantsfeatures/store/constants/stock.tsZERO_WAREHOUSE_ID, DEFAULT_INVENTORY_STORE_ID
    ERP stockfeatures/store/services/erp-stock-service.tsRestock/adjust; levels-aware getStockLevel
    Inventory syncfeatures/store/services/inventory-sync.tsReserve, fulfill, commitSaleForOrder, restore
    Settlementsfeatures/store/services/settlement.ts + settlement-pipeline.tsLedger + referral assists

    Roadmap phases

    1. Surface enablement (shipped) — Thin /admin/store tabs + vendor pages + EN ERP docs.
    2. Hub P0 (shipped 2026-07) — Invariant + paid commit + reverse paths + hub depth.
    3. Expansion waves — Cart soft-holds, transfers UI, RMA, Greenfood lots/FEFO (see empire plan; not clone-docs fiction).

    Related documentation

    Inventory & Stock

    Deep-dive: stock invariant, reserve, commitSaleForOrder, cancel/refund.

    Commissions & Settlements

    Same-workflow: settlements ledger after paid commit.

    PaymentConductor

    Depends-on: PaymentConductor remains payment SSOT; ERP reacts to paid/refund.

    Multi-Vendor Store

    Prerequisite: multi-vendor catalog and checkout before ERP ops.

    /vendor/earnings
    Pending + history from settlements

    Typical scenarios

    1. Prevent oversell — Checkout reserves sellable units (available). A second checkout cannot take reserved stock.
    2. Paid order — PaymentConductor marks paid → stock commits once (idempotent) → settlement row appears for each vendor slice.
    3. Buyer cancels unpaid — Holds release; sellable returns. Refund after paid restores stock from sale movements (WayForPay Refunded/Voided wired).
    4. Payout day — Dry-run due settlements, then Process due payouts (simulated badge until on-chain mode is verified).

    Default warehouse label is zero-warehouse (store id 1). Nova Poshta pickup points in shipping APIs are not ERP warehouses.

    Shipped vs backlog

    Shipped (hub P0): stock invariant, commitSaleForOrder, admin hub landing, stock/commissions depth, vendor ownership on restock.

    Admin actionsapp/_actions/admin-store-erp.tsInit stock, hold/release, dry-run, adjust
    Paid handlerslib/payments/conductor/handlers/store-order*.ts + credit/token routesCall commitSaleForOrder

    Invariant: store_products.stock === inventory_levels.available + inventory_levels.reserved · sellable = available.

    ProcessConductor owns TTL cleanup (cleanup-reservations) and settlement-payout cron — do not duplicate.

    Affiliate & Referral Enablement

    See-also: dual-rail referral — ERP ledger vs refcodes token rewards.

    /vendor/earnings
    Pending + history from settlements

    Typical scenarios

    1. Prevent oversell — Checkout reserves sellable units (available). A second checkout cannot take reserved stock.
    2. Paid order — PaymentConductor marks paid → stock commits once (idempotent) → settlement row appears for each vendor slice.
    3. Buyer cancels unpaid — Holds release; sellable returns. Refund after paid restores stock from sale movements (WayForPay Refunded/Voided wired).
    4. Payout day — Dry-run due settlements, then Process due payouts (simulated badge until on-chain mode is verified).

    Default warehouse label is zero-warehouse (store id 1). Nova Poshta pickup points in shipping APIs are not ERP warehouses.

    Shipped vs backlog

    Shipped (hub P0): stock invariant, commitSaleForOrder, admin hub landing, stock/commissions depth, vendor ownership on restock.

    Admin actionsapp/_actions/admin-store-erp.tsInit stock, hold/release, dry-run, adjust
    Paid handlerslib/payments/conductor/handlers/store-order*.ts + credit/token routesCall commitSaleForOrder

    Invariant: store_products.stock === inventory_levels.available + inventory_levels.reserved · sellable = available.

    ProcessConductor owns TTL cleanup (cleanup-reservations) and settlement-payout cron — do not duplicate.

    Affiliate & Referral Enablement

    See-also: dual-rail referral — ERP ledger vs refcodes token rewards.

    /vendor/earnings
    Pending + history from settlements

    Typical scenarios

    1. Prevent oversell — Checkout reserves sellable units (available). A second checkout cannot take reserved stock.
    2. Paid order — PaymentConductor marks paid → stock commits once (idempotent) → settlement row appears for each vendor slice.
    3. Buyer cancels unpaid — Holds release; sellable returns. Refund after paid restores stock from sale movements (WayForPay Refunded/Voided wired).
    4. Payout day — Dry-run due settlements, then Process due payouts (simulated badge until on-chain mode is verified).

    Default warehouse label is zero-warehouse (store id 1). Nova Poshta pickup points in shipping APIs are not ERP warehouses.

    Shipped vs backlog

    Shipped (hub P0): stock invariant, commitSaleForOrder, admin hub landing, stock/commissions depth, vendor ownership on restock.

    Admin actionsapp/_actions/admin-store-erp.tsInit stock, hold/release, dry-run, adjust
    Paid handlerslib/payments/conductor/handlers/store-order*.ts + credit/token routesCall commitSaleForOrder

    Invariant: store_products.stock === inventory_levels.available + inventory_levels.reserved · sellable = available.

    ProcessConductor owns TTL cleanup (cleanup-reservations) and settlement-payout cron — do not duplicate.

    Affiliate & Referral Enablement

    See-also: dual-rail referral — ERP ledger vs refcodes token rewards.