How to integrate Saga with an OMS/WMS without changing anything for your accountant
Saga C and Saga Soft are the top choices for accounting firms in Romania. Here is how to add modern operations (OMS, WMS, B2B portal) on top of Saga without touching a single accounting setting.
Mihai Istrati — CTO Azuvio · 2026-05-02 · 8 min · ERP & Integrations
Saga — the software your external accountant uses
Over 60% of Romanian SMEs work with an external accounting firm that uses Saga C or Saga Soft. It is affordable, stable, and it is what the accountant knows best. The problem arises when your business grows: you sell on eMAG, you have a warehouse with picking, you have distributors requesting a B2B portal — yet Saga is built for accounting, not for operations.
Why "replacing Saga" is the wrong answer
Your external accountant works with 30-50 companies on Saga. They will not change their software for you. If you force a migration to another ERP, you change the accountant — and that means 3-6 months of fiscal chaos (D394, SAF-T, unreconciled balances). The real cost: €15k-40k, plus fiscal risk.
The correct doctrine: Smart Operations Layer over Saga
You add Azuvio over Saga as an operational layer:
The OMS receives orders from eMAG, Shopify, the B2B portal, and field agents — all in one place
The WMS runs picking with scanners in the warehouse
The B2B Portal provides self-service for distributors
Saga receives a daily XML/CSV export with invoices, payments, and NIRs (reception notes) — exactly in the format the accountant currently imports manually from other programs
File exchange: technical realism
Saga does not have a real-time API. It uses file import/export (XML, CSV, TXT). Azuvio respects this reality: we don't invent what doesn't exist. We generate standardized files at a configurable frequency (daily, weekly), and the accountant imports them in one click. See also the D394 glossary and SAF-T D406.
Tangible benefits
The accountant changes nothing — Saga remains, balances remain, statutory reporting remains
Operations run modernly — automated orders, live stock, measured OTIF
Zero re-keying — invoices generated in Azuvio arrive fully structured in Saga
D394 and SAF-T pre-filled — exports have the exact fiscal format required by ANAF (the Romanian tax authority)
What implementation looks like
Typical setup: 2-4 weeks. Week 1: mapping accounting codes ↔ Azuvio products. Week 2: XML export configuration + test with the accountant. Week 3: progressive go-live across channels. Week 4: operational team training.
Conclusion
Saga is the fiscal backbone — Azuvio is the operational backbone. This combination allows you to scale without breaking the relationship with your accounting firm. See also the Saga connector or the OMS pillar.