Most of what you would integrate, Cobalt ERP already is.
The best integration is the one you do not need.
An integration exists to make two systems agree. Cobalt ERP covers the operation on one core, so for most of the stack there is nothing to reconcile — and the connections that remain are the ones actually worth building.
Most of what you would integrate, Cobalt ERP already is.
An integration exists to make two systems agree. Cobalt ERP covers sales, purchasing, stock, warehouse, delivery, people and the ledger on one core, so for most of the stack there is nothing to reconcile and nothing to connect.
What is worth connecting, and what there is nothing to connect
Four things sit outside Cobalt ERP and are worth a real integration. Everything else is already one record, so there is nothing to synchronise and nothing to reconcile.
a real integration
a real integration
a real integration
4 integrations·each one deliberate
1 system·0 reconciliations
An integration you do not need is the best kind. Every arrow between two systems is a thing that can be late, wrong or silently stopped. Four of them are worth having; the rest were removed by putting the work on one record.
No sync between modules
A stock movement and its ledger posting are the same event, not two records kept in step by a nightly job.
Connect what stays outside
Your accountant's software, your bank, your storefront and your messaging stay where they are. Those are the connections worth building.
Open API and webhooks
REST for reads and writes, webhooks for events. Your data is reachable from whatever you already run.
Live connections, and what each one carries.
- Xero — invoices, credit notes and contacts exported in the shape Xero expects, so your accountant's workflow does not change. See accountant handoff.
- QuickBooks — the same handoff, in QuickBooks' own import format.
- Sage — CSV exports formatted for Sage import.
- WhatsApp — customers order through WhatsApp and the message becomes a real sales order. See WhatsApp ordering.
- CSV in and out — every record imports and exports as CSV, with the Setup Agent reading an import before it lands and flagging what looks wrong.
- REST API — read and write access to the same records the interface uses, under the same permission model.
- Webhooks — subscribe to order, stock and invoice events and push them wherever you need them.
Not an integration marketplace.
Cobalt ERP does not have hundreds of one-click connectors, and building a directory of them is not the plan. The connections above are the ones a small trading business actually needs, and the API is there for the rest.
If a specific system is a hard requirement for you, tell us which one before you commit rather than after. We would rather say no early than build a page implying otherwise.
Frequently asked questions.
Does Cobalt ERP replace Xero or QuickBooks?
It can, and for most teams it does not have to. From Growth up Cobalt ERP syncs the general ledger straight into Xero or QuickBooks over their APIs, so your accountant's workflow does not change and nobody re-keys anything. If you would rather run the books inside Cobalt ERP, the in-app ledger does that too — see Finance Core.
Is there an API?
Yes. A REST API with read and write access to the same records the interface uses, under the same permission model, plus webhooks for order, stock and invoice events.
Can I import my existing data?
Yes. Point the Setup Agent at a CSV export or a Sage backup and it works out what it is looking at, flags duplicates and prices with no currency, and shows you before anything lands. See AI onboarding.
Do you have a connector for [my system]?
Probably not as a one-click connector. Tell us which system and we will say plainly whether the API covers it, rather than putting a logo on a page.
Need a specific system connected?
Tell us which one before you commit. We would rather say no early than put a logo on a page.
Talk to us