Skip to main content

How to Get a Separate Test ISA ID for Testing EDI Transactions

A
Written by Amelie Roux
Updated today

Audience: EDI developers, B2B integration teams, account administrators

When to use this article: You need this when your trading partner requires completely separate ISA IDs for test and production traffic — meaning your test transactions must come from a different ISA ID than your live transactions.

What's Happening

Trading partners handle test versus production EDI traffic in two ways:

  1. Same ISA ID, different usage indicator — They use your production ISA ID for both test and live transactions, relying on the ISA15 field (T for test, P for production) to distinguish them

  1. Separate ISA IDs entirely — They route test transactions to a completely different ISA ID, typically your production ISA ID with a "T" suffix

If your partner uses approach #2, you need Orderful to register that separate test ISA ID on your account. Without it, test transactions sent to that ISA ID will be rejected or misrouted.

The test ISA ID itself doesn't control whether Orderful treats transactions as test or production — that's determined by your relationship status, the ISA15 field, or the stream value in JSON API calls. But your partner's routing system needs to recognize the test ISA ID to deliver transactions correctly.

How Trading Partners Typically Set Test ISA IDs

Most common pattern: Add "T" to your production ISA ID

  • Production: 12/8004524462

  • Test: 12/8004524462T

Custom patterns: Some partners specify their own convention

  • Production: 12/ACME001

  • Test: 12/ACMETEST or 12/ACME001-T

Your trading partner will specify the exact test ISA ID value during EDI setup. If they haven't provided one, ask them directly — don't assume the "T" suffix pattern.

How to Request Your Test ISA ID

This requires Orderful support — test ISA IDs can't be changed directly in Orderful.

Step 1 — Find your current production ISA ID

  1. In Orderful, go to Relationships and open any active relationship

  2. Click Settings > Advanced Settings

  3. Note your ISA ID Qualifier and ISA ID Value (e.g., 12 and 8004524462)

Step 2 — Determine your test ISA ID value

  • If your trading partner specified a test ISA ID, use their exact value

  • If they haven't specified one, ask them directly what test ISA ID to use

  • Only use the "T" suffix convention if your partner explicitly confirmed it

Step 3 — Email [email protected]

Include this information:

  • Current production ISA ID: Both qualifier and value (e.g., 12/8004524462)

  • Requested test ISA ID: The exact value your partner requires (e.g., 12/8004524462T)

  • Partner confirmation: Forward the email or documentation where your partner specified the test ISA ID

  • Account scope acknowledgment: "I understand this test ISA ID will apply to all test relationships on this EDI account"

Important: Test ISA IDs are set at the EDI account level, not per relationship. This change affects every test relationship using your account.

Step 4 — Testing after setup

Once Orderful confirms the change:

  1. Send a test transaction using your test relationship

  2. Verify the outbound ISA header shows your new test ISA ID

  3. Confirm your partner receives and acknowledges the test transaction

Real-World Example

In a recent case, a logistics company needed to test 204 transactions with a major retailer. The retailer's EDI team specified:

  • Production ISA ID: 12/LOGISTICS001

  • Test ISA ID: 12/LOGISTICS001TEST

The company contacted Orderful support with both values and partner confirmation. After the update, all test 204s were sent from 12/LOGISTICS001TEST while production transactions continued using 12/LOGISTICS001.

What to Send Orderful Support

When requesting a test ISA ID, include:

  • Your current production ISA ID (qualifier and value from Relationship Settings)

  • The exact test ISA ID value your partner requires

  • Partner documentation confirming the test ISA ID (email, setup guide, etc.)

  • Your EDI account name in Orderful

  • Confirmation that you understand this applies to all test relationships on the account

Frequently Asked Questions

Does the test ISA ID automatically make transactions "test" transactions?

No. The ISA ID is just an identifier for routing. Whether transactions are test or production is controlled by your relationship status (test vs live), the ISA15 usage indicator, or the stream parameter in JSON API calls.

Will this affect all my trading partner relationships?

Yes. Test ISA IDs are set at the EDI account level. Every test relationship using that account will send transactions from the new test ISA ID. Production relationships are unaffected.

My partner uses the ISA15 field to distinguish test from production. Do I still need a separate test ISA ID?

No. If your partner accepts test transactions sent to your production ISA ID (distinguished only by ISA15 = T), you don't need a separate test ISA ID. This is only needed when partners route test traffic to a completely different ISA ID.

Can I change the test ISA ID back to the original after testing?

Yes. Contact [email protected] to revert to your previous test ISA ID. Include the original value you want restored.

What happens if I send a test transaction to the wrong ISA ID?

Your trading partner's system will likely reject it or route it incorrectly. You'll typically see routing errors or the transaction will be processed as production when you intended it as a test.

Did this answer your question?