South Moon Under EDI
integration guide.
Plan your South Moon Under EDI integration using 3 listed document types across 1 channel. Compare channels, map business records and test the operational handoff.
Adopted by fast-scaling companies moving mission-critical data in real time
Implementation guide
South Moon Under: EDI implementation plan
Build a reliable EDI workflow for South Moon Under. Use 3 document types across 1 channel to plan record mapping, prevent duplicate processing and reconcile results in your business systems.
The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 850 Purchase OrderListed on 1 channel: South Moon Under (via KWI) | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 856 Ship Notice ManifestListed on 1 channel: South Moon Under (via KWI) | shipment notice (ASN) shipment, order, package and item references |
|
| X12 810 InvoiceListed on 1 channel: South Moon Under (via KWI) | accounts-receivable or accounts-payable invoice invoice number, purchase order and invoice line |
|
Implementation steps
-
Choose the trading account and channel
Choose among South Moon Under (via KWI). Confirm the business unit and account before copying a mapping from another channel.
-
Map records and assign owners
Start with purchase order or sales order, shipment notice (ASN), accounts-receivable or accounts-payable invoice. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.
-
Test a complete exchange
Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the South Moon Under production handoff and save the results of each approved test.
-
Check results after launch
Match records between systems using buyer purchase order, order line and trading-party identifiers. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Go-live checklist
- The required X12 documents, versions and sample files are agreed.
- Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
- Delivery receipts, document validation and business responses have monitoring and a named owner.
- Tests cover duplicates, partial processing and reconciliation with realistic business records.
Document catalog
EDI documents listed for South Moon Under
3 transactions across 1 channel.
Document flow
Example document relationships for South Moon Under
Where each document sits in its trading cycle, based on the 3 document types listed for South Moon Under across 1 channel. These are example relationships; the trading agreement determines the required sequence.
Order-to-cash
Some example steps listed- 850 Purchase Order
- 855 Purchase Order Acknowledgment not listed for South Moon Under
- 856 Ship Notice Manifest
- 810 Invoice
Network context
South Moon Under channel references for KWI
These network names are derived from the listed South Moon Under channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method.
KWI
1 channel · 1 trading partner in the catalog
South Moon Under channel on this network: South Moon Under (via KWI)
- 810 1 ch
- 850 1 ch
- 856 1 ch
Still with a legacy EDI vendor? We cover the buyout.
Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.
Check your eligibility for the EDI migration fundSecurity teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related references
Partners with related document listings
Compare document requirements for similar business processes.
Showing 21 of 48 references
Browse the full directoryFAQ
South Moon Under EDI questions
Which EDI documents are listed for South Moon Under?
X12 850 Purchase Order; X12 856 Ship Notice Manifest; X12 810 Invoice. Confirm which documents, directions and versions apply to your account.
How should I choose the South Moon Under EDI channel?
The directory lists 1 channels for South Moon Under, including South Moon Under (via KWI). Match the channel to your actual trading relationship and compare its document list before reusing a mapping.
Which identifiers should the South Moon Under mapping preserve?
For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 856 Ship Notice Manifest, use shipment, order, package and item references. Use the partner guide to locate these values and check their allowed formats.
Does a successful EDI receipt mean South Moon Under accepted the business document?
Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.
What should be tested before launching South Moon Under EDI?
Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.




