A programmed interface between your systems, accepted with test cases and documented. If you wish, we monitor and look after it afterwards.
Services
Two systems, one workflow: we build the interface.
Shop and inventory management, ERP and accounting, a supplier using EDIFACT or a portal that only speaks CSV: when two systems need to exchange data, we connect them. REST, XML, EDIFACT, WebEDI, SFTP or file import, we build the interface so that it fits your workflow and holds up in daily operation.
The first conversation is free and without obligation. We get back to you within one working day.
Your offer at a glance
The systems involved, one real case from input to result, and contacts from the business side and IT.
Clearly described sections at a fixed price, open topics by effort within an agreed frame.
After the free first conversation you receive a written offer. For larger projects we clarify the requirements beforehand in a paid workshop.
Which systems we connect
Shop and inventory management
Orders arrive in the ERP, stock and prices in the shop. We map articles, variants and customer conditions unambiguously.
Suppliers and trading partners
Orders and order responses via EDIFACT, through WebEDI portals or as files via SFTP, with a status per message.
Accounting and invoices
Without retyping, documents, payments and XML e-invoices move between business software and accounting.
Shipping and logistics
Register shipments with the carrier and return tracking numbers to the shop and your customers.
Business applications and your own APIs
For your applications we develop REST APIs, documented with OpenAPI, or extend existing interfaces.
Files and legacy systems
Where no API exists, we use export and import functions, approved database access or file formats such as CSV and XML.
Formats and transfer paths
Web APIs for applications, shops and portals, secured with separate credentials per connection.
Classic ERP and industry interfaces. Where a schema exists, we validate every message against it.
ORDERS, ORDRSP and further messages with your trading partners, also through their portals.
Scheduled exports and imports via SFTP or network share, every file checked before it is taken over.
Transfers start as soon as something changes and are retried after a fault.
You name the counterpart. We read the documentation and tell you beforehand what is possible.
How we proceed
You describe one real case: source, target and how you recognise that it is complete from a business point of view.
We define which system owns which data, what the fields mean and how current the transfer has to be.
We then build the interface and test it with real data and with deliberately faulty data.
At go-live the workflow is accepted. Your staff see errors where they are handled, and if you wish we keep looking after the connection.
What you can rely on
You decide which system holds the original data. Together we define which details flow in which direction.
A call only starts once the new state has been saved, and is retried if there is a fault. You can see failed transfers and repeat them selectively.
Unique case identifiers and checks of the processing state protect against duplicate orders, even if a connection drops. How far this goes also depends on the systems involved.
Each connection gets its own credentials with narrowly defined rights. Confidential data stays out of error messages and logs.
If you wish, we keep looking after the interface: if a vendor changes its API, we adapt it, test it and roll out the new version.
Frequently asked questions
What is the difference between an API, an interface and an integration?
An interface defines how software communicates. An API is an interface with defined calls. An integration connects systems so that they form a working business process.
Is it enough if both systems have an API?
No. Two existing APIs are a good starting point, but not a finished connection. Terms, mandatory fields and states still have to be mapped.
Does an interface always have to work in real time?
No. Real time pays off when a delay immediately causes wrong decisions. For product catalogues or nightly billing runs a scheduled job is often more robust.
Which system should lead?
That is decided per type of data. The ERP can own the customer master, the shop the baskets. No single system has to be the source for everything.
Who monitors the interface and handles errors?
Technical monitoring checks availability and error rates, business monitoring whether orders reach their status. Who takes on what is set out in the operations contract.
What does an interface cost?
That depends on the systems and the workflow. Clearly described sections are offered at a fixed price, open topics are billed by effort within an agreed frame. You receive a written offer beforehand.
Which systems should work together in your company?
Tell us which programs are involved and name one case that is transferred by hand today. We get back to you within one working day and arrange a free first conversation.