Distribution integration
Nicholas and Company EDI for suppliers
A guide for suppliers to Nicholas and Company: verified company facts, what Nicholas and Company publishes about EDI, the documents foodservice and grocery distributors typically exchange, and what is still to confirm.
At a glance
Nicholas and Company integration, in three pictures
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Nicholas and Company program or a customer relationship.
Talk to an EDI/API Expert about Nicholas and Company
Tell us which documents you exchange with Nicholas and Company, 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 Nicholas and Company.
- Review of Nicholas and Company's requirements with you, once you have them
- EDI and API integration with your ERP and warehouse systems
- Monitoring and managed service after go-live, if you want it
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
How Nicholas and Company integration fits your systems
- ConfirmConfirm your Nicholas and Company program, role and the documents it requires.
- MapMap each document to your ERP fields and business rules.
- ConnectConfigure the connection and security the program needs.
- TestTest against the applicable specifications and acknowledgments.
- Go liveGo live with monitoring, alerts and exception handling.
Overview
Understanding Nicholas and Company integration
Who this is for: Food and beverage manufacturers, brokers and suppliers that sell through Nicholas and Company, and their EDI, order management and finance teams.
Nicholas and Company, Inc. is a privately held foodservice distributor based in Utah. Its website is nicholasandco.com.
Nicholas and Company 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.
Food and grocery distributors commonly send purchase orders by EDI and expect an order acknowledgment, an advance ship notice and an invoice in return. Item data matters as much as the documents: GS1 GTINs on each item and case, SSCC labels on pallets, and lot and date information where food traceability rules apply. Many distributors also share price and item information with suppliers, and some send product movement data. The documents, flow and connection options on this page describe that general practice. They are not Nicholas and Company's published requirements; confirm each one with Nicholas and Company before you build maps or test.
Workflows
Typical Nicholas and Company business workflows
General guidance: typical flows in this industry, not Nicholas and Company's published process.
Typical order to invoice
- 1Receive 850 purchase order
- 2Send 855 acknowledgment
- 3Label pallets and cases
- 4Send 856 ship notice
- 5Send 810 invoice
Documents and APIs
Nicholas and Company documents by program
General guidance. We could not verify Nicholas and Company's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Nicholas and Company's confirmed requirements. Confirm the list, versions and programs with Nicholas and Company.
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 Nicholas and Company | Not stated | General guidance | Typically how the distributor orders product for its warehouses. |
| 855 | Purchase Order Acknowledgment | To Nicholas and Company | Not stated | General guidance | Typically confirms quantities, prices and dates, or reports changes. |
| 856 | Ship Notice/Manifest | To Nicholas and Company | Not stated | General guidance | Typically lists what is on each shipment, often with pallet SSCC labels and lot details. |
| 810 | Invoice | To Nicholas and Company | Not stated | General guidance | Typically bills for what shipped, against the purchase order. |
| 832 | Price/Sales Catalog | To Nicholas and Company | Not stated | General guidance | Often used to share item and price information. |
| 997 | Functional Acknowledgment | Both directions | Not stated | General guidance | Typically confirms that each file was received and readable. |
Connectivity
How companies connect
AS2 or SFTP
Many distributors exchange EDI files directly over AS2 or SFTP. Confirm which methods Nicholas and Company 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
Item and case data
GTINs, case packs and catch weights must match what the distributor has on file, or receiving and invoices fail to match.
Lot and date tracking
Products covered by food traceability rules often need lot and date details on labels and in ship notices.
Invoice matching
Invoices that do not match the purchase order or the receipt are a common cause of payment delays and deductions.
Requirements not public
Nicholas and Company does not publish its supplier EDI requirements, so the document set and rules must be confirmed with Nicholas and Company before work starts.
Automation options for Nicholas and Company suppliers
Four ways to automate. One foundation.
ECOM helps you automate them, meet Nicholas and Company's labeling and ship notice requirements, and see what needs action. Nicholas and Company 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.
Learn more about WebConnect
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 Nicholas and Company documents to your ERP
ECOM connects the documents Nicholas and Company 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.
Food and Beverage
See how ECOM supports EDI for food and beverage suppliers.
ServiceFully Managed EDI
Have ECOM run your EDI connections, monitoring and partner changes.
General EDI flow
How EDI with Nicholas and Company typically works
The documents, their order and the timing are Nicholas and Company's to set; this is the general sequence most programs of this kind follow.
-
850 Purchase Order
From Nicholas and Company to you
Typically how the distributor orders product for its warehouses.
-
855 Purchase Order Acknowledgment
From you to Nicholas and Company
Typically confirms quantities, prices and dates, or reports changes.
-
856 Ship Notice/Manifest
From you to Nicholas and Company
Typically lists what is on each shipment, often with pallet SSCC labels and lot details.
-
810 Invoice
From you to Nicholas and Company
Typically bills for what shipped, against the purchase order.
-
832 Price/Sales Catalog
From you to Nicholas and Company
Often used to share item and price information.
-
997 Functional Acknowledgment
Both directions
Typically confirms that each file was received and readable.
Need help with the specification?
Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.
Next step
Get help with your Nicholas and Company program
Each request goes to an ECOM EDI specialist with Nicholas and Company's name attached, so the reply starts from your program.
-
Review Nicholas and Company's requirements
Send us Nicholas and Company's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements review -
Connect Nicholas and Company 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 Nicholas and Company document, then go live with monitoring from the first file.
Plan testing and certification -
Shipping labels and ASNs
Labels and ship notices that match Nicholas and Company's rules, to help avoid receiving problems and compliance deductions.
Review shipping compliance
Nicholas and Company integration FAQs
Does Nicholas and Company publish supplier EDI requirements?
We found no supplier EDI specification or onboarding page on Nicholas and Company's public website when we checked on 7 November 2026. Suppliers usually receive the requirements from Nicholas and Company during setup.
Which EDI documents do suppliers to Nicholas and Company usually exchange?
Suppliers to foodservice and grocery distributors typically exchange the 850, 855, 856, 810, 832, 997 documents listed on this page. That is general practice, not Nicholas and Company's published list; confirm the set with Nicholas and Company.
What is not yet known about EDI with Nicholas and Company?
Which EDI documents Nicholas and Company 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 Nicholas and Company?
Yes. Once Nicholas and Company 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 Nicholas and Company.
Sources and accuracy
This guide summarizes publicly available information as of November 2026. Nicholas and Company sets its own requirements and can change them at any time; your Nicholas and Company implementation guide, supplier portal or account contact is the authoritative source for your program.
- Nicholas and Company, company website Official Nicholas and Company source
Nicholas and Company 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
Winsupply EDI
A guide for suppliers to Winsupply: verified company facts, what Winsupply publishes about EDI, the documents building products distributors typically exchange, and what is still to confirm.
WPG Americas EDI
A guide for suppliers to WPG Americas: verified company facts, what WPG Americas publishes about EDI, the documents electronics and technology distributors typically exchange, and what is still to confirm.
Würth Industry USA EDI
A guide for suppliers to Würth Industry USA: verified company facts, what Würth Industry USA publishes about EDI, the documents industrial distributors typically exchange, and what is still to confirm.
ZD Integrated Circuits (ZDI) EDI
How EDI and API integration with ZD Integrated Circuits (ZDI) works in practice: documents, workflows, onboarding and common problems, and where ECOM helps.
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.
Request Nicholas and Company integration assistance
Tell us about your Nicholas and Company program, documents and ERP. We will outline the connection, mapping and testing plan.