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.
Manufacturing · EDI and API connectivity
How EDI and API integration with STARK typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with STARK.
About STARK
STARK is listed in ECOM's trading partner directory in the manufacturing category (segment: Rugs and floor coverings). Suppliers, vendors, carriers and customers that trade with STARK are often asked to exchange orders, shipment notices, status messages and invoices electronically instead of by email, phone or paper.
People searching for "STARK EDI", "STARK EDI requirements", "STARK trading partner" or "STARK vendor onboarding" usually need to know three things: which documents to exchange, how to connect, and how to get the data into their own systems. ECOM does not publish STARK's own EDI specification on this page, and nothing here is a statement of its requirements. Ask us, and an EDI specialist will review your program with you.
EDI, API, browser-based EDI, ERP integration and managed services from one team. Where ECOM is already certified for your customer's program you can trade within hours; otherwise within 2 business days.
Communication and connectivity
ECOM supports any-to-any connectivity: whatever protocol, format or portal your trading partner uses, we translate it to what your systems use. One connection layer replaces a separate project for each partner.
Secure file exchange with any trading partner, through direct AS2, SFTP or FTPS connections or through the value-added network the partner already uses.
Real-time API connections for order, shipment, inventory and status data, including API-to-EDI translation in both directions.
A web portal for teams that need to trade EDI without EDI software or EDI experience.
Orders and invoices that arrive as PDF, Excel or email converted into structured data for your ERP.
Portal-based programs such as SAP Ariba and Coupa handled through automation instead of manual re-keying.
Encrypted, audited file transfer with monitoring, retries and alerts for every connection.
Formats and standards: X12 · EDIFACT · XML · JSON · CSV and flat files · SAP IDocs · TRADACOMS · VDA
Solution options
Partners and applications connect in different ways. PRISM offers complementary methods, so each partner or application uses the one it can support and all of them reach your systems through the same integration layer.
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 WebConnectConnect ERP, commerce, warehouse and business applications with data mapping, transaction controls and monitoring, so orders, inventory and shipments move where they are needed.
Learn more about PRISM SmartConnect — Connect Apps and DataPRISM 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.
EDI transactions
These are the standard X12 documents ECOM supports for each type of program. Which ones apply to STARK depends on your agreement and onboarding package.
Purchase order through payment.
850 purchase order, 855 acknowledgment, 856 ship notice, 810 invoice, 820 payment.
Truckload, LTL and parcel: load tenders and responses, shipment status, bills of lading and freight invoices.
Rail shipment information, waybills, interchange and freight details with invoices.
Booking, shipping instructions, status, customs and ocean freight invoices.
ERP connectivity
EDI only pays off when the documents flow into the system you run the business on. ECOM integrates STARK orders, ship notices, invoices, inventory and shipment data with your ERP, warehouse management (WMS), transportation management (TMS) and accounting systems, so sales orders are created, shipments are confirmed and invoices are issued without re-keying.
We work with ERP platforms including SAP S/4HANA and SAP ECC, Oracle NetSuite and Oracle ERP Cloud, Microsoft Dynamics 365 and Business Central, Infor, Epicor, Acumatica, QAD, Sage, IBM Sterling and legacy AS/400 systems. Integration options include direct database and API connections, IDoc and flat-file interfaces, middleware and cloud connectors, and fully managed EDI where ECOM runs the connection for you. Every file is validated before it reaches your ERP and monitored after go-live, so exceptions are caught before they become chargebacks or late payments.
See ERP integrations · Fully managed EDI · Browser-based EDI
Zero Trust for supplier data exchange
Supplier exchanges with STARK 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. STARK 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
Not yet. ECOM does not publish STARK's EDI requirements on this page, but we can still connect you to STARK and to the rest of your trading partners. Ask an EDI specialist which documents, versions and connection method STARK requires for your program.
Where ECOM is already certified for the customer's program, you can start trading within hours. Where it is not, setup can be done within 2 business days. The exact timing depends on STARK's onboarding and testing process.
That depends on your program with STARK. Suppliers typically exchange purchase orders, acknowledgments, ship notices and invoices, while logistics and warehouse programs add shipment, status and inventory documents. Your STARK onboarding package lists the documents required.
Yes. ECOM maps EDI and API documents to ERP systems such as SAP, Oracle, Microsoft Dynamics, NetSuite, Infor, Epicor and Acumatica, so orders post without re-keying.
No. This is an independent page. It does not indicate an endorsement, partnership or approval by STARK.
Tell us about your STARK program, your ERP and your timeline. We will confirm the documents and connection method and give you a realistic start date.