Platform
A back office for every organization
Each customer organization gets its own ERP instance, built on Moqui and MarbleERP, with its own database. Accounting runs in the pilot; more modules are on the roadmap.
What does each organization's back office include today?
Its own ERP instance
Every customer organization's workspace runs its own ERP instance, built on Moqui and MarbleERP. No ERP is shared between organizations.
Its own database
Every customer organization's workspace has its own PostgreSQL database cluster. No database is shared between organizations.
Accounting (Beta)
The ERP back office includes accounting, in use in the pilot. (Beta)
How do a client's staff sign in?
Each workspace has its own web address under syncedoffice.com, where its users sign in.
Workspace users sign in to their ERP with single sign-on (OpenID Connect). (Beta) Every customer organization's workspace has its own sign-in realm, so its users and roles are kept apart from every other organization's.
Roles (admin, member, viewer) come from the sign-in realm and are refreshed at every sign-in. (Beta)
Next
What is coming to the back office?
- Orders, inventory, purchasing and invoicing, verified for pilot workspaces. (Roadmap)
- Scheduled backups of every workspace, with restores that are tested. (Roadmap)
- A CRM for leads, contacts and deals inside each workspace. (Roadmap)
- Workflow automation across each workspace's back office and website. (Roadmap)
Moqui and MarbleERP are open source (CC0-1.0, with a patent grant), so the ERP itself is not locked to us. How each organization is kept apart
Questions and answers
Which ERP does SyncedOffice run?
MarbleERP on the Moqui Framework 4.0.0, both open-source projects. Each customer organization's workspace runs its own instance.
Which parts of the ERP can a pilot client use?
Sign-in, the dashboard and accounting have been checked in the pilot. (Beta) Orders, inventory, purchasing and invoicing ship with MarbleERP but have not been checked for a workspace yet, so we do not list them as available. (Roadmap)
Why not one ERP shared by every customer?
A shared ERP keeps every customer's records in the same tables and depends on software filters to keep them apart. A separate instance with its own database removes that dependency: there is nothing shared to filter.
Can I import my existing data?
During the pilot we plan each move with you, starting from the spreadsheets or exports you have today. There is no self-service import tool yet.