Belli
Demo

Sign in

Belli runs on its own address for every airline. Enter yours to continue.

.belli.ai

Not sure of your address? Ask us.

News

How Farhan wants new EDI messages to plug in

Farhan's proposal for the next version of our inbound EDI pipeline: every message type and version becomes a small plugin, so adding FFM/9 or a new source like SFTP doesn't mean touching the core.

Published
18 November 2026
Reading time
3 min
In this article

Airlines, ground handlers and agents send us cargo messages all day: FFM manifests, FWB air waybills, FSU status updates, FHL house lists and FBL booking lists. Each type comes in versions, written after the slash on the first line, so FFM/8 is version 8 of the flight manifest. Our first inbound pipeline has served us well, but every new type or version means editing several places in shared code, and a new source such as SFTP or SITA needs its own custom work.

Farhan, one of our backend engineers, has proposed a different shape for the next version. It is a proposal, not something we have built yet.

One plugin per message type

In Farhan's design, each message type and its versions become a small plugin. A shared pipeline does everything the plugins have in common: it saves the original message, claims it, retries it and holds it when something is wrong. A registry reads the type and version from the first line and hands the message to the plugin registered for exactly that pair.

Adding a new version, a new type or a new source becomes one package and one line to register it. Nobody edits the core.

Never guess the version

If no plugin is registered for an exact type and version, say FFM/9 before anyone has written a parser for it, the message is held for a person to review. The pipeline never falls back to the nearest version it knows, because a manifest read with the wrong rules is worse than one that waits.

Try it yourself

Farhan built an interactive model of the design. Plug in a new version, a new message type or a new source below, then send a sample message and watch where it goes.

Farhan's interactive model. Click a dashed slot to plug in a plugin or source, then send a message and see where it goes.