Platform usage
The platform is provided for workflows such as POS, inventory, CRM, procurement, expenses, HR foundations, fleet, reporting, tenant websites, support, subscriptions, and operational management.
Use FAREXA ERP responsibly for legitimate business operations, tenant administration, sales, inventory, CRM, reporting, and related SaaS ERP workflows.
These terms describe general public website and platform usage expectations. Commercial agreements, support packages, implementation scopes, and subscription orders may add more specific terms.
The platform is provided for workflows such as POS, inventory, CRM, procurement, expenses, HR foundations, fleet, reporting, tenant websites, support, subscriptions, and operational management.
Access may depend on subscription plan, enabled modules, users, branches, limits, trial status, billing cycle, support level, and implementation agreement. Plans and feature availability may change over time.
Tenants are responsible for their business data, user access decisions, tax settings, invoices, customer communication, uploaded documents, integrations, and compliance with applicable laws.
Tenant administrators should maintain accurate company settings, assign permissions carefully, remove inactive users, protect credentials, review reports, and validate financial or tax outputs before use.
Users must not misuse the platform, attempt unauthorized access, interfere with tenant isolation, upload harmful content, bypass permissions, overload services, or use the ERP for unlawful activity.
Platform availability, maintenance, support response times, custom modules, integrations, migration, training, and release timing may be governed by separate commercial or service agreements.
Connected services such as payment gateways, messaging, email, analytics, hosting, or APIs may have separate terms. Tenants are responsible for credentials and configuration choices for their integrations.
To the maximum extent permitted by law, platform liability may be limited for indirect losses, data entered incorrectly by users, configuration mistakes, third-party service failures, or unsupported custom usage.