Vuola takes technical ownership of your B2B integration: we specify the flows, decide the messages, review and validate the mappings, and coordinate the team that builds them, whether that team is yours or your vendor's. The overall plan and the budget stay with you.
One partner and one message type is a task. Forty partners across six countries, three message formats, two ERPs and an EDI vendor who only answers what you ask is something else: a system nobody owns end to end. That is where we come in, and it is what we mean by complex ecosystems.
Complex supply chains · Manufacturers · Retailers · Logistics providers
A trading partner, a parent company or a transition agreement sets the date. You have to meet it with whatever you have in house.
The platform is contracted and the development team exists. What's missing is someone to decide what gets built, review what comes back and be technically accountable for the result.
Nobody has written the partner matrix or the message guides. The moment that person goes on holiday, EDI becomes an operational risk.
We work as part of your team, not as a black box. The usual split is 80% leading and coordinating, 20% hands-on work on the flow itself. And the stated goal is that when we leave, the knowledge stays in house.
The EDI tech lead role that mid-sized companies need and almost never have on payroll. We are the technical authority over the flow and the single point of contact for your vendor.
Bringing a new customer or supplier into the flow, from message guide to production, without leaving the process half done.
The flow written down, not passed on by word of mouth. It's what turns an integration into a company asset instead of a dependency on one person.
So the next incident gets solved by your people. We train whoever will live with the flow, at their level and with their own messages on the table.
We lead the technical workstream for exiting a system or a VAN: inventory, message plan, partner migration and testing. The overall project plan stays on your side.
When EDI has to be disconnected from the parent company against a contractual date, we lead that workstream and coordinate whoever executes it, in your team or your operations advisor's.
A short, bounded piece of work to find out what state your integration is really in before committing budget: inventory, prioritised risks and a report with a roadmap. It's the usual way to start with us.
As a layer of the integration project, not as a standalone service: designing how compliance is met (mapping to EN 16931, channel choice) and validating that an existing flow complies.
A project that has stalled, or a budget that doesn't match what is being delivered. We review it and tell you what we see.
We work with SAP Business Network and Ariba when they are part of the client's flow. We do not do SAP middleware (PI/PO, CPI).
Saying it upfront saves everyone time. If what you need is in the left-hand column, there are better vendors than us and we can point you to them.
If the date was fixed before the first conversation, we'll say so in the first conversation. A deadline that doesn't hold up technically doesn't improve because nobody mentions it.
There can be many teams around the table: communications, development, business, the vendor. Connecting them is our job. What we need from your side is someone who decides.
A misread segment, a partner identifier that isn't what you expected, an assumed unit of measure. That's where projects fall over, and that's where we put the hours.
We're at our best on engagements of six months and up, where there's time to understand the business and leave the flow documented. One-week emergencies are not our thing.
“A good EDI specialist ‘wastes time’ on the details.” Rebeca Delconte, Founder
What follows is what we sign up to without caveats. If your flow is here, the conversation starts quickly.
Ten years devoted to a single craft: getting two systems that don't know each other to exchange business documents without anyone having to check them by hand. She has worked the flow from all three sides of the triangle: from the company that needs it, from the vendor that sells it and from the consultancy that leads it.
Experience at Syensqo (Solvay), Fossil Group and EDICOM. Currently leading the EDI workstream of a group operating in 16 countries.
PhD in Applied AI and product owner. He brings the firm's product judgement: how an integration flow becomes something repeatable, measurable and documented, rather than work that has to be reinvented at every client.
He also leads Vuola's own R&D line: AI automation of EDI operations, classifying IDoc incidents and creating tickets automatically. It is in development today and is not a product for sale. The innovation and EU projects side lives at vuola.tech.
If you have an EDI workstream with nobody leading it, write to us. Tell us in four lines which flow it is, which platform you work with and what date you have hanging over you. We reply with a concrete opinion, not a catalogue. We work with a small number of clients at a time: if it's a good fit we'll say so early, and if it isn't, we'll say that too.
There's a message guide, there's a date, and nobody in house to read it. That's where we start.
Before moving anything, a real inventory of what exists and what breaks if you touch it.
Documenting it and training the team is cheaper than finding out the day it fails.
