AS2 | EDI

Set Up AS2 EDI Connectivity with Tractor Supply | Expert Guide 2026

Learn how to set up AS2 EDI connectivity with Tractor Supply. This guide covers AS2 software setup, EDI mapping, testing, and going live as a TSC supplier.

Janaka Bandara

Janaka Bandara

Modified: 09 Apr 2026

Blog image

How to Set Up AS2 EDI Connectivity with Tractor Supply

If you supply agricultural or heavy machinery products through Tractor Supply (TSC), AS2 EDI connectivity is not optional - it is a hard requirement. TSC mandates that all suppliers use the AS2 communication protocol for every electronic data interchange transaction.

Getting this right from the start saves weeks of back-and-forth. This guide walks you through every stage: from configuring your AS2 server, to EDI testing, to going live with production traffic.

AS2 EDI connectivity setup with Tractor Supply

Understanding the Two Layers of a TSC Connection

A Tractor Supply AS2 and EDI connection is built on two distinct layers that work together.

Layer 1 - AS2 Protocol

The AS2 protocol handles the secure transport layer. It encrypts and signs your files, delivers them to TSC’s endpoint, and returns an AS2 MDN (Message Disposition Notification) receipt to confirm successful delivery.

Layer 2 - EDI

The EDI layer carries the actual business documents - purchase orders, invoices, shipping notices, and functional acknowledgments — formatted to TSC’s specifications.

These two layers are set up in sequence, but they are tightly intertwined. TSC requires a valid EDI file even during the AS2 connectivity testing phase. This catches many first-time suppliers off guard. For a primer on how AS2 works as a transport protocol, see our must-know facts on AS2.

AS2 and EDI connection layer diagram for Tractor Supply

AS2 and EDI connection layer diagram for Tractor Supply

Step 1: Create Your Trading Identities (Stations)

The first step is to set up your AS2 server identity inside your chosen AS2 software.

If you are using Aayu’s MFT Gateway, create a station on your account. You can either generate a new certificate or upload an existing key pair if migrating from another provider.

A few things to keep in mind:

  • Use an AS2 identifier and certificate common name (CN) that clearly represents your organization name.
  • TSC requires two separate connections - one for their test environment and one for production. Create two stations accordingly.
  • A common convention for the test station is to append a T, TST, or TEST suffix to your AS2 ID, with its own dedicated certificate.

Step 2: Exchange AS2 Configuration with TSC

Once your stations are ready, you will exchange AS2 connectivity details with Tractor Supply through their vendor portal.

Open a support ticket to begin the onboarding process. TSC’s team will ask you to submit onboarding documents and a Vendor AS2 Specifications form. Fill in the following details for both your test and production stations:

  • AS2 ID of your station
  • Encryption Algorithm: 3DES
  • Hashing Algorithm: SHA-1
  • Receipt Type: Signed receipt requested
  • PKI/S-MIME: Encrypted and signed
  • Source IP address allocated to your station
  • AS2 URL of your receiving endpoint
  • AS2 Software: e.g. Aayu Technologies MFT Gateway

TSC will share their own AS2 protocol configurations and certificates in return - typically .cer files embedded in a Word document. Use these to create partner records in your AS2 software.

Important: Always check the certificate expiry date before importing. TSC occasionally shares certificates from the previous year that are already expired or close to expiring.

TSC typically takes up to 5 business days to configure the connection and whitelist your IP. If you have a non-US IP address, additional whitelisting fees may apply. Aayu MFT Gateway uses US-based IP addresses exclusively, so this is not a concern for MFT Gateway users.

Step 3: Test AS2 Transmissions - Both Ways

TSC allocates two weeks for testing both the test and production AS2 and EDI connections. Testing runs in both directions.

Receiving from TSC is generally straightforward. When TSC sends a test EDI file, your AS2 server will accept it, save it to your inbox, and automatically return an AS2 MDN receipt. If anything fails, our guide on troubleshooting AS2 EDI transfer issues covers the most common failure modes.

Sending to TSC requires more care. The file you send must meet all of the following requirements:

  • EDI standard: X12 4010
  • ISA/GS identifiers: Must use DUNS numbers with qualifier 01
  • ISA15 flag: Set to T for test traffic, P for production
  • Content-Type (MIME type): application/edi-x12 - use the .x12 file extension in MFT Gateway, or specify the MIME type directly via the REST API

If these conditions are not met, TSC’s system may return errors referencing unexpected payload types or XML parsing failures. This is a direct result of incorrect EDI integration settings, not an AS2-level issue. Revisiting your EDI mapping and file content usually resolves it quickly.

Step 4: EDI Transaction-Level Testing

Once the AS2 connectivity phase passes, you move into full EDI integration testing. The exact documents required depend on your business model (e.g. drop-shipping vs. 3PL), but a typical D2C supplier will need to test all of the following:

  • 850 - Purchase Order (PO)
  • 997 - Functional Acknowledgment (FA)
  • 846 - Inventory Advice
  • 855 - Purchase Order Acknowledgment
  • 856 - Advanced Ship Notice (ASN)
  • 810 - Invoice
  • 860 - Purchase Order Change
  • 180 - Return Authorization Notification

For an overview of what each of these document types contains, see our EDI document types explained guide.

X12 mapping for each of these transactions must align precisely with TSC’s EDI documentation. Aayu’s EDI Generator handles the majority of these document types out of the box, reducing the need for custom EDI mapping software or manual EDI data mapping work.

Step 5: Go Live with Production Traffic

When all testing is approved, TSC sends a production approved email. At that point, switch your AS2 software configuration to the production station and begin live traffic.

A few key operational rules to follow once live:

  • Send 846 inventory updates once per day
  • Follow TSC’s “all orders shipped” policy
  • Return 997 functional acknowledgments within 48 hours for all TSC-originated EDI documents

For a broader checklist of what to verify before flipping to production, our AS2 compliance checklist is a useful reference.

Migrating an Existing TSC Connection?

If you already have a live TSC connection through another provider, the process is slightly different. Rather than opening a new onboarding ticket, you will need to submit a SNOW task through the TSC vendor portal to migrate the connection to your new provider and complete re-testing.

Aayu’s MFT Gateway has handled multiple TSC migrations. The transition is straightforward when your AS2 identifiers and certificate configurations are prepared in advance.

Get Your Tractor Supply EDI Connection Running Today

Setting up a Tractor Supply AS2 and EDI connection is entirely manageable - provided you know the steps, the certificate pitfalls, and the EDI file requirements up front.

Whether you are onboarding as a new TSC supplier or migrating an existing connection to a more cost-effective solution, Aayu’s AS2 software and EDI integration tools are built for exactly this use case.

Start your free MFT Gateway trial and connect with Tractor Supply.

Have questions about your specific setup? Reach out to our team - we are happy to help.

Janaka Bandara

Janaka Bandara

Janaka is a Software Architect at Aayu Technologies. He is experienced in diverse areas including enterprise integration, B2B communication, and cloud and serverless technologies; and has been involved in the design and implementation of almost every Aayu product. Any interesting bug will keep him up overnight, as will tea, movies, and music.
Talk to an EDI Expert
Stay Compliant. Stay Connected. Powered by AS2.

Join hundreds of organizations already taking full control of their B2B AS2 communications with our trusted solutions. Contact us today to tailor a solution that fits your specific AS2 EDI needs.

Request a demo and take a live look at all the features of our AS2 EDI solutions.
Get answers to your questions and explore customizations that we can offer tailored specifically for you.
Get to know the dedicated deployment option available for your specific use cases.
Loading...
Please wait...

We're processing your request

Related Articles

View All Blogs
EDI Generator
Cloud-Based EDI Solution with AS2 Integration
Aayu logomark
Driving Innovation, Simplifying Connections.
EDI via AS2
30-day Free Trial
Secure and Compliant