How to Prepare Your Trading Partner List Before Starting an EDI Project

The single biggest source of stalled EDI projects isn't a technology problem — it's an information problem. Teams kick off an onboarding engagement without a complete picture of who they're connecting to, how those partners currently send and receive data, and what documents actually need to flow. The result is delays, scope surprises, and testing cycles that stretch far longer than they should.

If you're a pharmacy operator, 503B compounder, or supply-chain team preparing for EDI onboarding, spending an extra day collecting the right details about each trading partner up front can save weeks downstream. This guide walks through exactly what to gather — and why each piece of information matters.

---

What a Trading Partner List Actually Is

In EDI, a trading partner list is your working inventory of every business you need to exchange electronic transactions with. That includes wholesalers, distributors, GPOs, buying groups, manufacturers, and any other entity in your supply chain that sends or receives purchase orders, invoices, advance ship notices, or related documents.

The list itself isn't just names. For each partner, your EDI team needs a small bundle of facts before any mapping work can begin. Without those facts, onboarding stalls while people chase down contacts, dig up old spec sheets, or discover mid-project that the scope is wider than originally understood.

Think of the trading partner list EDI project prep as the foundation of your entire engagement. Timelines, resource estimates, and go-live sequencing are all built on top of it. A rough list assembled before kickoff is far more useful than a complete list assembled three weeks in.

---

Why This Matters in Pharma Supply Chains

Pharma operations teams face a few dynamics that make up-front partner inventory more important than in many other industries.

Partner environments vary significantly. One distributor may connect via AS2 with a strict ISA/GS segment spec. Another may accept files over SFTP with a different envelope structure. A buying group might route transactions through a VAN or clearinghouse with its own requirements. Uniformity across your partner set is rarely the reality.

Contacts change. It's common to discover halfway through an onboarding project that the technical contact on file left the company, or that a partner recently switched EDI providers and the connection specs have changed. These surprises are avoidable with early outreach.

Document scope creeps. A project scoped for 850 purchase orders and 810 invoices can expand when someone realizes a key partner also requires 856 advance ship notices, or that a wholesaler expects functional acknowledgments (997s) that weren't in the original plan.

Compliance and business deadlines are real. Some partners impose go-live deadlines tied to contract terms, formulary changes, or operational cutover dates on their side. If you don't surface those deadlines early, you may learn about them after the timeline is already in trouble.

For a broader look at why these timelines stretch even with good intentions, see Why Pharma Trading Partner Onboarding Takes So Long.

---

Common Gaps That Stall EDI Projects

When teams arrive at kickoff without a complete trading partner list, these are the gaps that surface most often — and the ones that cause the longest delays:

• No documented connection method — teams don't know whether a partner uses AS2, SFTP, a VAN, a clearinghouse, a portal, or still relies on manual processes
• No monthly transaction volume — difficult to prioritize partners or right-size the engagement without a sense of which connections carry the most traffic
• No named technical contact — testing requires a real person on the partner side who can receive test files, confirm acknowledgments, and flag spec issues; a generic support email rarely moves things forward
• Unclear document requirements — which transactions are required versus optional isn't always obvious, especially when partners have legacy setups or informal workarounds in place
• No awareness of compliance deadlines — a partner-imposed cutover date two months out changes how the entire project needs to be sequenced
• Unknown current provider — if you're replacing an existing EDI setup, the current provider's configuration affects migration planning and realistic timeline estimates

Each of these gaps is recoverable, but each one costs time. The goal of the trading partner inventory is to find them before kickoff, not during it.

---

What to Capture for Each Trading Partner

For each partner on your EDI partner list, aim to collect the following before your project begins. Some fields will be blank at first — that's fine. Knowing what you don't know is still useful.

1. Partner Name and Identifier

Legal name plus any EDI identifier in use, such as ISA qualifier and ID or GLN. If you don't have the identifier yet, the name and a contact is enough to get started — identifiers can be confirmed during the testing coordination phase.

2. Primary Business Contact

The person on the partner side who owns the relationship. Useful when escalations are needed or contract questions surface mid-project.

3. Primary Technical or EDI Contact

This is the person who will coordinate testing, share implementation guides, and confirm file receipt during go-live. This contact is often different from the business contact and harder to track down quickly. Getting it early is one of the highest-value things you can do for your project timeline.

4. Current Connection Method

Document how the partner currently exchanges data. Common options include:

• AS2 — direct, point-to-point connection
• SFTP — file transfer via secure FTP
• VAN or clearinghouse — transactions routed through a third-party network
• Portal — manual upload or download via a web interface
• Manual — email, fax, or no structured data exchange today

If the method is unknown, note that explicitly. It tells you where your discovery questions need to go.

5. Document Types Exchanged

List the transaction sets involved for each partner. Common ones in pharma supply chains include:

• 850 — Purchase Orders
• 810 — Invoices
• 856 — Advance Ship Notices (ASNs)
• 997 / 999 — Functional Acknowledgments
• 855 — Purchase Order Acknowledgments

Note which are currently in use and which may be required but not yet implemented. The gap between what's flowing today and what will need to flow after go-live is often larger than teams expect.

6. Approximate Monthly Transaction Volume

Even a rough estimate — dozens, hundreds, or thousands of transactions per month — helps with prioritization. High-volume partners typically warrant earlier attention in the project sequence and more thorough testing.

7. Current Provider Being Replaced (If Applicable)

If you're migrating from an existing EDI setup, note which provider or platform currently handles each partner connection. Migration steps depend heavily on what's already in place.

8. Compliance or Business Deadline

If a partner has a specific date by which you need to be live — whether due to contract terms, a system cutover on their side, or a business requirement — capture it here. These deadlines shape everything about how the project is sequenced and resourced.

---

How Managed EDI Services Use This Information

When you bring a complete trading partner list to a managed EDI provider, the engagement can start moving immediately. The provider can:

• Check template coverage — many partners have already been mapped; reusable templates can significantly reduce time to go-live for those connections
• Identify new mapping work early — partners without existing templates can be flagged before kickoff so timeline estimates reflect actual build requirements
• Sequence the project realistically — known deadlines and volumes allow the team to prioritize the right connections first rather than working through partners arbitrarily
• Begin testing outreach immediately — having technical contacts on file means coordination can start in parallel with mapping, rather than waiting for contact discovery to happen first

Without this information, the early weeks of a project are often spent collecting what should have been gathered before kickoff. That delay compounds quickly.

For a broader view of what a well-prepared onboarding engagement looks like end to end, see our Pharma EDI Onboarding Checklist.

---

Where APXConnect Fits

APXConnect is a managed EDI and API service designed for pharma trading-partner workflows. When customers are ready to start an EDI project — or migrate from an existing setup — they share their trading partner list, and APXConnect helps manage mapping, testing, monitoring, and ongoing support from there.

For partners that have already been mapped, go-live can often happen in days. For new partner maps, the typical timeline is one to three weeks, depending on partner responsiveness and workflow complexity. Pricing is flat monthly with no per-transaction fees, which makes it easier to plan costs across a portfolio of any size.

Tiers start at $749/month for up to five partners (Managed Connect), $1,249/month for up to fifteen partners (Managed Connect Pro), and from $2,000/month for larger enterprise needs.

If your list isn't complete yet, don't wait. The detail level described in this article is a practical starting point. A rough list shared early is still more useful than a polished list shared late.

---

Frequently Asked Questions

How many trading partners should I expect to onboard at once?

Most teams find it practical to onboard in waves rather than all at once — prioritizing the highest-volume or most deadline-sensitive partners first. A managed EDI provider can help you sequence based on complexity and urgency once you share your full list.

What if I don't know my trading partner's technical contact yet?

Start with the business contact and ask them to connect you with their EDI or IT team. For larger distributors and wholesalers, many have EDI onboarding portals or published support contacts. Your managed EDI provider may also have existing relationships that can speed up that outreach.

Does every partner need a separate EDI map?

Not necessarily. Partners that use the same transaction sets with similar specifications can sometimes share a base map with minimal customization. The number of distinct maps you need depends on how much variation exists across your partner set — which is another reason to document connection methods and document types before the project begins.

What's the difference between a VAN and a direct AS2 connection?

A VAN (Value-Added Network) is a third-party intermediary that routes EDI transactions between trading partners. AS2 is a direct, point-to-point connection protocol. VANs typically add per-transaction fees and a routing layer; AS2 connections are direct but require both parties to manage the connection setup. Your trading partner list should note which method each partner prefers or requires, since it affects the technical setup on your side.

What if a partner says they don't do EDI?

It's worth documenting that too. Some partners are open to EDI implementation but haven't prioritized it; others have portal-based ordering that can sometimes be replaced with a structured connection over time. Knowing which partners are not yet EDI-capable helps you plan manual workarounds or partner development conversations in parallel with your main onboarding project — rather than discovering the gap during go-live coordination.

---

Next Steps

A complete trading partner list is the most practical thing you can do to accelerate an EDI project — and it doesn't require any technical work to assemble. Gather the fields outlined above, even if some are still blank, and you'll be in a much stronger position when onboarding begins.

Ready to move forward? Send us your trading partner list — share what you have and we'll help identify coverage, flag new mapping work, and map the fastest realistic path to go-live for each partner.