Supplier and vendor access
Each supplier, 3PL and vendor connection has its own account and limited scope, so one compromised credential cannot reach other partners' data.
Retail integration
A guide for suppliers connecting with Capitol Lighting, covering the documents exchanged, the main program rules, testing and ERP integration.
At a glance
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Capitol Lighting program or a customer relationship.
Tell us which documents you exchange with Capitol Lighting, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Capitol Lighting.
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
Overview
Who this is for: Suppliers that sell to Capitol Lighting, and the EDI, logistics and finance teams that support them.
Capitol Lighting is a US lighting retailer. Suppliers that trade with Capitol Lighting electronically exchange documents such as the 850 purchase order, 855 purchase order acknowledgment, 856 ship notice/manifest, 810 invoice and 820 payment order/remittance advice. This page summarizes how that exchange works from the supplier's side, so your team can scope the work before mapping starts.
The program uses X12 4030. Order types include store orders and direct to customer. Each order type can change which documents apply and how locations, labels and invoices are handled, so it helps to confirm which ones you will supply before you build anything.
Most of the effort goes into keeping your ERP, warehouse and shipping data consistent with what each document says. Ship notices, labels and invoices need to agree with the original order, and any rule that applies only to one order type needs its own handling in your maps. Capitol Lighting sets its own requirements and can change them, so treat your account contact and current guide as the final word.
Program summary
A summary in ECOM's own words. Requirements vary by program and change over time, so confirm the details with Capitol Lighting during setup.
Workflows
A typical flow built from the documents below; your own program may differ.
Documents and APIs
Documents used in Capitol Lighting's EDI program, seen from the supplier's side. Which ones apply depends on your program, so confirm the list with Capitol Lighting.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Status | Purpose |
|---|---|---|---|---|
| 850 | Purchase Order | You receive from Capitol Lighting | Program document | Places an order for goods. |
| 855 | Purchase Order Acknowledgment | You send to Capitol Lighting | Program document | Confirms, changes or rejects an order. |
| 856 | Ship Notice/Manifest | You send to Capitol Lighting | Program document | Describes a shipment before it arrives. |
| 810 | Invoice | You send to Capitol Lighting | Program document | Bills for what shipped. |
| 820 | Payment Order/Remittance Advice | You receive from Capitol Lighting | Program document | Explains what a payment covers. |
Connectivity
Direct internet connections such as AS2 or SFTP are common ways to exchange EDI documents. Confirm the options with Capitol Lighting.
General guidance
Many suppliers connect through an EDI provider or network that manages the connection with Capitol Lighting.
General guidance
Challenges
Different order types can need different maps, locations and labels, so identify each Capitol Lighting order type before mapping.
Ship notices, labels and invoices need to match the order and each other, or they can cause receiving and payment problems.
Requirements change. Keep a process for picking up new Capitol Lighting rules and retesting affected documents.
Automation options for Capitol Lighting suppliers
ECOM helps you automate them, meet Capitol Lighting's labeling and ship notice requirements, and see what needs action. Capitol Lighting sets its program's rules; ECOM confirms which options fit yours.
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/APIReceive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDIConvert 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 SmartConvertAutomate 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.
Learn more about WebConnectPRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
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.
ECOM can connect Capitol Lighting documents with ERP and warehouse systems, so ship notices and invoices are generated from your own order and shipping data.
Zero Trust for supplier data exchange
Supplier exchanges with Capitol Lighting carry orders, ship notices, invoices and item data. A Zero Trust design assumes no connection, file or user is safe by default.
ECOM has implemented Zero Trust EDI and Zero Trust MFT in retail.
For supplier exchanges this means each supplier and vendor connection has its own scope, orders, ship notices and invoices are verified on arrival, late or altered files are noticed early, and the transfer log helps answer deduction and security-review questions.
Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.
Business outcome: A lost or reused credential affects one partner, not all of them.
Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.
Business outcome: A mistake or compromise in one account stays limited to what that account could reach.
Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.
Business outcome: Outside connections do not land directly on your internal systems.
Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.
Business outcome: Less exposure if a file is intercepted or a file store is reached.
Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.
Business outcome: Fewer outages caused by an expired certificate or key.
Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.
Business outcome: Late, missing or failed files are noticed early, before they hold up late shipments or deductions.
Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.
Business outcome: You can answer who sent what and when, for your own audits and partner reviews.
Each supplier, 3PL and vendor connection has its own account and limited scope, so one compromised credential cannot reach other partners' data.
Documents are verified when they arrive and every transfer is logged, so a missing or altered file shows up quickly.
Replace shared logins and open folders with named accounts, reviewed on a schedule you set.
Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Capitol Lighting may set its own security requirements, which come first.
Talk to an EDI/API Expert about Zero Trust Managed file transferSecure proxy and DMZ designSecurity at ECOM
Next step
Each request goes to an ECOM EDI specialist with Capitol Lighting's name attached, so the reply starts from your program.
Send us Capitol Lighting's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements reviewOrders in, ship notices and invoices out, from the ERP and warehouse systems you already run.
Discuss ERP integrationBuild, test and certify each Capitol Lighting document, then go live with monitoring from the first file.
Plan testing and certificationLabels and ship notices that match Capitol Lighting's rules, to help avoid receiving problems and compliance deductions.
Review shipping complianceThe documents in this guide are the 850, 855, 856, 810 and 820. Which ones apply depends on your program, so confirm the list with Capitol Lighting during setup.
This guide reflects X12 4030. Versions can differ by document and can change, so confirm the release for each document before you build your maps.
Timing depends on your systems, the number of documents and the partner test plan. Mapping and testing each document is usually the largest part of the work.
This page is an integration guide and does not indicate an approval or partnership with Capitol Lighting. ECOM can help you build and test your connection.
This guide describes Capitol Lighting's program in ECOM's own words as of November 2026. Capitol Lighting sets its own requirements and can change them at any time; your Capitol Lighting implementation guide, supplier portal or account contact is the authoritative source for your program.
Capitol Lighting is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
How EDI and API integration with The Tile Shop typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with The Tile Shop.
A guide for suppliers connecting with The Vitamin Shoppe, covering the documents exchanged, the main program rules, testing and ERP integration.
How EDI and API integration with Tiffany & Co. typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Tiffany & Co.
How EDI and API integration with TJ Maxx typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with TJ Maxx.
How EDI and API integration with TJX Companies typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with TJX Companies.
How EDI and API integration with Tokyo Central typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Tokyo Central.
Tell us about your Capitol Lighting program, documents and ERP. We will outline the connection, mapping and testing plan.