Built from thousands of real EDI mappings
Early access for teams buried in EDI mapping.
We have built thousands of EDI maps by hand.
Then we taught EDI Genius how to do it.
EDI Genius identifies field mappings based on patterns that experienced mappers typically review. Provide your source and target files. The system evaluates possible field matches and highlights the ones that align most closely.
Built for EDI onboarding, EDI platform migration, and automated EDI mapping workflows.
EDI Genius is automated EDI mapping software for teams that need to discover, review, and validate mappings across X12, EDIFACT, ERP, ETL, and migration workflows.
The knowledge of how your business system maps to a document spec usually lives in one person's head. It takes years to build and is rarely documented. When that person leaves, when new trading partners need onboarding, or when you want to switch platforms — that bottleneck turns into a real problem.
Anyone who has mapped EDI by hand knows the hard part is not copying fields. It is everything in between:
This is where most tools fall short. The challenge is not text generation. It is dealing with incomplete specs, partner-specific exceptions, and edge cases that only show up in production.
EDI Genius understands the relationships between ERP data elements. When it resolves one field in a group, it narrows the search for the rest. And when it cannot find a confident answer, it tells you.
These patterns come from real implementation work. EDI Genius uses a proprietary DNA Engine built on that experience to surface reusable mapping rules across your integrations.
This is not for casual signups. We are looking for technical teams doing real integration work, with edge cases and clear opinions on how this should perform.
People building mappings, writing transformations, troubleshooting files, and automating pipelines across systems.
Teams managing onboarding, gathering requirements, and handling ongoing mapping changes.
Teams supporting multiple clients who want a faster way to deliver mappings and launch projects.
Watch it fingerprint, test, and resolve mappings across 6 trading partners — 3.4M+ candidate paths evaluated in real time.
We're using the first round of access to see where the product is most useful: faster mappings, better partner onboarding, and more consistent delivery for consultants and integration teams.
Early adopters can submit a small number of trading partners and document definitions, review the generated mappings manually, and tell us where the output is right, wrong, or incomplete.
Best fit for teams actively onboarding partners or maintaining a large map inventory.
EDI Genius is not just about source-target mapping. It can become part of a broader workflow around partner requirements, mapping review, and implementation coordination.
Most useful for teams managing multiple onboarding efforts at the same time.
If you implement integrations for multiple customers, EDI Genius can become a productivity layer for discovery, mapping, and review. It can also open conversations around SimplicIT ETL for execution at scale.
We want partner feedback early.
Most tools compare field names and data types and draw connections. Some add confidence scores. Others generate code from samples or rely on stored mapping libraries.
We tested those approaches. They did not meet our requirements.
So we built our own engine.
EDI Genius builds a fingerprint of your business system. It captures structure, patterns, and transformation logic unique to your data. That carries forward to every new trading partner.
It does not rely on guesses. It evaluates every viable function sequence such as Copy, Transform, Concatenate, Lookup, HardCode, and SystemGenerated, then scores each option.
The highest scoring path is selected. Schema matching finds direct copies. EDI Genius identifies when a field needs multiple inputs, transformations, or lookup logic.
Your mappings remain private. You control them. Nothing is shared or locked away.
There are strong tools for moving EDI data, matching fields, and generating mapping code. Some require shared mappings. Others claim to remove mapping entirely by converting everything to JSON.
But the mapping still exists. It just moves upstream.
EDI Genius focuses on your business system. It captures structure, patterns, and logic behind your mappings. That knowledge stays with you.
EDI Genius delivers a complete mapping output.
Every target field is matched with a discovered source, transformation logic, accuracy score, and confidence level. The results are provided in a single Excel file that your team can review or use in your integration platform.
| # | Target Field | Discovered Source | Transform | Accuracy | Confidence | Status |
|---|---|---|---|---|---|---|
| 1 | ISA-01 | — | HardCode("00") | 100% | High | Resolved |
| 2 | ISA-02 | — | HardCode("") | 100% | High | Resolved |
| 3 | ISA-03 | — | HardCode("00") | 100% | High | Resolved |
| 4 | ISA-04 | — | HardCode("") | 100% | High | Resolved |
| 5 | ISA-05 | — | HardCode("ZZ") | 100% | High | Resolved |
| 6 | ISA-06 | SenderID | Copy | 100% | High | Resolved |
| 7 | ISA-07 | — | HardCode("ZZ") | 100% | High | Resolved |
| 8 | ISA-08 | ReceiverID | Copy | 100% | High | Resolved |
| 9 | ISA-09 | — | SystemGenerated | 100% | High | Resolved |
| 10 | ISA-10 | — | SystemGenerated | 100% | High | Resolved |
| 11 | ISA-11 | — | SystemGenerated | 100% | High | Resolved |
| 12 | ISA-12 | — | HardCode("00401") | 100% | High | Resolved |
| 13 | ISA-13 | — | SystemGenerated | 100% | High | Resolved |
| 14 | ISA-14 | — | HardCode("0") | 100% | High | Resolved |
| 15 | ISA-15 | — | HardCode("P") | 100% | High | Resolved |
| 16 | ISA-16 | — | SystemGenerated | 100% | High | Resolved |
| 17 | GS-01 | — | HardCode("SH") | 100% | High | Resolved |
| 18 | GS-02 | AppSenderCode | Copy | 98% | High | Resolved |
| 19 | GS-03 | AppReceiverCode | Copy | 98% | High | Resolved |
| 20 | GS-04 | — | SystemGenerated | 100% | High | Resolved |
| 21 | GS-05 | — | SystemGenerated | 100% | High | Resolved |
| 22 | GS-06 | — | SystemGenerated | 100% | High | Resolved |
| 23 | GS-07 | — | HardCode("X") | 100% | High | Resolved |
| 24 | GS-08 | — | HardCode("004010") | 100% | High | Resolved |
| 25 | ST-01 | — | HardCode("856") | 100% | High | Resolved |
| 26 | ST-02 | — | SystemGenerated | 100% | High | Resolved |
| 27 | BSN-01 | — | HardCode("00") | 100% | High | Resolved |
| 28 | BSN-02 | ShipmentID | Copy | 98% | High | Resolved |
| 29 | BSN-03 | ShipDate | FormatDate(yyyyMMdd) | 96% | High | Resolved |
| 30 | BSN-04 | ShipTime | FormatDate(HHmm) | 96% | High | Resolved |
| 31 | HL[S]-01 | — | SystemGenerated | 100% | High | Resolved |
| 32 | HL[S]-03 | — | HardCode("S") | 100% | High | Resolved |
| 33 | HL[S]-04 | — | HardCode("1") | 100% | High | Resolved |
| 34 | HL[S].TD1-01 | — | HardCode("CTN25") | 100% | High | Resolved |
| 35 | HL[S].TD1-02 | TotalCartons | OnlyInt | 93% | High | Resolved |
| 36 | HL[S].TD1-07 | GrossWeight | Copy | 95% | High | Resolved |
| 37 | HL[S].TD1-08 | — | HardCode("LB") | 100% | High | Resolved |
| 38 | HL[S].TD5-01 | — | HardCode("B") | 100% | High | Resolved |
| 39 | HL[S].TD5-02 | — | HardCode("2") | 100% | High | Resolved |
| 40 | HL[S].TD5-03 | CarrierSCAC | Copy | 100% | High | Resolved |
| 41 | HL[S].TD5-04 | — | HardCode("M") | 100% | High | Resolved |
| 42 | HL[S].TD5-05 | CarrierName | Copy | 98% | High | Resolved |
| 43 | HL[S].TD3-01 | — | HardCode("TL") | 100% | High | Resolved |
| 44 | HL[S].TD3-03 | TrailerNum | Lookup | 85% | Medium | Evaluate |
| 45 | HL[S].REF(BM)-01 | — | HardCode("BM") | 100% | High | Resolved |
| 46 | HL[S].REF(BM)-02 | BOLNumber | WhicheverIsNotEmpty | 98% | High | Resolved |
| 47 | HL[S].DTM(011)-01 | — | HardCode("011") | 100% | High | Resolved |
| 48 | HL[S].DTM(011)-02 | ShipDate | FormatDate(yyyyMMdd) | 96% | High | Resolved |
| 49 | HL[S].FOB-01 | FreightTerms | Copy | 88% | Medium | Resolved |
| 50 | HL[S].N1(ST)-01 | — | HardCode("ST") | 100% | High | Resolved |
| 51 | HL[S].N1(ST)-02 | ShipToName | Copy | 100% | High | Resolved |
| 52 | HL[S].N1(ST)-03 | — | Lookup | 100% | High | Resolved |
| 53 | HL[S].N1(ST)-04 | ShipToID | Copy | 98% | High | Resolved |
| 54 | HL[S].N1(ST).N3-01 | ShipToAddr1 | Copy | 100% | High | Resolved |
| 55 | HL[S].N1(ST).N4-01 | ShipToCity | Copy | 100% | High | Resolved |
| 56 | HL[S].N1(ST).N4-02 | ShipToState | Copy | 100% | High | Resolved |
| 57 | HL[S].N1(ST).N4-03 | ShipToZip | Copy | 99% | High | Resolved |
| 58 | HL[S].N1(SF)-01 | — | HardCode("SF") | 100% | High | Resolved |
| 59 | HL[S].N1(SF)-02 | ShipFromName | Copy | 100% | High | Resolved |
| 60 | HL[S].N1(SF)-03 | — | HardCode("92") | 100% | High | Resolved |
| 61 | HL[S].N1(SF)-04 | ShipFromID | CopyFromQualifiedLoop | 97% | High | Resolved |
| 62 | HL[O]-01 | — | SystemGenerated | 100% | High | Resolved |
| 63 | HL[O]-02 | — | SystemGenerated | 100% | High | Resolved |
| 64 | HL[O]-03 | — | HardCode("O") | 100% | High | Resolved |
| 65 | HL[O].PRF-01 | PONumber | Copy | 100% | High | Resolved |
| 66 | HL[O].REF(IA)-01 | — | HardCode("IA") | 100% | High | Resolved |
| 67 | HL[O].REF(IA)-02 | InternalVendorID | CopyFromQualifiedLoop | 83% | Medium | Evaluate |
| 68 | HL[I]-01 | — | SystemGenerated | 100% | High | Resolved |
| 69 | HL[I]-02 | — | SystemGenerated | 100% | High | Resolved |
| 70 | HL[I]-03 | — | HardCode("I") | 100% | High | Resolved |
| 71 | HL[I].LIN-01 | — | SystemGenerated | 100% | High | Resolved |
| 72 | HL[I].LIN-02 | — | HardCode("VP") | 100% | High | Resolved |
| 73 | HL[I].LIN-03 | VendorPartNum | Copy | 98% | High | Resolved |
| 74 | HL[I].LIN-04 | — | HardCode("BP") | 100% | High | Resolved |
| 75 | HL[I].LIN-05 | BuyerPartNum | Copy | 100% | High | Resolved |
| 76 | HL[I].SN1-01 | — | SystemGenerated | 100% | High | Resolved |
| 77 | HL[I].SN1-02 | QtyShipped | OnlyInt | 95% | High | Resolved |
| 78 | HL[I].SN1-03 | — | HardCode("EA") | 100% | High | Resolved |
| 79 | HL[I].PO4-01 | PackQty | Copy | — | — | Unresolved |
| 80 | HL[I].PID-01 | — | HardCode("S") | 100% | High | Resolved |
| 81 | HL[I].PID-05 | ItemDescription | Copy | 100% | High | Resolved |
| 82 | HL[I].MEA(WT)-01 | — | HardCode("WT") | 100% | High | Resolved |
| 83 | HL[I].MEA(WT)-02 | — | HardCode("WT") | 100% | High | Resolved |
| 84 | HL[I].MEA(WT)-03 | ItemWeight | OnlyInt | 93% | High | Resolved |
| 85 | HL[P]-01 | — | SystemGenerated | 100% | High | Resolved |
| 86 | HL[P]-02 | — | SystemGenerated | 100% | High | Resolved |
| 87 | HL[P]-03 | — | HardCode("P") | 100% | High | Resolved |
| 88 | HL[P].MAN-01 | — | HardCode("GM") | 100% | High | Resolved |
| 89 | HL[P].MAN-02 | SSCCBarcode | ConcatWithDash | 95% | High | Resolved |
| 90 | CTT-01 | — | SystemGenerated | 100% | High | Resolved |
| 91 | SE-01 | — | SystemGenerated | 100% | High | Resolved |
| 92 | SE-02 | — | SystemGenerated | 100% | High | Resolved |
| 93 | GE-01 | — | SystemGenerated | 100% | High | Resolved |
| 94 | GE-02 | — | SystemGenerated | 100% | High | Resolved |
| 95 | IEA-01 | — | SystemGenerated | 100% | High | Resolved |
| 96 | IEA-02 | — | SystemGenerated | 100% | High | Resolved |
"We onboard enough partners each year that reducing mapping and review time would have an immediate impact."
"We already have tools. The real cost is still the manual thinking, review, and coordination behind each map."
"If this shortens discovery and mapping work for clients, it changes how our delivery team operates."
Launch Constraints
The first release focuses on mapping discovery and review. It does not include an execution engine yet. We are prioritizing teams willing to validate results and provide direct feedback.
These are the questions teams ask when evaluating mapping tools, speeding up onboarding, or deciding if manual mapping is still workable.
EDI Genius discovers and scores field mappings between source definitions and target definitions. It is built to help integration teams review mappings faster instead of starting from a blank map every time.
It is built for integration developers, EDI coordinators, consultants, and managers working on EDI onboarding, EDI migration, and mapping maintenance workflows.
The first release is focused on mapping discovery and review. It helps your team figure out what maps to what, what looks strong, and what still needs validation before execution.
It can find direct copies, transforms, concatenations, lookups, hardcodes, and system-generated values. It then scores candidate paths so your team can review the best options first.
Yes. EDI Genius is designed to work alongside your current platform and mapping workflow. The output is meant to be reviewed by your team and used in downstream implementation work.
It is especially useful when your team is onboarding trading partners, migrating EDI platforms, rebuilding maps, inheriting undocumented logic, or trying to reduce dependence on a single expert mapper.
Tell us about your integration work and how you build mappings today.
We review every submission and send verification codes to approved users.
Free preview. No credit card required. Limited spots.