Switching EDI Software: A Small Supplier’s Guide to Leaving SPS Commerce or TrueCommerce

Switching EDI software is safe to do without losing compliance, as long as you run your old and new connections in parallel through at least two full order cycles before cutting over. The real risk isn’t the software — it’s the gap between when your old VAN stops talking to Walmart and your new one starts, which is exactly when 856s go missing and chargebacks show up.

Why Small Suppliers Outgrow SPS Commerce and TrueCommerce

Most suppliers don’t leave SPS Commerce or TrueCommerce because the EDI breaks. They leave because the pricing model was built for a 500-SKU enterprise vendor, not a company doing $2M in wholesale revenue with three retail partners. Per-document fees, mandatory “mapping” add-ons, and support tiers that gate basic troubleshooting behind a higher plan add up fast — often $400-$900/month for functionality a smaller platform delivers for a flat $150-$250.

The actual EDI requirements don’t change when you switch providers. You still need to generate an 856 ASN before the truck leaves, still need to respond to an 850 within the retailer’s window, and still need a 997 functional acknowledgment firing automatically. What changes is who’s charging you to do it.

What EDI Software for Small Suppliers Actually Needs to Do

Strip away the enterprise sales pitch and small supplier EDI software needs exactly four things: accept and translate 850 purchase orders, generate compliant 856 ASNs with correct carton/pallet hierarchy, process 810 invoices, and send/receive 997 acknowledgments automatically. Everything else — dashboards, “analytics,” multi-entity portals — is overhead you’re paying for whether you use it or not.

The Switching Timeline, Week by Week

Week	Activity	Risk if Skipped
1	Pull trading partner specs from current provider; document retailer-specific flags	Mis-mapped 856 ASNs on cutover
2	Configure new platform mappings for each retailer (Walmart, Target, Kroger each differ)	Rejected documents, EDI 997 errors
3-4	Run parallel testing — send real transactions through both systems	Undetected formatting errors
5	Retailer certification/re-certification test transactions	Delayed go-live, blocked POs
6	Cutover old connection, monitor first live order cycle closely	Chargebacks from missed ASN timing

Six weeks is realistic for a single-retailer switch. Add 1-2 weeks per additional retailer running parallel mappings.

Transaction Sets You Can’t Afford to Break During a Migration

The 850, 856, 810, and 997 aren’t just “EDI documents” — they’re the trail retailers audit when a chargeback dispute happens. If your new provider mis-maps the 856’s ship notice hierarchy (pack vs. carton vs. pallet) during the switch, Walmart’s system will flag a receiving discrepancy even if the physical shipment was correct. We break down exactly how these four documents interact in Walmart EDI 850, 856, 810 Explained — worth reviewing before you touch any mapping configuration.

AS2, SFTP, or VAN: Does Your New Provider Need to Match the Old Connection?

Not necessarily — but it has to match what the retailer requires, which isn’t always what your old provider used. Walmart mandates AS2. Target accepts AS2 or SFTP depending on the division. Kroger still runs a lot of traffic through VAN relationships. If you’re switching software, this is the moment to confirm connection method requirements fresh rather than assuming your new vendor replicates the old setup automatically. We cover the tradeoffs in detail in AS2 vs SFTP vs VAN.

Retailer	Required Connection	Transaction Sets Mandatory	Typical Chargeback for ASN Error
Walmart	AS2	850, 856, 810, 997	$75-$250 per violation
Target	AS2 or SFTP	850, 856, 810, 856, 997	Up to 3% of PO value
Kroger	VAN or AS2	850, 855, 856, 810	Flat fee + vendor scorecard hit

Common Mistakes That Trigger Chargebacks During a Switch

The most expensive mistake is running the cutover on a live PO instead of a test batch — if the new 856 mapping has even one wrong qualifier code, you’ll find out when the chargeback invoice arrives, not before. Second most common: forgetting that Target’s EDI setup differs by division, which we detail in the Target EDI setup guide. Third: assuming your new provider auto-generates 997s — some platforms require you to manually enable acknowledgment rules per trading partner.

FAQ

How long does it take to switch EDI software without breaking compliance?

Plan for 4-6 weeks per retailer, including parallel testing and re-certification. Rushing cutover is the single biggest cause of post-switch chargebacks.

Can I switch EDI software without re-certifying with Walmart or Target?

No. Retailers require re-certification test transactions whenever your trading partner ID or connection method changes, even if the transaction sets themselves stay the same.

Is SFTP a valid replacement for AS2 when switching providers?

Only if the retailer allows it. Walmart requires AS2 outright; Target permits SFTP in some divisions. Confirm per retailer before assuming your new platform’s default connection will work.

What’s the biggest hidden cost of staying with an enterprise EDI provider?

Per-document and per-trading-partner fees that scale with order volume rather than complexity — a supplier doing 200 POs a month often pays the same support tier as one doing 2,000.

Do I need new onboarding with each retailer after switching software?

Yes, typically a shortened version — new ISA/GS qualifiers and a round of test transactions, not a full onboarding from scratch. Full new-vendor setup only applies to brand-new retailer relationships, covered in New Walmart Vendor EDI Setup.

Last verified: October 21, 2026