Incoming documents — EDI, X12, EDIFACT, JSON, XML, Excel, webhooks, and more — are received, parsed, validated, and actioned the moment they arrive. Zero manual intervention. Zero integration projects.
Every trading partner sends data differently. EDI 850 from one, JSON webhook from another, Excel spreadsheet from a third. Each format requires custom mapping. Each connection requires an integration project. Each change requires a developer. The overhead is constant. The errors are inevitable.
That ends with Justransform.
01 — Receive
Any format, any protocol, any partner maturity level. AS2, SFTP, API, email, webhook, web scraping. If a partner can send it, Justransform can receive it. No negotiation. No project. No timeline.
Intake layer02 — Transform
JTMapper identifies the document standard and maps it to JTCanonical automatically. 33,000+ pre-built specifications. Your partners are probably already there. No custom mapping required.
JTMapper engine03 — Act
Validated documents trigger immediate workflow execution. Acknowledgements sent. Partners notified. System updated. No manual step. No queue. No delay. Under 80ms start to finish.
Execution layerEvery format your trading ecosystem uses — already built in. No connector projects. No custom development. No timeline.
Document formats
Communication protocols
JTMapper
JTMapper reads any incoming document, identifies its structure and standard, looks up the specification in JTRegistry, maps every field to the canonical object, and validates the result — automatically. No configuration. No training data. No custom code.
JTRegistry
JTRegistry is the world's largest library of EDI specifications, canonical object definitions, workflow templates, partner configurations, and form schemas. Browse, discover, and deploy in one click. Community-contributed. Constantly growing.
The core transformation engine. Identifies any incoming document, locates its specification, maps fields to canonical structure, and validates — in a single automated pass.
RPA-enhanced mapping for non-standard documents — Excel spreadsheets, PDFs, and screen-scraped data. Handles the long tail of partner formats that do not follow standards.
Manages all inbound and outbound communication channels. AS2, AS4, SFTP, REST, SOAP, webhooks, VAN networks — configured once, operational immediately.
Transforms spreadsheet-based workflows into structured system inputs. Partners who live in Excel get a seamless onboarding path — no portal required, no behavior change needed.
The specification library powering all intake operations. 33,000+ pre-built mappings, partner configurations, and schemas. Browse, download, and deploy in one click.
System integration
Every intake module feeds directly into JTProcess, JTWorkflow, and JTCanonical. No hand-off configuration. No middleware. The system is whole by design.
View system architecture →A tier-1 supplier sends a purchase order in X12 EDI 850 format over AS2. Justransform receives the document, validates it against the 33,000-spec library, maps it to JTCanonical, sends a 997 acknowledgement, creates the purchase order in the system, and triggers fulfillment — all before the sender’s system has finished its transmission handshake.
EDI 850 received → Spec identified → 997 sent → PO created → Fulfillment triggered<80msA new supplier sends an Excel spreadsheet — their internal format, no EDI capability. JTRPAMapper reads the file, infers the column mapping, maps to canonical PurchaseOrder, and creates the record. The partner then receives a generated data portal for future submissions. No integration project. No developer. First document processed the same day.
Excel received → RPA maps fields → Canonical created → Portal generated → Partner onboardedDay 1An e-commerce platform posts a JSON order webhook. Justransform receives it, maps the payload to JTCanonical SalesOrder, validates against business rules, triggers the fulfillment workflow, assigns a carrier, generates the shipping label, and sends the order confirmation — fully automated, no human in the loop.
Webhook received → Order canonical → Fulfillment → Label generated → Confirmation sentAutomated