After go-live
Making your team autonomous on what we delivered
A flow your team cannot maintain without us is a flow half delivered. These formats exist to prevent that.
The principle
- We train on your real flows, not on generic examples. The training material is your own mapping.
- The goal is not to turn your teams into EDI specialists, but to let them read a rejection, fix the common cases and recognise the ones that need an intervention.
- These formats come after a go-live. They make no sense in isolation.
The formats
Flow handover
- Audience
- IT / integration team
- Duration
- Half a day per flow
Full handover of a delivered flow: architecture, business rules, known breaking points, recovery procedure. By the end, your team can maintain it.
- Reading and interpreting a rejected message
- Supervised modification of an existing mapping
- Replay and error-recovery procedure
- Documentation handed over and walked through
Reading rejections
- Audience
- Finance / order management
- Duration
- Two hours
For the teams who receive the errors without having caused them: understanding what a rejection says, what they can fix on their side, and what they cannot.
- Anatomy of a rejection message
- The most frequent causes, in order of frequency
- What gets fixed in the ERP, what belongs to the flow
- When and how to escalate
Monitoring & operations
- Audience
- Operations / support
- Duration
- Two hours
Taking over exchange monitoring: knowing what was sent, what is stuck, what failed, and reacting without waiting for the partner to call.
- Reading the monitoring views
- Alerts: which to act on, which to ignore
- Replaying pending flows
- Incident log and follow-up
Start with the flow, not the training
These formats assume a flow has been delivered. If that is not the case yet, the diagnostic is where to start.