Build//software // integrations

Your business software, connected and linked to ANAF.

The order comes in through the website, the invoice comes out of the invoicing program, the shipping label (AWB) comes from the courier and the e-Factura goes to SPV. We build the links between these programs so the data moves on its own and nobody has to copy it by hand. We work from Iași, with companies across Romania.

  • invoicing · online store
  • couriers · AWB
  • e-Factura · e-Transport

01Sound familiar?

Signs that your programs don't talk to each other

Each program does its job. The trip between them is made by someone in the office, with copy and paste, and that is where the mistakes happen.

Orders from the online store are typed into the invoicing program by hand
At the end of the month invoices are exported and entered again into accounting
Shipping labels are made on the courier's website, one at a time, with the address copied from the order
Marketplace stock doesn't match the warehouse and you sell products you no longer have
Someone logs into SPV every day to check whether invoices went through and what suppliers sent
A report takes three Excel exports and an afternoon of matching columns

02What we connect

The connections companies ask us for most often

We grouped them in pairs, the way they show up in a company. For each one we agree from the start which program holds the correct data, what happens when the other side doesn't respond and who gets the alert.

01
Invoicing and the online store
The order placed on the website reaches the invoicing program with the products, prices and customer details. The issued invoice goes back to the store, and stock stays the same in both places.
02
Invoicing and accounting
Issued and received invoices move into the accounting program through an export or a direct link. Anything that doesn't match, such as a customer without a tax ID, lands on a list to check instead of disappearing.
03
Orders and the courier
The shipping label is generated from the order, with the address and weight already filled in. The parcel status comes back automatically and the customer can receive the tracking link.
04
Marketplace, stock and invoicing
Marketplace orders, for example from eMAG Marketplace, enter the same flow as orders from your own store. The stock shown there comes from your inventory, so you don't sell the same product twice.
05
e-Factura (SPV)
The invoice goes to SPV straight from the application and its status shows next to it, together with the message from ANAF when it is rejected. Supplier invoices are downloaded from SPV automatically.
06
e-Transport
The UIT code is requested from the order or the delivery note, with the transport details already filled in, and stays attached to the document it came from.
07
SAF-T (D406)
The SAF-T file is generated from your application's data instead of being assembled by the accountant from several exports.
08
Company details from the tax ID
When you add a customer or supplier, the name and address are filled in from ANAF's public data, based on the tax ID (CUI).
09
Excel import and export
When the other program has no API, the link works through files: importing an Excel sheet with prices or stock, exporting in the format accounting asks for. The file is checked row by row before it is imported.

03Custom or ready-made

Sometimes a ready-made connector is enough

Many invoicing programs and online store platforms already have connectors between them. We tell you honestly when an existing one covers you and when a link built around your workflow is worth it.

A custom integration makes sense when

  • The existing connector doesn't cover your case: several warehouses, per-customer prices, products with variants
  • You have three or more programs that need to exchange data
  • You want to see what was synced, what failed and why
  • Your own application needs to connect to ANAF or to the courier

A ready-made connector is enough when

  • You use two programs that already have an official connector between them
  • Volumes are small and one sync a day is enough
  • You have no special rules for prices, stock or documents
  • In that case we help you set up the connector and check that the data comes out right

04 — Integrations

What every integration comes with

A link between programs works fine until the day a server doesn't respond. What happens then is what matters, so we build that part from the start.

  • Scheduled or event-driven sync (webhooks)
  • Automatic retry when one side doesn't respond
  • No duplicate documents on retry
  • A log for every transfer
  • Email alert when something fails
  • A list of items waiting for a person to check

Because we also do IT management, we look after the server the integration runs on, its backup and secure access.

05Budget

What an integration costs

Indicative budgets for typical integrations, at 260 lei per hour, excl. VAT. The final price comes out of the analysis and depends on how many programs are involved, what APIs they have and how many special cases turn up along the way.

Example Usually includes Estimated hours Estimated budget (excl. VAT)
Connecting two programs syncing orders, products, stock 20–60 5,200–15,600 lei
Courier integration shipping labels (AWB), tracking, statuses 25–70 6,500–18,200 lei
e-Factura integration in an existing application sending, statuses, errors 30–80 7,800–20,800 lei
e-Transport from orders UIT code from the order or delivery note 30–80 7,800–20,800 lei
AI · how we build

AI-accelerated development, led and checked by people.

Our developers work with AI assistants on the repetitive tasks: routine code, tests, documentation. Architecture, business logic and the final review stay with people. That way the project is finished in fewer hours, and you pay only for the hours worked.

  • Your code and data are not used to train AI models.
  • Every change is reviewed by a person before delivery.
All price examples

06How we work

From the first conversation to the app your team uses

  1. 01

    Discovery

    We map your real process, the documents involved and who does what. You get a clear scope and an estimate.

  2. 02

    Prototype

    A first working version within weeks, on your own data, so you can see it before committing further.

  3. 03

    Iterations

    We build module by module, with short feedback cycles. You decide the priorities.

  4. 04

    Launch & support

    Data migration, team training, go-live and maintenance. The source code is yours.

07FAQ

What companies ask us about integrations

For an estimate we need the names of the programs you use and what you want to move between them.

What do you need to estimate an integration?

Which programs you use, what data has to move from one to the other (orders, invoices, stock, prices) and how often. If the programs have an API, we read their documentation. If they don't, we look at what exports and imports they allow.

Our invoicing program has no API. Can anything be done?

Often yes, through files: a regular export on one side and a checked import on the other. It is less elegant than an API, but it saves the company from copying data by hand.

Can you add e-Factura to an application we already have?

Yes, if we have access to the application's code or its database. Sending invoices, tracking their status and downloading supplier invoices from SPV are added as a new module. The indicative budget is in the table above.

What happens if one of the programs changes its API?

The integration stops in a controlled way: failed transfers stay in the log, you get an alert and nothing is lost. We adapt it to the new version as part of maintenance or on request, billed by the hour.

Who owns the integration code?

You do, as with any application we build. The code is versioned and documented, and the API accounts and access keys stay in the company's name.

Tell us which programs you use and what should move between them

We get back to you within 24 hours with an approach and an indicative estimate.

Talk to us We reply within 24h