Platform Overview

Business modules and shared context

CRM, sales, purchasing, inventory, manufacturing, HR and finance each provide their own working records. Company, branch, location, party, item and date context help teams interpret the related activity. Optional extensions address additional documented needs when enabled.

Cross-functional capabilities

Reporting and inquiries support visibility. Documents manage controlled revisions. Approval functions support authorized review, and AI tools provide contextual assistance. Each capability retains its own permission and processing boundaries.

Configuration and connections

Administrative roles maintain the relevant settings, including authorized integration configuration. APIs, webhooks, communication and external service workflows require deployment review. This overview describes the business architecture without publishing internal implementation routes.

Is SERP web-based?

Yes. The documented workflow begins by opening the SERP address in a web browser and signing in with an authorized account. Menus and functions depend on the company, role and enabled modules.

Browser access and hosting are different decisions

Browser access does not by itself establish a managed cloud service, native mobile application or offline operation. Confirm the hosting arrangement, supported browsers/devices, connectivity and service responsibilities in the deployment discussion.

Company, branch and currency context

SERP documents company switching for authorized users, branch and location context, currencies and exchange rates. Check those settings together with the intended reports. Explore company and currency controls.

External systems and configuration

APIs, webhooks, communication providers and AI services require defined mappings, credentials and scope. Review integration families and verify the intended exchange before committing to a connector or deployment architecture.