In many operations, the ERP is the source of truth — and also the source of rework. The same invoice is entered in SAP or TOTVS, then re-keyed into the TMS to generate the pickup, checked again in the WMS during picking, and even exported to a spreadsheet to close the books. Every handoff is a chance for error: a swapped CFOP, a wrong weight on the manifest, an order that vanished between the e-commerce platform and the warehouse.
Meta Dados connects the ERP (SAP, TOTVS, Sankhya, Omie) to the rest of your operation so that inventory, finance, orders and NF-e stay synchronized in real time. No re-keying, no spreadsheet in the middle. Data is born in one place and flows — auditable — to every system that needs it.
The cost of typing the same invoice twice
Re-keying isn't just slow. It's the discrepancy that surfaces at month-end close, when the WMS inventory doesn't match the ERP. It's the freight billed wrong because the weight in the TMS came from a manual entry. It's the invoice issued twice because two departments didn't know the other had already billed it.
When the ERP talks directly to the TMS, WMS and sales channels, that invisible cost disappears:
- No more re-keying — the order is entered once and moves through billing, shipping and finance without being retyped.
- Single source of inventory — the WMS write-down is reflected in the ERP and the e-commerce platform at the same instant, preventing overselling.
- Automatic reconciliation — NF-e, CT-e and invoice are matched by access key, not by manual checking.
- Traceability — every record carries where it came from and when it arrived. Auditing stops being a treasure hunt.
Which data syncs between the ERP and the other systems
The integration is organized by module. You decide which ones go into the project — almost always starting with the ones that hurt the most.
- Inventory — balances, reservations, warehouse positions and movements between ERP and WMS. Inbound, outbound and stock counts matching across systems.
- Finance — accounts payable and receivable, write-downs, bank reconciliation and cost centers. The freight completed in the TMS becomes a posting in the ERP with no data entry.
- Billing / NF-e — issuance, SEFAZ response, cancellation and correction letter. The invoice issued in the ERP feeds shipping and transportation automatically.
- Orders — orders from e-commerce (VTEX, Shopify) and B2B land in the ERP already validated, with correct customer records, pricing and taxation. Status flows back to the channel without anyone updating a spreadsheet.
Every field is mapped one-to-one across systems: the SAP CFOP that corresponds to the operation type in the TMS, the TOTVS product code that matches the Shopify SKU. That mapping is where the integration becomes reliable — and it's exactly the work Meta Dados does in the assessment.
How we connect: API, EDI or middleware
There is no single right method. There's the right method for each pair of systems. We choose based on the technical reality of your environment, not on preference.
- API (REST/SOAP) — the preferred path when systems expose modern interfaces. SAP (BAPI, OData, RFC), TOTVS (Protheus/Datasul APIs), Sankhya, Omie, VTEX and Shopify have mature APIs. Real-time exchange, with delivery confirmation.
- EDI — for structured flows with carriers, customers and large retailers that work by file (NF-e/CT-e in XML, orders in a fixed layout). Where EDI is the partner's standard, we integrate to it.
- Middleware — an integration layer between systems that translates formats, applies the mapping rules, controls the queue, retries what failed and logs everything. It's what keeps one system going down from taking the other with it.
Middleware is what makes the integration resilient: if SEFAZ goes down or the e-commerce platform slows, messages stay in the queue and are reprocessed — nothing is lost, nothing brings the whole operation to a halt.
Systems we integrate
Meta Dados specializes in transportation and logistics, but the integration engineering serves any operation. We work with:
- ERP: SAP (ECC and S/4HANA), TOTVS (Protheus, Datasul, RM), Sankhya and Omie.
- TMS / WMS: RODOPAR and the market's leading transportation and warehouse management systems.
- E-commerce: VTEX, Shopify and marketplaces.
- Telemetry: SASCAR, Autotrac, Omnilink, Onixsat, Cobli and Geotab, when transportation enters the same flow.
More than 50 systems have already gone through our integrations. When the system isn't one of the common ones, we map the interface it does have — database, file or legacy API — and integrate it just the same.
What the project looks like, from assessment to real time
Integration isn't an off-the-shelf product; it's engineering built around your operation. But the path is predictable:
- Assessment (48h, free) — we map the systems, the data flows and where the re-keying is. You receive the integration design and an honest effort estimate.
- One-to-one mapping — we define which fields sync, with which rules, and how to handle the rare cases (returns, cancellations, discrepancies).
- Build and validation — we integrate in a test environment, validate with real data, and only then go to production.
- Go-live and monitoring — synchronization goes live with alerts. If something fails, you know before the customer does.
For point integrations — an e-commerce platform connecting to the ERP, for example — a timeline of a few weeks is typical. Projects with several SAP or TOTVS modules are phased, precisely so the operation never stops. The assessment is what turns that timeline from a guess into a commitment.
Frequently asked questions
Do I need to halt operations to integrate SAP or TOTVS?
No. The integration is built and tested in a staging environment, with real data, before any go-live. When it moves to production, synchronization is switched on in phases — one module at a time — so that nothing in the operation stalls during the transition.
How long does an integration between the ERP and a TMS or e-commerce take?
It depends on the number of modules and the complexity of the tax rules. A point integration, such as a VTEX or Shopify store connecting to the ERP, is usually ready in a few weeks. Projects with several SAP or TOTVS modules are phased. The free 48h assessment turns that estimate into a concrete timeline for your case.
Which data stays synchronized between the systems?
Inventory (balances, reservations and movements), finance (accounts payable and receivable, write-downs, reconciliation), billing and NF-e (issuance, SEFAZ response, cancellation) and orders (e-commerce and B2B with customer records, pricing and taxation). You choose which modules go in; almost always starting with the ones that generate the most rework.
Is the integration real time or batch?
Whenever the systems allow it, the exchange is real time, with delivery confirmation via API. When the partner only works by file — a common case of EDI with carriers and large retailers — we use batches in frequent windows. The middleware controls the queue and reprocesses what fails, so nothing is lost in either scenario.
Does it work with SAP S/4HANA and TOTVS Protheus?
Yes. We integrate SAP in the ECC and S/4HANA versions (via BAPI, OData and RFC) and TOTVS Protheus, Datasul and RM (via their APIs). We also work with Sankhya and Omie. When the ERP is an older version without a modern API, we integrate through whatever interface is available — database, file or legacy service.
What is EDI and when is it needed instead of an API?
EDI is the exchange of documents in a structured, standardized format — NF-e and CT-e in XML, orders in a fixed layout — widely used between companies, carriers and large retailers. We use EDI when the partner requires that standard. For integration between your own systems, an API is usually better because it's real time. Meta Dados works with both and chooses based on what each connection calls for.