Skip to content
Balkan Tecnologia
AccessibilityGet in touch
Balkan Tecnologia

Orders, customers and stock the same in every system

We connect ERP, CRM, online store, marketplaces and internal systems so that orders, customers, products and stock flow on their own, with every failure logged and handled.

A mint-green thread passing through the brass eyelets of two stone blocks.

Who it's for

For companies where someone copies orders, records or stock from one system to another.

What it solves

  • An order comes in through the online store and someone types it all again into the ERP.
  • Stock on the website does not match the ERP, and products that are not there get sold.
  • The same customer is registered three times, with the CNPJ written in different ways.
  • When the integration fails overnight, someone only finds out from a customer complaint.

What we do

Integration map
Which systems exchange which data, in which direction, and which one is the source of truth.
Field mapping
Each field in one system linked to its match in the other, with written conversion rules.
Connectors
Integration by API, webhook, file or database, depending on what each system offers.
No duplicates
The same message received twice never creates two orders or two records.
Error queue
Whatever fails goes into a visible message queue, with the reason, and can be reprocessed.
Monitoring
An alert when an integration stops or falls behind, before it turns into a complaint.

What you get

  • An integration map and a field dictionary across the systems
  • Connectors in production, with automatic retries and no duplicates
  • A dashboard of failed messages, with an option to reprocess them
  • Alerts for stopped or delayed integrations
  • Documentation for your team to run each integration

How we do it

  1. Survey

    Systems involved, data exchanged, volumes and the access available.

  2. Data rules

    The source of truth for each piece of data and the conversion rules between systems.

  3. Development

    Connectors and error queue, tested with real anonymised data.

  4. Initial load

    Cleaning up existing records before synchronisation is switched on.

  5. Go-live and follow-up

    Integration switched on in stages, with the first days checked closely.

Technology examples

  • REST
  • SOAP
  • Webhooks
  • RabbitMQ
  • n8n
  • PostgreSQL

Related services

FAQ

Will it work with the ERP we use?

It depends on what the ERP offers: an API, a web service, files or database access. We check this during the survey, together with the ERP vendor when needed.

What if the ERP has no API?

There are still options, such as scheduled files or reading from an intermediate database. They are more fragile, so they come with more checks and alerts.

Should we use an off-the-shelf integration tool?

For simple flows, sometimes yes. When there are business rules, volume or many systems, custom code usually gives more control. We assess it case by case.

What about the tax document for the order?

When an order has to become a tax document, the tax integration joins the same flow. See the order-to-tax-document package.

Write to Balkan

Talk to us about your project