EDI OpenText Integration

EDI OpenText Integration

Electronic Data Interchange for enterprise B2B transactions with retail partners

Connect OmniOrders to OpenText EDI and exchange business documents automatically with retail partners and suppliers. Purchase orders flow in, invoices and Advanced Shipping Notices (ASNs) flow out—no manual data entry or paper-based processes.

Quick Setup

You’ll need an OpenText EDI account and connection details from your EDI provider or trading partner. Setup typically takes 15–20 minutes.

---

Why Connect EDI OpenText?

Connecting EDI OpenText to OmniOrders means purchase orders from retailers arrive automatically, invoices and ASNs send out without manual work, and your B2B transactions stay compliant with retail partner requirements—all from one central order management system.

Automated PO Import

Purchase orders (850) from retail partners flow directly into OmniOrders—no re-keying or email attachments.

Invoice & ASN Export

Generate and send invoices (810) and Advanced Shipping Notices (856) automatically when orders ship.

Trading Partner Compliance

Meet retailer EDI requirements (Walmart, Target, and others) without maintaining separate systems.

Centralized B2B Orders

Manage EDI orders alongside your eCommerce channels in one OmniOrders dashboard.

---

Before You Start

Gather these items before connecting:

OpenText EDI Account

You need an active OpenText EDI subscription or connection through your EDI provider. Contact OpenText or your trading partner for access.

Connection Details

Your EDI connection credentials: trading partner IDs, mailbox or VAN details, and document type mappings (850, 810, 856, etc.).

Trading Partner Requirements

Know which retailers or suppliers you’ll connect to—each may have specific EDI document and format requirements.

---

Connect Your EDI OpenText Account

1. Go to Integrations

   In OmniOrders, click Integrations in the main menu, then click Add Integration

2. Select EDI OpenText

   Find EDI OpenText in the list (under EDI & B2B) and click Connect

3. Enter Connection Details

   You’ll need:

   • Trading Partner ID (or your EDI identifier)
   • Connection credentials (from OpenText or your EDI provider)
   • Document mappings (which EDI types to send and receive)

   What We Exchange

   OmniOrders exchanges only order and fulfillment data—purchase orders, invoices, and ASNs. We never access payment or sensitive customer information.

4. Configure Document Types

   Choose which EDI documents to sync:

   • 850 (Purchase Order): Import orders from retail partners
   • 810 (Invoice): Send invoices when orders ship
   • 856 (ASN): Send Advanced Shipping Notices for fulfillment
   • 997 (Functional Acknowledgment): Confirm document receipt (if required)

5. Map Locations

   If you have multiple warehouses, map them to your EDI fulfillment locations for accurate routing.

6. Start Sync

   Click Start Sync to begin receiving purchase orders. The first sync may take a few minutes depending on your trading partner setup.

First Sync

The first connection imports recent purchase orders from your EDI mailbox. After that, new POs flow in as they arrive.

---

What Gets Synced?

The EDI OpenText integration exchanges standard X12 EDI documents: purchase orders flow into OmniOrders, and invoices plus ASNs flow out when you fulfill—keeping your B2B transactions automated and compliant.

Inbound (Into OmniOrders)

• 850 (Purchase Order): Order details, line items, quantities, ship-to addresses, and requested dates
• 855 (PO Acknowledgment): Optional—send acknowledgments back to confirm order receipt
• 997 (Functional Acknowledgment): System-level confirmations (handled automatically)

Outbound (From OmniOrders)

• 810 (Invoice): Generated when orders ship—includes line items, quantities, and pricing
• 856 (ASN): Advanced Shipping Notice with tracking, carrier, and expected delivery
• 855 (PO Acknowledgment): Optional—confirm order acceptance to the trading partner

Fulfillment

• Tracking numbers and carrier info
• Shipment status updates
• Delivery date notifications

---

Managing Your Connection

View Sync Status

Check if everything is syncing correctly:

1. Go to Integrations → EDI OpenText (or Services → EDI)
2. View the sync dashboard showing:
   • Last sync time
   • Documents received and sent
   • Any errors or warnings

Pause Syncing

Need to temporarily stop syncing?

1. Open your EDI OpenText integration settings
2. Toggle Sync Active to OFF
3. Syncing stops immediately (you can resume anytime)

Update Settings

Change what syncs:

1. Click Settings on your EDI integration
2. Toggle document types on/off
3. Update trading partner mappings if needed
4. Click Save Changes

Update Connection Credentials

If you need to change your EDI credentials:

1. Obtain new credentials from OpenText or your EDI provider
2. Update them in OmniOrders integration settings
3. The connection will resume automatically

---

Common Questions

How often does it sync?

Purchase orders sync as they arrive in your EDI mailbox. Invoices and ASNs send automatically when orders ship.

Which retailers are supported?

EDI works with any retailer or supplier that uses standard X12 EDI (Walmart, Target, and many others). Your specific partners depend on your OpenText setup.

What about existing orders?

We can import recent purchase orders during initial setup. Older orders may require a manual import—contact support if needed.

Is my data secure?

Yes. EDI connections use secure protocols and we encrypt all data in transit and at rest.

---

Troubleshooting

Purchase Orders Not Syncing

Problem: New EDI purchase orders aren’t appearing in OmniOrders

Solutions:

• Check that Order Sync is enabled in integration settings
• Verify your connection credentials are valid and not expired
• Confirm your EDI mailbox is receiving documents (check with OpenText)
• Look for error messages in the sync log
• Try clicking Force Sync to trigger a manual refresh

Invoices or ASNs Not Sending

Problem: Invoices or ASNs aren’t being sent to trading partners

Solutions:

• Confirm Invoice and ASN export are enabled in settings
• Verify the order has shipped and tracking is entered
• Check that trading partner IDs and document mappings are correct
• Look for validation errors in the sync log (e.g., missing required fields)

Connection Expired

Problem: EDI integration shows “Connection Expired” or “Authentication Failed”

Solutions:

• Verify your OpenText credentials are still valid
• Check if credentials were rotated or revoked by your EDI provider
• Update credentials in OmniOrders integration settings
• No data is lost—syncing resumes after reconnecting

---

Best Practices

For New Users

1. Start with One Partner: Connect one trading partner first to verify the flow
2. Verify Mappings: Ensure your SKUs and product codes match EDI requirements
3. Test in Sandbox: Use a test environment if available before going live
4. Monitor Ship Dates: EDI orders often have strict ship-by dates—track them closely

For B2B Sellers

1. Centralize Orders: Let OmniOrders be your source of truth for all channels
2. Use Consistent SKUs: Keep SKUs identical across EDI and eCommerce for accurate matching
3. Send ASNs Early: Send Advanced Shipping Notices as soon as orders ship to meet retailer SLAs
4. Track Compliance: Monitor acknowledgment and error rates to stay compliant

For High-Volume Operations

1. Enable Auto-Fulfillment: Let OmniOrders automatically process EDI orders when ready
2. Sync Tracking Immediately: Enter tracking as soon as orders ship
3. Monitor Sync Logs: Check regularly for 997 errors or document rejections
4. Plan for Peaks: During busy seasons, ensure your EDI provider can handle volume

---

Need More Help?

Contact Support

Our team is here to help with setup, troubleshooting, or any questions. Get Support →

OpenText Documentation

Check OpenText’s documentation for EDI document specifications and trading partner requirements.

More Integrations

Explore other platforms and integration options. View Integrations →

---

Pro Tip

Keep your product catalog and SKUs in sync with your EDI trading partner requirements before connecting—matching product codes from the start prevents mapping errors and rejections.