Customer 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
Choose EDI when your ERP already exchanges X12/AS2 and you need standardized document exchange with ScanSource.
EDI is a strong fit when:
• Your ERP already exchanges EDI documents
• Your process is highly automated
• You exchange large document volumes
• Your organization already supports AS2
• You need standardized purchasing and invoicing
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.
EDI vs APIs
Use this comparison to choose the right tool for each need — or combine them. Web Hooks are included for event-driven status.
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
Polling: your application requests updates on a schedule. Web Hooks and EDI push notifications when events or documents are ready.
APIs for pricing and availability; EDI for orders, ASN, and invoices. Quoting platforms (Popular platforms) often use organization credentials from Profile → Organization Subscription Information for live price/ATP, while ERP still runs EDI.
How Onboarding Works
Follow this path so you always know what happens next.
1. Contact the ScanSource EDI team to begin trading-partner setup.
2. Exchange AS2 information (IDs, URLs, certificates) using the Production and Test settings below.
3. Configure the Test environment (validation and onboarding only). Open firewalls using DNS hostnames — not hardcoded IPs.
4. Validate transactions (typically 850/855 first, then 856/810).
5. Move to Production (source of truth for live documents — use the Production SSL endpoint and FQDN below).
6. Exchange live documents and monitor acknowledgements / MDNs.
You'll need:
• EDI translator or gateway
• AS2 capability
• Trading partner identifier
• Firewall access for ScanSource connectivity
• Test contact
• Production support contact
Tip: If you also need APIs or platform credentials, complete Start here through Active status first. Organization credentials appear under Profile → Organization Subscription Information — never use portal Try it Primary/Secondary keys for production or platforms.
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
Certificates and Security
Use Production certificates with Production, and Testing certificates with Testing.
Production
Testing
Technical Requirements
Trading partners should open firewalls for the ScanSource IP address range to receive transactions.
Tip: Use published DNS hostnames only — never hardcode IP addresses. ScanSource uses DNS load balancing and failover; hardcoded IPs cause connection errors.
Signing algorithm: SHA256 preferred; SHA1 allowed
Encryption algorithm: Triple DES 168
Frequently asked questions
Which EDI page should I use?
Customer EDI and Supplier EDI are publicly available connection guides. Choose the page that best matches your role and onboarding scenario — customers use Customer EDI; suppliers/vendors use Supplier EDI; Internal Developers may use either.
Which AS2 URL should new partners use?
Use the current SSL endpoint for each environment (ediprod for Production, editst for Test). Prefer SSL; Non-SSL is listed when a partner requires it. Open firewalls by FQDN/CNAME — never hardcode IPs.
Can I connect with a hardcoded IP address?
No. Use DNS hostnames. ScanSource uses DNS load balancing and failover; hardcoded IPs cause errors.
Which certificate should I download?
Use Testing certificates with the Test environment and Production certificates with Production. Self-signed and CA options are provided for each.
Do you charge for EDI?
ScanSource does not charge per-document or set-up fees for EDI transactions.
Should I use EDI, APIs, Web Hooks, or a platform?
EDI is Path B (Partner Direct) when your ERP does AS2 and you need automated document exchange. Use APIs for real-time pricing and product search, Web Hooks for event-driven status, and Popular platforms (Path A) when a connector already covers quoting.
What documents should we test first?
Most partners validate 850 and 855 first, then add 856 and 810 before production cutover.
What ERPs and gateways commonly use EDI?
EDI is mainstream for VARs, distributors, and enterprise buyers — not a niche path.
ERP / finance: NetSuite · SAP · Oracle · Microsoft Dynamics · Acumatica · Sage
EDI / B2B gateways: IBM Sterling · Cleo · OpenText · SPS Commerce
Contact the EDI Team
To start onboarding or get help with AS2 connectivity, certificates, or document mapping, contact the ScanSource EDI / B2B team.
EDI / B2B setup: b2brequest@scansource.com — include your company name, ScanSource customer number, AS2 identifier, target environment (Test or Production), and a short description of the issue or request.
Portal access delays (Submitted vs Active): b2bsupport@scansource.com — or see Start here.
Ready to start EDI?
Contact the EDI team above to begin onboarding. Or return to Start here if you still need Active status for APIs or platform credentials.
Start here · APIs · Web Hooks · Popular platforms · Customer Journeys