Core OS
Included with every account
Organizations, companies and branches. Users, roles and permissions. Customers, suppliers, items and warehouses. Entered once, used by everything above it.
Platform
The operating layer for your business.
Most businesses run on a stack of tools that were never designed to know about each other. OrbitWix replaces that with a single layer underneath everything: one Core OS, and the applications your business needs activated on top of it.
What the platform is
Seven parts, one platform.
Every OrbitWix account is built from the same seven parts. The Core OS is always there; the rest is what you choose to switch on.
Business Apps
Activate what you need
Sales, purchase, inventory, warehouse, trade, dispatch, logistics, finance, HR, projects, service, manufacturing and intelligence.
Workflows
Approvals and handoffs
A quotation becomes an order, an order becomes a dispatch, a dispatch becomes an invoice — with the approvals your business requires at each step.
Automation
Rules on business events
Reorder points, stock reservations, status changes and notifications run from the events the platform already emits, instead of someone remembering to check.
AI
On your own live records
Demand forecasting and replenishment suggestions that read the same stock, order and movement history your team works from — not a separate copy of it.
Integrations
Keep what already works
ERPNext, storefronts, payment gateways, shipping providers, WhatsApp and your own APIs connect into the same Core OS records.
Security
Roles, permissions and audit
Access is granted per role, per company and per branch, and every change to a record is written to an audit trail you can read back.
Architecture
Core OS first. Everything else sits on it.
The order matters. Because the shared foundation is in place before the first app is switched on, adding an app is a configuration change rather than a migration.
Four layers, top to bottom: intelligence and automation; the applications you activate; the workflow and integration layer; and the Core OS underneath all of them.
Intelligence — reads everything below
- Analytics
- AI forecasting
- Automation rules
Applications — activate what you need
- Sales
- Purchase
- Inventory
- Warehouse
- Trade
- Dispatch
- Logistics
- Finance
- and more
Workflow & integration — how the apps reach each other
- Approvals
- Business events
- Notifications
- External systems
Core OS — included with every account
- Organizations, companies and branches
- Users, teams, roles and permissions
- Central master data
- Documents and activity history
- Audit and configuration
Why a platform
What changes when the layer underneath is shared.
One customer record, not five
A customer created in sales is the same customer dispatch schedules against and finance invoices. Nothing is re-keyed at a handover.
Stock that reflects movement
A dispatch moves stock. A goods receipt moves stock. The number in inventory is the result of what actually happened, not a periodic reconciliation.
Permissions decided once
A role defined in the Core OS applies across every app that role touches, so access does not have to be re-granted per tool.
Growth without a migration
Adding trade, warehouse or logistics later means switching an app on against data that is already there — not starting a new implementation.
Reporting from one source
Operational and financial figures are drawn from the same records, so two reports of the same month do not disagree.
A trail on every change
Who changed a price, who approved an order, when a shipment status moved — kept by the platform rather than reconstructed from memory.
FAQ
Questions about the platform.
Is OrbitWix an ERP?
It covers what an ERP covers, but it is built the other way round. An ERP is usually one large product you configure down to fit. OrbitWix is a Core OS plus the applications you choose to activate, so a business can run on a small part of it and add the rest later.
Do we have to adopt the whole platform at once?
No. The usual path is the Core OS plus two or three apps that cover your most painful workflow, with the rest added once that is running. Because every app reads the same Core OS, adding one later does not mean re-entering data.
Can it run alongside systems we already use?
Yes. Integrations connect ERPNext, storefronts, payment gateways, shipping providers and your own APIs into the same records, so an existing system can stay in place while OrbitWix takes over the parts it does not cover.
How does the platform handle multiple companies and branches?
Organizations, companies and branches are Core OS concepts, not an add-on. Records, permissions and reporting are scoped to them from the start, so a second company or a new branch is a configuration change rather than a second installation.
Have a different question? Talk to us.
See the platform against your own workflow.
Bring a process that currently spans three tools. We will walk through how it runs on one.