Audience: EDI analysts, integrators, B2B integration teams
Orderful's Any file over MFT feature lets you exchange files of specific formats with your trading partners — even if those files don't follow standard EDI specifications like X12 or EDIFACT. This article explains what qualifies as "any file", what MFT means, and answers common questions.
What counts as "any file"?
Any file means a file that is not a standard EDI format (X12, EDIFACT, or Orderful JSON). At launch, Orderful supports the following file formats over MFT:
JSON — Custom or proprietary JSON formats (non-Orderful)
XML — cXML, ebXML, proprietary XML schemas
CSV — Custom purchase orders, inventory files, healthcare claims
PDF — Proof of Delivery (POD), Bill of Lading (BOL), invoices
JPEG — Label files, scanned documents, images
If your use case requires a different file format, contact Orderful support — additional formats can be added.
What transaction types are supported?
Because any file transactions don't follow EDI standards, Orderful created a set of format-agnostic transaction types to differentiate business documents that may use the same file format. For example, both a purchase order and an invoice could be sent as XML — the transaction type tells Orderful (and your partner) what kind of document it is.
See the full list of available transaction types. If you need a transaction type that isn't listed, contact Orderful support — new types can be added on demand.
What is MFT?
MFT stands for Managed File Transfer. In Orderful, MFT means the file is routed and passed through from sender to receiver without any EDI content processing.
Orderful will:
Receive the file
Route it to the correct relationship
Create a transaction
Deliver it to your partner
Orderful will not validate the file content against a schema or guideline, transform or convert its content, or process acknowledgments automatically. Validation in MFT mode covers successfully extracting routing metadata and routing the file to the correct relationship — not file content.
What to Send Orderful Support
If you have questions about supported file formats or transaction types, contact [email protected] with:
The file format you are trying to exchange
Your partner's name and the transaction type you need
A description of what you are trying to achieve
Frequently Asked Questions
Can Orderful convert my partner's custom XML into Mosaic (simplified JSON)?
Not yet. In the current release, Orderful acts as a pass-through — the file is delivered to you exactly as received, without any conversion. If your integration expects Mosaic JSON, you will need to handle the conversion in your own system. Conversion from custom file formats to Mosaic JSON is planned for a future release.
Can I trade both standard EDI and any file with the same partner?
Yes. A partnership can include both standard EDI transaction types (e.g. 204, 214, 210) and any file transaction types (e.g. PROOF_OF_DELIVERY). Each transaction type has its own relationship, and all transactions appear in the same unified Transaction List. This is common in transportation and logistics, where standard EDI covers load tenders and status updates while supporting documents like PODs travel over MFT.
Where can I see my any file transactions?
Any file transactions appear in the Transactions view alongside your standard EDI transactions. You can filter by transaction type, direction, delivery status, business number, and more.