Inbound EDIEngineering proposal, November 2026

Inbound EDI plugins

Each EDI message type and version becomes a small plugin. The shared pipeline does the rest. To add a new one, you write one plugin and register it. You do not edit the core.

ProposalNot built yet

Words used here

Seven words come up often. Here is what each one means.

WordMeaning
Message typeThe kind of EDI message, such as FFM, FWB, FSU, FHL or FBL.
Wire versionThe number after the slash on the first line. In FFM/8, the version is 8.
PluginA small package that handles one message type and its versions.
RegistryThe list that maps a type and version to a plugin.
ApplicatorCode that makes the business change, such as creating an order.
ConnectorCode that gets messages from a source, such as Gmail or SFTP.
HeldSet aside so a person can review it.

The solution

A plugin handles one message type and its versions, such as FFM/8. The shared pipeline does everything else. A new plugin is one package and one line to register it.

%%{init: {"theme":"base","themeVariables":{"darkMode":false,"titleColor":"#1C1917","fontFamily":"Inter, system-ui, sans-serif","fontSize":"13px","background":"#FFFFFF","mainBkg":"#FFFFFF","primaryColor":"#FFFFFF","primaryTextColor":"#1C1917","primaryBorderColor":"#A49D98","nodeBorder":"#A49D98","lineColor":"#A49D98","textColor":"#1C1917","secondaryColor":"#F6F5F3","tertiaryColor":"#FBFAF9","edgeLabelBackground":"#FFFFFF","clusterBkg":"#FBFAF9","clusterBorder":"#E8E6E3","actorBkg":"#F6F5F3","actorBorder":"#A49D98","actorTextColor":"#1C1917","signalColor":"#514C48","signalTextColor":"#1C1917","noteBkgColor":"#FEEFCD","noteBorderColor":"#9B5208","noteTextColor":"#1C1917","labelBoxBkgColor":"#E8F1FC","labelBoxBorderColor":"#1D5CAF","labelTextColor":"#1D5CAF","loopTextColor":"#1D5CAF"},"flowchart":{"nodeSpacing":24,"rankSpacing":30,"padding":8,"curve":"basis","wrappingWidth":180}}}%%
flowchart TD
  S1["Gmail connector"] --> PL
  S2["SES connector"] --> PL
  S3["Edifly, SFTP or SITA connector"] --> PL
  PL["Shared pipeline: saves, claims, retries, holds"] --> RG["Registry: type and version"]
  RG --> P1["FWB plugin"]
  RG --> P2["FSU plugin"]
  RG --> P3["FHL plugin"]
  RG --> P4["FBL plugin"]
  RG --> P5["FFM plugin: versions 5, 6, 8"]
  RG --> HD["Held: unsupported type or version"]
  P1 --> DA["Shared applicators"]
  P2 --> DA
  P3 --> DA
  P5 --> DA
  V1["v1 integrator"] --> DA
  classDef default fill:#FFFFFF,stroke:#A49D98,color:#1C1917
  classDef ok fill:#E5F6EB,stroke:#186D37,color:#1C1917
  classDef hold fill:#FEEFCD,stroke:#9B5208,color:#1C1917
  classDef bad fill:#FDEDED,stroke:#B62020,color:#1C1917
  classDef info fill:#E8F1FC,stroke:#1D5CAF,color:#1C1917
  classDef ext fill:#F6F5F3,stroke:#A49D98,stroke-dasharray:4 3,color:#1C1917
  class S3,V1 ext
  class PL,DA info
  class HD hold
      
Two plug points. Connectors plug in at the top. Plugins plug in at the registry. v1 reaches the same business changes through shared applicators.
%%{init: {"theme":"base","themeVariables":{"darkMode":false,"titleColor":"#1C1917","fontFamily":"Inter, system-ui, sans-serif","fontSize":"13px","background":"#FFFFFF","mainBkg":"#FFFFFF","primaryColor":"#FFFFFF","primaryTextColor":"#1C1917","primaryBorderColor":"#A49D98","nodeBorder":"#A49D98","lineColor":"#A49D98","textColor":"#1C1917","secondaryColor":"#F6F5F3","tertiaryColor":"#FBFAF9","edgeLabelBackground":"#FFFFFF","clusterBkg":"#FBFAF9","clusterBorder":"#E8E6E3","actorBkg":"#F6F5F3","actorBorder":"#A49D98","actorTextColor":"#1C1917","signalColor":"#514C48","signalTextColor":"#1C1917","noteBkgColor":"#FEEFCD","noteBorderColor":"#9B5208","noteTextColor":"#1C1917","labelBoxBkgColor":"#E8F1FC","labelBoxBorderColor":"#1D5CAF","labelTextColor":"#1D5CAF","loopTextColor":"#1D5CAF"},"flowchart":{"nodeSpacing":24,"rankSpacing":30,"padding":8,"curve":"basis","wrappingWidth":180}}}%%
sequenceDiagram
  participant P as Pipeline
  participant R as Registry
  participant X as FFM plugin
  participant A as FFM applicator
  P->>R: first line is FFM/8
  alt FFM/8 is registered
    R->>X: hand over the message
    X->>X: read it and check the rules
    X->>A: apply the change
    A-->>X: done
    X-->>P: processed
  else FFM/9 is not registered
    R-->>P: hold as unsupported_version
  end
      
One lookup. The registry matches type and version exactly. A miss is held and kept, never guessed.

Try plugging one in

Click a dashed slot. Plug it in. Then send a message and see where it goes.

Registry, by type and wire version
Inspector
Plugins and sources. Try FFM/9 for a new version, FSA/1 for a new type, and SFTP or SITA for a new source. Slots are examples.

Add your own

Three common jobs. Each one lists what you write, what you register and how you test it.

I want to addYou writeYou registerYou test
A new version, such as FFM/9A parser for the new format. Reuse the FFM rules and applicator if the meaning is the same.The key FFM/9 on the FFM pluginA test that compares the output with FFM/8
A new type, such as FSA/1A parser, the rules and an applicator.The plugin, with its keysTests for failures and for repeated messages
A new source, such as SFTP or SITATwo functions: Fetch and Acknowledge. Say if accepted IDs can be listed.The connector and the channel ownerA crash drill, as in the durability page
No core edits. Saving, claiming, retrying and holding come from the shared pipeline.