Terms of Service
Last updated: June 17, 2026
1. Multi-Tenant Business Profiles
By registering on VextoApp, you initialize a unique isolated tenant profile mapped to your `business` records. All child data allocations, layout metadata, and location parameters remain strictly bound to your specific commercial entity context.
2. Licensing Limits & Subscriptions
System operational capabilities scale under a prepaid framework mapped to active `subscriptions` and `plan` records. Exceeding allowed row entry limits (such as active `branch` entries or product storage boundaries) triggers an automated validation requirement to upgrade via explicit gateway procedures.
3. Role Provisioning & User Accountability
The root administrator maintains strict control over deploying `user` accounts, mapping specific `user_type` levels, and defining advanced object access permissions using custom JSON parameters. You assume total responsibility for mutations performed by credentials linked to your tenant instance.
4. Product Catalog Integrity
When appending components to your main `product` catalog schema, rows must map securely to existing `brand`, `category`, and active `status` configurations. Pricing definitions (cost_price and selling_price) must be maintained properly to ensure valid calculations across downstream POS environments.
5. Real-Time Multi-Branch Stock Logs
Inventory values across multiple warehouses are synchronized using isolated `branch_stock` datasets. Stock transfers, batch changes, or real-time location balances must occur through verified workspace pipelines to avoid stock count discrepancies.
6. Supplier Procurement & Purchase Workflows
Managing inventory restocking processes requires binding records to verified commercial `supplier` logs. Every structural intake sequence must generate an immutable `purchase` envelope containing detailed `purchase_item` objects and an accurate transaction reason code.
7. Invoice Processing & Sales Data
Point-of-sale actions auto-generate secure ledger entries compiling specific `invoice` headers alongside relational `invoice_item` rows. Transactions link immediately to localized `customer` profiles, producing finalized records that serve as unalterable financial historical logs.
8. Payment Integration & Receipt Archival
All client transactions must resolve against specific methods audited by standard `payment_method` reference rows. Finalized checkouts process an automatic relational database lock, generating a unique alphanumeric `receipt_no` index string for long-term audit verification.
If you encounter unexpected schema errors or require specific legal clarity regarding multi-branch data synchronization rules, please submit technical assistance tickets directly to billing@vextoapp.com.