EDI Production Cutover Checklist (Free, Export)

0%

0 of 28 items complete

10 critical items still open - these are the highest-risk gaps.

Download checklist:

Connectivity and envelope

Partner confirmed ISA05, ISA06, ISA07, ISA08 values in writingCRITICALISA and GS padding checked at exactly 15 charactersAS2, SFTP or VAN credentials and certificates tested and not near expiryCRITICALFirewall and IP allow lists in place for production endpointsISA15 switched from T to P only on the agreed cutover dateCRITICALControl number counters configured and set to start without overlap with testDelimiters and character set confirmed with partner

Maps and data

Every inbound and outbound transaction set tested with real examplesCRITICALUnit of measure cross reference loaded for the partnerCustomer part number to item cross reference completeShip-to location table loaded and validated against partner listCRITICALPricing and currency rules tested on sample ordersPartner-specific required segments (REF, DTM, N1) verified against guideError handling for unmapped codes sends an alert, not a silent dropCRITICAL

Acknowledgments and compliance

997 or 999 received and matched for each test documentCRITICAL855, 856 and 810 timing rules documented (hours after order, before shipment)ASN and label formats approved by the partnerCRITICALGS1-128 label data matches ASN data for each packChargeback rules and compliance scorecard reviewed with the partnerDuplicate document detection enabledRetention period for EDI files agreed and configured

Monitoring and fallback

Alerts for failed transmissions and missing 997s routed to a named personCRITICALDaily check for orders received versus orders in ERPManual fallback documented (email PO, portal) with owner and triggerCRITICALPartner contact list with escalation path for both sidesFirst five production documents reviewed manually end to endRollback step defined if the partner reports a critical issueHypercare window and owner agreed for the first two weeks

Every critical item should be checked before the switch. If a critical item is open, agree a dated plan with the partner or delay cutover.

Partner onboarding register

An optional review of how onboarding status could be tracked against your ERP and EDI monitoring.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work through the groups with the partner on a call, not alone. Tick items as you verify them with evidence: a test file, a 997, an email from the partner. The critical items are those that cause lost orders, rejected shipments or financial penalties if wrong. Export the finished list to PDF and keep it with the partner record as the cutover sign-off.

Plan the first week

The first production documents deserve manual review. Compare what the partner sent with what arrived in the ERP, and compare each outbound document with the ERP source. Agree the daily check with the partner, and watch for the first 997 on each document type. Do not start a second partner cutover until the first has stable traffic and the compliance dashboard is clean.

Review the first five documents of each type manually.
Confirm 997 receipt within the agreed window.
Track rejected documents by cause.
Hold off new maps during the first week.

Common mistakes

Teams often go live on the technical test alone and forget the business side: the ship-to table, the label data, the invoice timing. Another frequent gap is monitoring: a failed AS2 session at night means orders arrive late and nobody notices until the buyer calls. Make sure someone owns the alert, and that the manual fallback has been rehearsed at least once.

Frequently Asked Questions

How long should EDI testing last?

It depends on the number of transaction sets and the partner. A single 850 and 810 pair may take a few days, while full retail programs with ASN and labels often take several weeks. Plan time for partner review cycles.

Who approves going live?

Both sides. Typically the partner's EDI team approves the technical test and the business owner approves the order and shipping flow. Keep the approval in writing.

Should test and production use different control numbers?

Use separate counters or ranges. A production file reusing a test ISA13 may be dropped as a duplicate, and mixing them makes troubleshooting harder.

What is hypercare for EDI?

A short period after go-live, usually one to two weeks, when someone checks every document and alert daily and the partner is on call. It ends when error rates stabilize.

If cutovers are tracked in emails and spreadsheets, Netray can help set up a partner onboarding register that links checklist status to your ERP and EDI monitoring.

Talk to an Expert Explore More Free Tools

Related Tools

Developer Tools

More Supply Chain & Inventory tools

See all

EDI Trading Partner Production Cutover Checklist