Frequently asked questions

22 products: Core operations: PALBONSphere, PALBONTradeFinance, PALBONComply, PALBONGST, PALBONIbanking, PALBONShipping, PALBONLending; People: PALBONPeople, PALBONPayroll; Learning: PALBONCampus, PALBONLMS; Customers: PALBONGrowth, PALBONSupport, PALBONWhatsApp; Care: PALBONCare; Intelligence: PALBONInsights, PALBONJustice; Commerce: PALBONShop, PALBONPay; Platform services: PALBONComm, PALBONEkyc, PALBONPrint.

No. Start with the products you need today and switch others on later. They share the same sign-in and the same data, so nothing has to be migrated between them.

Start where the pressure is greatest: PALBONSphere if finance and stock come first, PALBONGrowth or PALBONSupport if customer-facing teams do. The others can follow in phases.

They read and write the same customers, items, employees and accounts. A won deal becomes a quotation, payroll posts to the ledger and an online order arrives as a sales order, without an export or an integration to build.

Yes. Each product covers its area end to end, so you are not buying a module that needs three others before it is useful.

PALBONCampus is built for schools, colleges and institutes, and PALBONCare for clinics and hospitals. For other kinds of organisation, the solutions page shows which products fit together.

On the infrastructure you choose: your own servers or a private cloud. The suite does not depend on outside services to run.

You do. It is stored in a standard open-source database on your infrastructure, and records can be exported to spreadsheets or read through the API whenever you want.

Yes. Fields, forms, print formats, workflows, reports and roles can all be configured without changing the core of the product.

Yes. Records can be imported from spreadsheets with the built-in import tool, or loaded through the API.

Yes. Each person chooses the language of their interface. The accounts handle several companies and currencies, and taxes and number and date formats are set to local conventions.

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.

Through roles. Permissions are set for each role and each type of document, down to individual fields, and a person can be limited to the records of one company, branch or customer.

Your administrator can switch on two-factor authentication and set a password policy for the whole installation.

Yes. Changes to a document are kept as a version history that shows who changed which value and when, and sign-ins and activity are logged.

The database and files are backed up on a schedule. The backups are ordinary files that you hold and can store wherever your own policy requires.

In phases. We agree the scope, show the products on your processes, set them up and load your data, train the people involved, and go live with one product or one team at a time.

That depends on the scope: how many products, how much data and how many teams. Because the rollout is phased, the first team can be working while later phases are still being prepared.

The products share one way of working, so what a person learns in one carries over to the others. Training for each role is part of the scope we agree with you.

Yes. Request a demo through the contact page and we will walk you through the products that fit, using examples from the way you work.

There is no fixed price list, because the price follows your scope: the products you use, the people who use them, where the suite runs and the services you want. Tell us your scope through the contact page and we will send a written proposal.

All products run on the same platform and sign-in, your data stays yours and can be exported, and no outside services are needed at run time. Setup, data migration, training and support are included to the extent you ask for them.

Which products interest you, roughly how many people will use them, where the suite should run and how much help you want with setup, data migration and training.

Yes. The rollout is phased, so you can start with one product or one team and extend the scope when you are ready.