Flow map
One diagram showing which data moves from which system to which, how often, and who currently retypes it. It frequently reveals for the first time how much effort goes into copying.
Service · Custom software
Systems integration
A plastic moulding firm in Velenje supplies car plants in Germany and across Europe. Customers transmit delivery schedules by EDI, yet each morning somebody prints them and retypes them into Pantheon. Works orders travel to the presses on spreadsheets, quality readings sit in a separate database, and at dispatch the same details are keyed in yet again for the delivery note and the e-invoice. Every retyping costs time and invites mistakes. A wrong digit in a part number surfaces only when the customer's assembly line runs short, at which point the cost is no longer minutes but penalties. For us, systems integration means a fact is captured once, at its source, and finds its own way to wherever it is needed. First we agree which system owns which data; then we make each link visible, repeatable and written down. The work is remote, with shop-floor staff helping via screen sharing and brief calls.
EDI
EDIFACT and VDA with customers
E-invoices
eSLOG 2.0 via your exchange provider
Queue
nothing lost during an outage
Alerts
the responsible person sees failures
Scope of the service
From links nobody remembers building to a data flow with an owner, monitoring and documentation.
Single source of truth
For items, partners, price lists, orders, stock and bills of materials, one system is declared owner. The rest read that data but may not alter it.
An integration layer with a log
Instead of a web of point-to-point links, a single layer using n8n, Azure Logic Apps or a small bespoke service. Every transfer is logged, failures retry and alerts go to one address.
ERP on one side
Pantheon, Minimax, Metakocka, SAOP, SAP Business One, Microsoft Dynamics 365 Business Central or Odoo, connected via API, database views or file exchange.
Customers and suppliers on the other
Delivery schedules and despatch advice over EDI, eSLOG 2.0 e-invoices through the exchange provider you picked, and whatever formats overseas customers require.
Shop floor and warehouse
Quantities from machines or a MES, stock movements and quality readings flowing into the ERP automatically and regularly.
Interfaces on paper
Each interface is versioned and described, and every change goes to a test environment first. When a partner alters a format, you see at once what is affected.
How the work runs
We begin with the link that involves the most retyping or the greatest risk. Each step pays off on its own.
01
Drawing the map
Conversations with the people involved, a look at every existing connection, a named owner per data type and a red, amber or green rating for each link.
02
Choosing the order
We agree with management which connection is tackled first and on what platform.
03
Changing over gently
A connection is proven against a copy of live data, then old and new run side by side until the figures agree.
04
Keeping watch
A dashboard, alerting, a short monthly review and updates whenever a customer or supplier changes their format.
Every link needs a named human owner. When a connection fails, it must be obvious who receives the alert and who decides what happens next. If the answer is “IT” or “the ERP vendor”, in practice nobody responds. For each link we record a person on your side and one on ours, together with what each of them does.
Your questions answered
Far from it. The most fragile or most laborious connection goes first, and everything else carries on as today until it is scheduled.
Not at all. SQL views, scheduled CSV or XML drops and utilities supplied by the ERP maker all work. These routes tend to break when the ERP is upgraded, so we watch them harder and give each its own write-up.
If you have a support agreement with us, we do. The dashboard tells us whether the fault is ours, the ERP's or the partner's, and we chase whichever party needs to act.
We are not an exchange provider for e-invoices and do not intend to be. We wire your ERP to the provider you have contracted, so invoices leave without anyone retyping them and delivery status comes back automatically. Your agreement with that provider is unaffected.
A handful of standard connections are cheaper to build in n8n or similar. Heavy transformations, large message volumes or strict timing call for a lean custom service instead. The flow map usually makes the answer obvious.
More services in this area
Service
From idea to product
A rough concept turned into a tool people genuinely use, with each step checked against a figure you can measure
Service
Mobile apps
iOS and Android apps designed for the forest track, the loading bay and the customer, not for the boardroom
Service
Open source development
Open source solutions with no per-seat licences, chosen carefully, kept patched and always with a way out
Service
Dedicated developer teams
Remote engineers who keep your rhythm, use your tools and work on your product and nothing else
Let us tidy up your data flows
List the software you rely on and the places where someone copies figures from one screen to another. Our reply will name a sensible first connection.
When we work
Weekdays 9:00-17:00 CET, answers the same or next working day
Weekdays 9:00-17:00 CET, answers the same or next working day
Calls
Video meetings, Teams and Meet both welcome
Video meetings, Teams and Meet both welcome
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
- Questions first. If something is missing before we can estimate, we email you or set up a brief video chat.
- A written quote. It spells out the work, a euro figure excluding VAT and a sensible start date. No fine print, no surprise line items down the road.
- You choose. It lands in your mailbox. Read it at your own pace, query anything that seems vague, and only then make up your mind.