One shared business core. Every application connected.
The Core OS comes with every OrbitWix account, before a single app is switched on.
It holds the structure of your business, the people in it, and the master data
every app depends on — so that data is entered once and used everywhere.
In a stack of separate tools, a single customer exists several times over — once in
the sales tool, once in the accounting system, once in a spreadsheet the dispatch
team keeps. Each copy drifts. The Core OS removes the copies.
Without a shared core
A customer is created three times, with three spellings of the name.
A credit limit agreed by finance is invisible to the person taking the order.
An item code means one thing in the warehouse and another on the invoice.
Every handover between teams is a re-entry, and every re-entry is a chance to be wrong.
Month-end starts with reconciling systems against each other.
With the Core OS
The customer is one record. Sales, dispatch and finance are looking at it.
The credit limit is on that record, so it applies wherever the customer is used.
An item has one code, one unit and one description across every app.
A handover passes a reference, not a retyped copy.
Reports are drawn from the records themselves, so they agree by construction.
Inside the Core OS
Everything the apps above it depend on.
Five groups. None of them is an app you activate — they are present from the first
day of the account.
Business structure
How your business is shaped, and what each record belongs to.
Organizations
Companies
Branches
Locations
Warehouses
People and access
Who can see and do what, decided once and honoured by every app.
Users
Teams
Roles
Permissions
Master data
The records every app reads from, held in one place rather than copied per tool.
Customers
Suppliers
Items
Process
How work moves and who has to agree before it does.
Workflow
Approvals
Business events
Notifications
Record and trust
What happened, when, and on whose authority.
Documents
Activity history
Audit
Configuration
And then the apps
Sales, purchase, inventory, warehouse, trade, dispatch, logistics, finance and the
rest are activated on top of all of the above — never beside it.
No. It is included with every OrbitWix account and is what the apps are activated on top of. There is no configuration in which a business has apps but no Core OS.
Can we run the Core OS on its own, before adding apps?
Yes, and it is a reasonable way to start. Getting companies, branches, users, roles, customers, suppliers and items right first means the first app you switch on has correct data to work with from day one.
How does master data get in to begin with?
Through import from your existing files or systems as part of implementation, and through integrations where a system stays in place. Cleaning up duplicates at that point is usually the most valuable part of the exercise.
We run several companies. Does that mean several accounts?
No. Organizations, companies and branches are built into the Core OS, so several companies live in one account with records, permissions and reporting scoped to each.
Who can see what?
Access is granted through roles and permissions held in the Core OS and scoped by company and branch. Because the definition sits below the apps, a role does not have to be re-granted in each one, and every change to a record is recorded in the audit trail.