Skip to main content

Implementations - Portal Testing

See below guidelines for testing trading partners via designated customer portals.

Written by Lori Anne Stevens

Product(s): Foundry platform, Transaction Manager


Whenever you begin testing a new Trading Partner Connection, your Trading Partner will typically require either Portal Testing (Web) or Direct Testing (AS2) to ensure compliance is met for all EDI Transactions in regards to the RAW EDI data sent.

Portal Testing is when your Trading Partner selects a third-party platform to host EDI testing on their behalf utilizing a Web Portal that affirms compliances. This article explains Portal Testing essentials, common portals, access requirements, fees, and best practices to ensure a smooth transition to production.


Overview of Trading Partner Portal Testing


At times, a Trading Partner can choose not to conduct EDI compliance testing for their vendors. They can decide to outsource their compliance testing to a third-party or certification company on their behalf, or conduct independent testing. There are several options for Trading Partners to choose from when it comes to third-party testing companies. The most commonly used third-party testing companies are listed in the table under Commonly Used Third Party Companies, below.

Third-party certification companies allow vendors to test via their online portal while trading transactions directly within your Transaction Manager. Upon completing the required forms and providing the third-party with all necessary details, they will provide you with a URL, Username, and Password for the online testing portal. These details can be shared with your Implementation Specialist upon adding the Trading Partner plug-in to your account. Testing can consist of testing inbound transactions, such as Purchase Orders, as well as Outbound transactions, such as Advance Shipping Notices (ASNs) and Invoices. Testing can also consist of testing UCC-128 labels and/or Packing Lists/Slips. There is a timeline to complete all required testing and that timeline will be discussed with your Trading Partner, the third-party, and your organization.


Commonly Used Third Party Companies


While there are many Third-Party Compliance companies out there, many of the Trading Partners connected with the TrueCommerce Network (TC.Net) share common ones.

These Trading Partners are often marked with a suffix to indicate which Third-Party Compliance company they may utilize, such as Kohls DSCO, Trader Joe's (SPS), and Home Depot CommerceHub.

Third-Party Company

Notes

SPS Commerce

EDICT Systems

OpenText

Logicbroker

LBMX

York

CommerceHub

Owned by Rithum

DSCO

Owned by Rithum


Preparation and Access


Actions needed:

· Ensure an employee at your organization has the appropriate URL and login credentials to access the third-party testing portal in order for testing to begin.

· Review all testing requirements thoroughly.

· Discuss any discrepancies with your Trading Partner and/or the portal host.

IMPORTANT: A testing fee can be charged by your Trading Partner or the third party and is outside of TrueCommerce's control.


Testing Process and Transactions


Portal testing processes and transactions vary based on your Trading Partner.

Some portals test connectivity with TrueCommerce, while others require manual intervention for file transfers and may need assistance from your Implementation Specialist.


Warning Callout


Most portal testing validates the “syntax” or structure of your EDI data, not necessarily its data accuracy. However, it is highly recommended to ensure your data is as accurate as possible for Trading Partner requirements to facilitate a smooth transition to production.

rev. 7/12/2026

Did this answer your question?