Skip to content
PALBON-SuitesComplete ERP Solution

Platform

The platform under every product

Every product stands on one foundation: the same sign-in, data model, permissions, automation and reporting, running on infrastructure you control.

Foundation

Six things every product shares

The products were not joined together afterwards. They are built on the same platform, so what is true of one is true of all of them.

One sign-in, one set of roles

A person has one account for every product. Roles decide what they can see and do, and a change of role takes effect everywhere at once.

One shared data model

Customers, items, employees and accounts are defined once. Every product reads and writes the same records, so there is nothing to synchronise.

Automation built in

Approval workflows, assignment rules, notifications and scheduled jobs are set up on screen, and work the same way in every product.

Reporting on live data

A report builder, dashboards and print formats work on the records your teams are using right now, not on an overnight copy.

Open to integrate

A REST API and webhooks connect the suite to your other systems, and records can be imported from and exported to spreadsheets.

Adaptable without code

Add fields, rearrange forms and design print formats on screen. Where a rule needs logic, a short script attaches to the form and the product itself stays untouched.

Security and control

People see what their role allows, and every change leaves a trace

Access is decided in one place for the whole suite. Your administrator sets who can read, write, approve or export, and the platform keeps the record of what was done.

  • Role-based permissions, down to the individual field
  • Limits for each person on the records they can open, such as one company or one branch
  • Two-factor authentication at sign-in
  • A password policy that you set

Kept on record

  • Version historyChanges to a document are kept with who made them and when.
  • Activity logsSign-ins and activity are logged, so there is a trail to review.
  • Scheduled backupsThe database and files are backed up on a schedule.

Deployment

Runs where you decide, and stays under your control

PALBON-Suites is installed for your organisation. You choose the infrastructure, and the suite does not reach outside it to do its work.

  • Nothing is fetched from outside services at run time
  • Built on a standard open-source database that your own team can inspect
  • Backups are ordinary files that you hold and can restore elsewhere
  • Your data stays on your infrastructure and can be exported whenever you want it

Where it can run

  • Your own serversIn your server room or data centre, looked after by your own team.
  • A private cloudOn cloud infrastructure that you rent and control.
  • A closed networkWhere there is no internet connection at all, the suite keeps working.

International

Made for many countries and companies

One installation can serve a group that works across borders, in the language and conventions of each place.

Work in your language

The interface is available in many languages, and each person chooses their own without affecting anyone else.

Several companies and currencies

Keep separate books for each company in one installation, and buy, sell and report in more than one currency.

Local taxes and formats

Taxes are configured rather than built in, and numbers, dates and time zones follow the conventions you set.

FAQ

Questions about the platform

Is the platform really the same for every product?

Yes. Sign-in, permissions, workflows, reports and print formats work the same way in every product, so a new product is never a new system to learn.

Does the suite need an internet connection?

No. Everything it needs at run time is served from your own installation, so it works on a closed network. Connections you choose to add, such as email or a telephony provider for PALBONComm, use the network access you give them.

Do our changes survive a product update?

Custom fields, form layouts, workflows and print formats are stored as configuration, separate from the product itself, so they stay in place when the product is updated.

How do other systems connect to the suite?

Through a REST API that reads and writes records, webhooks that tell another system when something changes, and the import and export of spreadsheets.

Products

Every product on this platform

They share one sign-in, one database and one set of permissions.

See the platform at work on your own processes

Tell us how you work today. We will walk you through the products that fit, on your data and your terms.