Distribution integration
Border States EDI for suppliers
A guide for suppliers to Border States: verified company facts, what Border States publishes about EDI, the documents building products distributors typically exchange, and what is still to confirm.
Overview
Understanding Border States integration
Who this is for: Manufacturers and suppliers of electrical, plumbing, HVAC and building products that sell through Border States, and their EDI, order management and finance teams.
Border States Industries, Inc. (Border States Electric) is an employee-owned distributor of electrical, utility and industrial supplies. Its website is borderstates.com.
Border States does not publish supplier EDI requirements on its public website: we found no supplier EDI specification, implementation guide or onboarding page when we checked on 7 November 2026. Suppliers usually receive a distributor's requirements during setup, from its purchasing or EDI team, and they can differ by program, division and region.
Distributors of electrical, plumbing, HVAC and building products commonly send purchase orders by EDI and expect an order acknowledgment, an advance ship notice and an invoice in return. Item and price catalogs are often exchanged as well, and orders may ship to a branch, a distribution center or straight to a job site. Branch and ship-to details, units of measure and pricing are where most mismatches start. The documents, flow and connection options on this page describe that general practice. They are not Border States' published requirements; confirm each one with Border States before you build maps or test.
Workflows
Typical Border States business workflows
General guidance: typical flows in this industry, not Border States' published process.
Typical order to invoice
- 1Receive 850 purchase order
- 2Send 855 acknowledgment
- 3Ship to branch or job site
- 4Send 856 ship notice
- 5Send 810 invoice
Documents and APIs
Border States documents by program
General guidance. We could not verify Border States' EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Border States' confirmed requirements. Confirm the list, versions and programs with Border States.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Program | Status | Purpose |
|---|---|---|---|---|---|
| 850 | Purchase Order | From Border States | Not stated | General guidance | Typically how the distributor orders for its branches, warehouses or job sites. |
| 855 | Purchase Order Acknowledgment | To Border States | Not stated | General guidance | Typically confirms quantities, prices and ship dates. |
| 856 | Ship Notice/Manifest | To Border States | Not stated | General guidance | Typically lists what is on each shipment and where it is going. |
| 810 | Invoice | To Border States | Not stated | General guidance | Typically bills for what shipped, against the purchase order. |
| 832 | Price/Sales Catalog | To Border States | Not stated | General guidance | Often used to share item numbers, descriptions and prices. |
| 846 | Inventory Inquiry/Advice | To Border States | Not stated | General guidance | Often used to report stock available to ship. |
Connectivity
How companies connect
AS2 or SFTP
Many distributors exchange EDI files directly over AS2 or SFTP. Confirm which methods Border States accepts.
General guidance
EDI network (VAN)
Many suppliers connect through a value-added network that delivers files to and from the distributor.
General guidance
Supplier web portal
Some distributors offer a supplier portal for orders, invoices or onboarding; a login is usually required.
General guidance
Challenges
Common integration challenges
Branch and ship-to details
Orders for many branches and job sites need the right ship-to on every acknowledgment, ship notice and invoice.
Units and pricing
Units of measure and contract prices must match the distributor's records, or invoices are held.
Local operating companies
Groups with many local companies may run different setups, so confirm which locations a setup covers.
Requirements not public
Border States does not publish its supplier EDI requirements, so the document set and rules must be confirmed with Border States before work starts.
Automation options for Border States suppliers
Four ways to automate. One foundation.
ECOM helps you automate them, meet Border States' labeling and ship notice requirements, and see what needs action. Border States sets its program's rules; ECOM confirms which options fit yours.
-
Fully Automated EDI/API
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/API -
WebEDI
Receive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDI -
SmartConvert
Convert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvert -
WebConnect
Automate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
PRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
Compliance and actionable visibility
Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.
Connect Border States documents to your ERP
ECOM connects the documents Border States asks for with your ERP and warehouse systems, so orders post without re-keying and ship notices and invoices come from the data you already hold.
Wholesale Distribution
See how ECOM supports EDI across wholesale distribution.
ServiceFully Managed EDI
Have ECOM run your EDI connections, monitoring and partner changes.
General EDI flow
How EDI with Border States typically works
This page does not include Border States' EDI specification, so here is the general flow most buyers and suppliers follow. It describes common industry practice, not Border States' requirements: the documents, their order and the timing vary by partner and program.
-
850 Purchase order
From Border States
The buyer sends the order: items, quantities, prices, ship-to and requested dates.
-
855 Order acknowledgment
From you to Border States
You confirm, change or reject the order, where the partner asks for it.
-
856 Advance ship notice
From you to Border States
You tell the buyer what is on the shipment, with the carton and label details the buyer needs to receive it.
-
810 Invoice
From you to Border States
You bill for what shipped, in the format the buyer's payables system expects.
-
997 Functional acknowledgment
Both directions
Each side confirms that every file it received was readable. A rejected file is corrected and resent.
From first contact to live orders
- Get the specification
Ask Border States for its EDI or API specification, usually through its supplier portal or onboarding contact.
- Choose the connection
Agree how files move: AS2, SFTP, a VAN or an API, and how each side identifies itself.
- Map to your systems
Map each document between the partner's format and your ERP, warehouse or order system.
- Test and certify
Exchange test documents until the partner accepts them. Many partners require this before the first live order.
- Go live and monitor
Start with live orders and watch every document, so a rejection is fixed before it becomes a late shipment or a deduction.
Need the specification?
Some trading partners keep their EDI and API specifications private and share them only with authorized suppliers, for security reasons. You are welcome to contact ECOM. We will see whether we can share the specification with you; each request is reviewed case by case, and sharing depends on the partner's rules. Do not send passwords or EDI identifiers with your request.
Next step
Get help with your Border States program
Each request goes to an ECOM EDI specialist with Border States' name attached, so the reply starts from your program.
-
Review Border States' requirements
Send us Border States' guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements review -
Connect Border States to your ERP
Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.
Discuss ERP integration -
Testing and certification
Build, test and certify each Border States document, then go live with monitoring from the first file.
Plan testing and certification -
Shipping labels and ASNs
Labels and ship notices that match Border States' rules, to help avoid receiving problems and compliance deductions.
Review shipping compliance
Border States integration FAQs
Does Border States publish supplier EDI requirements?
We found no supplier EDI specification or onboarding page on Border States' public website when we checked on 7 November 2026. Suppliers usually receive the requirements from Border States during setup.
Which EDI documents do suppliers to Border States usually exchange?
Suppliers to building products distributors typically exchange the 850, 855, 856, 810, 832, 846 documents listed on this page. That is general practice, not Border States' published list; confirm the set with Border States.
What is not yet known about EDI with Border States?
Which EDI documents Border States requires, the X12 version, the connection method, the testing steps and any labeling or compliance rules were not found in public sources.
Can ECOM help suppliers set up EDI with Border States?
Yes. Once Border States provides its requirements, ECOM can map, test and run the documents with your ERP. This page is an integration guide and does not indicate a partnership with Border States.
Sources and accuracy
This guide summarizes publicly available information as of November 2026. Border States sets its own requirements and can change them at any time; your Border States implementation guide, supplier portal or account contact is the authoritative source for your program.
- Border States, company website Official Border States source
Border States is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
More distribution integration guides
84 Lumber EDI
A guide for suppliers to 84 Lumber: verified company facts, what 84 Lumber publishes about EDI, the documents building products distributors typically exchange, and what is still to confirm.
ABC Supply EDI
A guide for suppliers to ABC Supply: verified company facts, what ABC Supply publishes about EDI, the documents building products distributors typically exchange, and what is still to confirm.
AFC Industries EDI
A guide for suppliers to AFC Industries: verified company facts, what AFC Industries publishes about EDI, the documents industrial distributors typically exchange, and what is still to confirm.
Airgas EDI
A guide for suppliers to Airgas: verified company facts, what Airgas publishes about EDI, the documents industrial distributors typically exchange, and what is still to confirm.
AMCON Distributing EDI
A guide for suppliers to AMCON Distributing: verified company facts, what AMCON Distributing publishes about EDI, the documents foodservice and grocery distributors typically exchange, and what is still to confirm.
Applied Industrial Technologies EDI
A guide for suppliers to Applied Industrial Technologies: verified company facts, what Applied Industrial Technologies publishes about EDI, the documents industrial distributors typically exchange, and what is still to confirm.
Request Border States integration assistance
Tell us about your Border States program, documents and ERP. We will outline the connection, mapping and testing plan.