Two systems that finally talk to each other
ERP and API integrations, built for you
We connect ERP, CRM, shop and accounting through interfaces (APIs). If a system has no usable one, there is often still a way.
Free intro callScope and timeframe depend on your project
An interface lets two programs exchange data (the shop and the inventory system, for example). Most lost time isn't inside the systems but between them. As long as everything goes smoothly, building an interface is usually manageable. The real work is in the details: which field means what, special characters, time zones, partial deliveries. And which system is right when two disagree. We prefer to settle these questions before any code is written.
- 01Connecting, for example, SAP, Dynamics, Odoo, DATEV, Salesforce, Shopware and in‑house software
- 02Settling which field goes where and which system wins in a conflict, ideally before any code is written
- 03Without an interface, often through the database, a file export or, as a last resort, a program that operates the screen like a person
- 04Syncing one way or both ways as needed, with a log if you want one
- 05Moving your old data across, usually with a trial run first
Connected to
- SAP
- Microsoft Dynamics
- Odoo
- DATEV
- Salesforce
- Shopware
- REST/GraphQL
- SFTP
How it runs
How it runs
A project like this usually runs in four steps.
01
Review the systems
Which interfaces exist, which fields are really there and which system is authoritative for what.
02
Agree the mapping
Field by field, with rules for conflicts and required fields. A lot depends on this step.
03
Build and test
Usually in a test environment, for example with real records and deliberately broken cases.
04
Switch over
Moving the data and, where possible, running old and new side by side for a while. We advise against switching everything over at once with no way back.
What this is not
So you know in advance what it isn't suited for.
- No interface against the vendor's will. If the licence terms forbid access, we decline.
- No cleaning up your data on the side. Duplicate master data, such as customers or products, has to be sorted out first.
- No real time where the source program can't provide it. Then the data is synced at intervals instead.
Common questions
Before you ask
Usually once it's clear what is to be built. That includes which other systems the solution has to work with and what we're assuming along the way. We work this out with you and write it down. That becomes the quote, and the quote states the price.
Usually it should move across to the new system. Moving old data is often underestimated in projects. So it pays to look at the old data early, clean it up together and test the move before switching over.
Interested in custom systems?
Drop us a line about what you need. We'll get back to you as soon as we can.
Reach us directlyinfo@tscodeworks.de
We'll get back to you as soon as we can