Integrations and API
Set up around the accounting, webshop and terminal you already have.
Your accountant stays in Fortnox or Visma, your webshop stays on WooCommerce, and the card terminal on your counter can stay too. Karo sends each of them what it needs, and when a system you rely on isn't connected yet, you ask and hear back within days.
Verification D214Close the day, and the books have it.
When you close the day, Karo posts the sales to Fortnox or Visma as one verification, split by VAT rate and by how they were paid. Your accountant stops retyping Z reports.
Not Fortnox or Visma? Karo connects to the accounting system or ERP you use, on request.
Ask for the one you don't see.
Ask for a system Karo doesn't connect to yet and you'll hear back within days: it's built, it's on the plan, or it's a no, and you'll know why. One store needed their WordPress site and WooCommerce shop connected; it was connected within the week, before they'd signed.
For your developer, an open API.
Your developer gets keys, the full spec in the open, and webhooks that fire when something happens in Karo: a sale, a refund, a change in stock. Sign-in for other apps through OAuth comes next.
POST https://your-system.example/karo{ "event": "sale.completed", "receipt": 4219, "amount": 1825.88, "currency": "SEK", "store": "Södermalm", "till": "Till 1", "at": "2026-09-26T14:12:03+02:00"}
Already connected
Connection questions.
No. We make the accounting, webshop and terminal connections with you. The API is for the systems you or your developer build yourselves.
WooCommerce, through Karo for WooCommerce. If yours runs on something else, ask.
Bring the list of systems you use.
Tell us what runs your business today, down to your accountant's software, and in the demo you'll see how each one connects, or when it will.