Platform
PERSO One Platform: the shared backbone of the products.
The same platform runs underneath every PERSO product. This page describes the shared capabilities every customer has, independent of products.
What is PERSO One Platform?
PERSO One Platform is the platform layer that lets PERSO HR, CRM, Field Sales, POS, Construction, Installation, Procurement, AMS and Finance share one user, permission and company/branch infrastructure. Notifications, tasks, the report centre and shared master data (personnel, business parties, catalog, physical assets) live in this layer; it is not a product itself. WMS, IoT, Vision and Smart Expense are positioned in the ecosystem as separate products; their integration with the platform is assessed per project.
Platform architecture
Platform architecture
Platform, products, capabilities and features are four distinct layers. Which products and capabilities are enabled is settled during the quote process according to your needs; the platform is set up once underneath all of them.
- 1
PERSO One Platform
User, permission, company/branch, notification, task, reporting and master-data services.
- 2
Products
A thirteen-product ecosystem: nine run on PERSO One Platform; WMS, IoT, Vision and Smart Expense are positioned as separate products. Each product’s scope is settled according to your needs.
- 3
Capabilities
The business areas inside a product (e.g. assets, maintenance, service in AMS).
- 4
Features
The individual screens and actions that make up a capability.
Why One Platform?
Nine platform products, one shared backbone.
PERSO products are scoped to your business needs; the products, capabilities and commercial package structure are settled during the quote process. The nine platform products work together on the same PERSO One Platform; WMS, IoT, Vision and Smart Expense are separate ecosystem products included in scope on request.
PERSO One Platform
One user experience
One sign-in, a product launcher and switching between products; every product speaks the same interface language.
Company / branch structure
The multi-company and multi-branch model is the shared scope of all products.
Users and roles
Users, roles and permissions are defined on the platform; products inherit them.
Tenant isolation
Each company’s data stays within its own scope; access is checked at company and branch boundaries.
Notifications and tasks
Approvals, tasks and notifications flow through a shared infrastructure.
Shared master data
Personnel, business-party (customer/supplier), catalog and physical-asset records are kept in one place.
Report centre and data transfer
Reports, exports and import tools are offered at the platform level.
Web and mobile
Management in the web app, field and employee experience in the mobile app.
Integration approach
Integration approach
Links between products are built on shared master data and the shared user model. Product pages state the difference between “used together” and “transfers data automatically”; an integration that does not exist in code is not promised here either.
Mobile
Field and employee experience in your pocket.
The PERSO mobile app covers employee self-service, field sales visits, construction and installation field records and field service work orders. We do not claim full mobile parity for every web product; each product page states exactly what it offers on mobile.
Shifts, QR attendance, leave and advance requests, payslips, targets and commissions, documents, contracts, benefits and assigned assets live in the employee mobile app.
Visits, route tracking, order and collection entry live in the rep’s mobile app; field users can sign in without an HR personnel profile.
Field records, photo-backed daily entries and weather records live on the construction mobile screen.
Site summary, progress, attendance, quality, NCR, punch, equipment, custody and acceptance screens live in the crew’s mobile app, with offline support.
Field service work orders, NFC/QR asset verification and location capture live in the technician’s mobile app, with offline support.
Platform & Security
Permission, scope and trail: the same discipline in every product.
Role-based permissions, company/branch scope, tenant isolation and the audit trail are defined at the platform layer; every product inherits them.
- Role-based authorisation
- Company, branch and site scope
- Tenant isolation
- Audit trail
- Sensitive-field masking
- Secure password reset
- Location-aware QR
- Supplier portal token security
PERSO One Platform
Let’s shape PERSO around your business, together.
Let’s clarify which products to start with, your branch structure and your field teams, and build a demo plan.