Audience: EDI analysts, integrators, B2B integration teams

Your partner sends CSV files over SFTP or AS2, but their files contain no information Orderful can use to identify the sender, receiver, transaction type, or stream. This article explains your options for routing these files correctly.

Orderful needs four routing metadata fields to create a transaction on the correct relationship: sender identifier, receiver identifier, transaction type, and stream. For any file over MFT, Orderful cannot extract these from the file content. They must come from either a regex applied to the file name or static values configured on the communication channel.

If your partner's CSV files have no identifiable metadata in their file names either, static mode is the right approach.

Your partner's CSV files arrive with generic or unpredictable file names that contain no routing information — for example export.csv, data_20260301.csv, or files named by their internal system without any sender, transaction type, or stream identifier. A regex cannot reliably extract routing metadata from these names.

When files carry no routing metadata, configure all four routing fields to Static mode on the communication channel. This tells Orderful to assign fixed values to every file that arrives on that channel.

Because Static mode assigns the same routing values to all files on a channel, you need one SFTP folder per transaction type and stream combination. For example:

For each folder, create a dedicated communication channel in Orderful and configure it with Static values matching that folder's transaction type and stream.

The sender and receiver identifiers can also be set to Static if all files from a given folder always come from the same partner and go to the same EDI account — which is typical for dedicated SFTP folders.

If files are arriving in the SFTP folder but no transactions are being created, you will have received an unprocessed notification. To investigate:

1. Confirm the SFTP channel is active
Check that the communication channel is active and the connection credentials are valid.

2. Check the relationship status
Confirm the relationship is in LIVE status — or TEST if you are testing.

If files are arriving but transactions are not being created, contact [email protected] with:

Can I use one SFTP channel for all transaction types if I use Static mode?

No. With Static mode, every file on a channel is assigned the same transaction type. To receive different transaction types, you need a separate channel — and therefore a separate SFTP folder — for each.

What if my partner can add information to the file name in the future?

If your partner can include a consistent identifier in the file name, you can switch to Regex mode on the channel and extract the transaction type dynamically. This would allow you to consolidate into fewer folders. See I receive different types of XML files from my partner over AS2 for a worked example of that approach.

Does this work for AS2 as well?

Yes. The same Static mode approach works for AS2 channels. You would configure one AS2 channel per transaction type and stream, with all routing fields set to Static. Note that partners using AS2 typically configure a single channel for all transactions — creating individual AS2 channels per relationship is not common practice.