# 1 EDI Source EDI Integration with Infor VISUAL

> Source: https://netray.co/stack/1-edi-source-edi-integration-infor-visual
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Stack

## Short answer

1 EDI Source connects VISUAL to trading partners for EDI orders, invoices and ship notices. Their integration page says they use Infor ION connectors or point-to-point integration through Infor APIs, so you choose between a BOD-based design and a direct one.

## Erp

Infor VISUAL

## Erp Key

infor-visual

## On Prem

true

## Product

Infor VISUAL EDI Integration

## Vendor

1 EDI Source

## Category

EDI

## Integration

**Method:** Infor ION connectors

**Detail:** Documents flow between 1 EDI Source and VISUAL as ION BODs. This suits sites that already run ION for other integrations and want one messaging layer.

**Method:** Point-to-point through Infor APIs

**Detail:** The vendor also describes a direct integration through Infor APIs. This avoids an ION dependency, but you need to agree on which APIs, credentials and error handling are used.

## Data Flows

**From:** Trading partner via 1 EDI Source

**To:** Infor VISUAL

**Data:** Purchase orders and changes

**Trigger:** Partner transmits the document

**From:** Infor VISUAL

**To:** 1 EDI Source

**Data:** Advance ship notices

**Trigger:** Shipment released or confirmed

**From:** Infor VISUAL

**To:** 1 EDI Source

**Data:** Invoices

**Trigger:** Invoice posted to the customer

## Setup

### Choose ION or API

**Detail:** Decide whether to use ION connectors or direct API integration, based on what your team already maintains.

### List partners and documents

**Detail:** Document each trading partner, their document types and any special rules.

### Prepare master data

**Detail:** Load customer ship-to codes and partner part cross-references into VISUAL.

### Build the mappings

**Detail:** Agree with 1 EDI Source how EDI fields map to VISUAL order and invoice fields.

### Test end to end

**Detail:** Run test orders through to shipment and invoice for each partner.

### Go live with monitoring

**Detail:** Assign daily review of failed and held documents.

## Pitfalls

- Choosing ION without existing ION expertise adds an unplanned project.
- Direct API integration needs credential and version management that is often forgotten at upgrade time.
- Partner-specific requirements get added late and break generic mappings.
- Price, quantity and unit of measure differences between PO and VISUAL order lead to invoice disputes.
- Items with lot or serial tracking need careful ASN design.

## Ai Layer

### Mapping exception review

**Description:** A private assistant compares incoming EDI with VISUAL customer and part data and lists orders that cannot map, with suggested cross-reference entries for approval.

### Price and quantity mismatch checks

**Description:** Flag orders where PO price or unit differs from the VISUAL price list before they are released.

### Daily EDI summary

**Description:** Summarize overnight documents, failures and held items in plain language for the customer service lead.

## Alternatives

- SPS Commerce is another provider that integrates with VISUAL, using ION BOD XML.
- A few partners can sometimes be handled through their web portals without EDI.
- Use VISUAL's own import tools with flat files for low-volume, simple documents.

## Faq

### How does 1 EDI Source connect to VISUAL?

**Answer:** Their integration page says they use Infor ION connectors or point-to-point integration through Infor APIs. Which one fits depends on your ION footprint and IT preferences.

### Which documents are covered?

**Answer:** The page mentions EDI orders, invoices and ship notices between VISUAL and trading partners. Ask the vendor about other document types you need.

### Is it suitable for on-prem VISUAL?

**Answer:** VISUAL is commonly on-prem, and the vendor lists direct API as an option, so network access and security need to be designed with them.

### What would a private AI layer add?

**Answer:** It can triage failed EDI documents and check mappings against VISUAL data on your own servers. Any change to orders or master data stays behind human approval.

## Source

https://www.1edisource.com/integrations/infor-visual-erp/

## Search terms

infor visual edi integration 1 edi source, infor visual edi, visual erp edi provider, infor ion edi connector, edi ship notice infor visual

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json