EDI
Use EDI to automate purchasing, acknowledgements, shipping notifications, and invoicing between your ERP and ScanSource.
Most partners use EDI for transactional document exchange, while APIs provide real-time pricing and product information — and many use both.
EDI is part of Partner Direct (Path B), alongside APIs and feeds. If a quoting platform already connects for you, start with Popular platforms (Path A). Not sure? Start here explains platform vs Partner Direct.
Good to know: ScanSource does not charge per-document or set-up fees for EDI transactions.
Why use EDI?
EDI lets trading partners exchange business documents directly with ScanSource — without email, portals, CSV files, or manual order entry.
Eliminate: email orders · manual order entry · CSV transfers · re-keying invoices
Enable: automated ordering · shipment visibility · electronic invoicing · faster processing
Strong fit when
Your ERP already exchanges EDI · process is highly automated · large document volumes · organization already supports AS2 · need standardized purchasing and invoicing.
Audience hubs
AS2 Environment details (ISA/GS, endpoints, CNAMEs) and certificates are on this page. Open Customer EDI or Supplier EDI for role-specific onboarding, transaction specs, and FAQs.
Supported transactions
Exchanging documents with ScanSource brings immediate processing and responses you can use to update your systems.
Typical document flow: 850 → 855 → 856 → 810.
850 — Purchase Order
Automatically submit orders from ERP or procurement systems.
855 — Order Acknowledgement
Know when orders have been accepted.
856 — Advance Shipment Notice
Receive shipment details before delivery.
810 — Invoice
Synchronize billing information electronically.
AS2 connection and certificates
Production and Test AS2 identifiers, endpoints, and CNAMEs are listed below — the same Environment details as Customer EDI and Supplier EDI.
Download Test and Production certificates here. Open Customer EDI or Supplier EDI for role-specific onboarding steps, transaction specs, and FAQs.
Important: use published DNS hostnames
Configure trading partners against the SSL endpoints below (ediprod for Production, editst for Test). Prefer SSL; Non-SSL is listed for partners that require it.
Tip: Prefer DNS hostnames and FQDNs — do not hardcode IP addresses. ScanSource uses DNS load balancing and failover.
Production Environment (source of truth)
Primary trading-partner endpoint for live documents. Everything a new partner ultimately needs for go-live points here.
ISA/GS ID: ZZ / SCANSOURCENA
AS2 Identifier: ScanSourcePRD
AS2 Software: IBM Sterling B2B Integrator
SSL endpoint (current): https://ediprod.scansource.com:8560/inbound/as2
Non-SSL endpoint: http://ediprod.scansource.com:9560/inbound/as2
FQDN: ediprod.scansource.com
CNAME: ves-io-64ddc31a-4c66-4140-a632-544f5ec8de05.ac.vh.ves.io
Cert serial number (CA): 0d2b728162c6afff514bcfc8966ff998
Test Environment
Validation and onboarding only — not for live traffic. Use it to prove maps and connectivity before you cut over to Production.
ISA/GS ID: ZZ / SCANSOURCETST
AS2 Identifier: ScanSourceTST
AS2 Software: IBM Sterling B2B Integrator
SSL endpoint (current): https://editst.scansource.com:8560/inbound/as2
Non-SSL endpoint: http://editst.scansource.com:9560/inbound/as2
FQDN: editst.scansource.com
CNAME: ves-io-7d6c09bf-265a-49d1-9d05-d48e4f51f1d8.ac.vh.ves.io
Cert serial number (CA): 0583f93c4aa8ae2ae4abbeca38823411
EDI vs APIs
Real-time pricing / product search
APIs: Yes · Web Hooks: No · EDI: No
Order submission
APIs: Yes · Web Hooks: No · EDI: Yes
Shipment / invoice notification
APIs: Polling · Web Hooks: Yes · EDI: Yes
Many partners use both
APIs for pricing and availability; EDI for orders, ASN, and invoices. Platforms often use organization credentials for live price/ATP while ERP still runs EDI.