CVS EDI Requirements: How to Become Compliant

Reference discipline is what separates smooth CVS suppliers from the ones fighting deductions. A CVS purchase order arrives carrying department and promotion references, and CVS expects to see those same references again on the ship notice and the invoice. Suppliers whose systems carry data forward automatically barely notice the requirement; suppliers who re-key documents lose the references and then lose the match.

The echo rule

On the 850 purchase order, REF*DP segments identify the department and any promotion behind the buy. The rule is simple to state and unforgiving in practice: whatever references arrive on the order must reappear on the 856 and the 810. CVS's matching machinery uses them to connect the three documents; a ship notice without the department reference is, from the retailer's side, a document about nothing in particular.

The same PO carries item identity as a CVS item number plus UPC pair — cross-reference both directions — and one structural habit worth knowing: promotional buys come in as their own purchase orders, separate from replenishment. Keep the streams distinct in your system so each downstream document inherits the right context.

Timing against the appointment

CVS receiving runs on DC appointments, and the ASN must be in CVS's hands before the appointment window opens. That ordering matters more than any batch schedule you may have: if ship-confirm happens in the afternoon and your EDI job runs overnight, an early-morning appointment can beat your ASN to the dock. Transmission triggered by the warehouse event itself, not by the clock, is the fix.

Structure-wise, CVS's 856 follows the standard shipment → order → pack → item hierarchy, and mixed cartons get flagged at receiving — so describe cartons as they were physically packed, mixed contents included, rather than idealizing the shipment.

What the compliance program watches

CVS supplier compliance concentrates on ASN presence and appointment discipline — the deductions land when documents are late, missing, or mismatched against freight. None of that requires heroics to avoid. Validation before transmission catches structural errors; event-driven ASN timing kills lateness; and the reference echo, handled in the map, never gets forgotten by a busy human because no human touches it.

Invoices that inherit their context

The 810 closes the loop, and it lives or dies by inheritance. An invoice built from the shipment record — the same data that produced the ASN — arrives already carrying the PO number, the department and promotion references, and quantities as actually shipped. An invoice built by re-keying from the order carries whatever the person doing the keying remembered. Large-retail accounts payable reconciles documents by machine, so the first kind gets paid on schedule and the second kind generates research requests, and research requests are where margin goes to wait.

One data lineage from order to invoice is the design principle that makes every CVS rule above cheap to follow.

Connectivity and the setup path

CVS trades AS2 direct — certificates, MDN handling, endpoint management. With EDISQ that infrastructure is included rather than being your project. From there, onboarding is a familiar arc:

1. CVS vendor setup and program assignment.
2. System connection — QuickBooks Online, NetSuite, or any of 30+ platforms.
3. Cross-reference load: item numbers, UPCs, ship-to locations, departments.
4. Sandbox certification replaying CVS scenarios, then go-live with 997 tracking on.

The EDI side typically takes 2–3 days on certified CVS maps.

Costs scale with what you ship, not with the calendar: after 25 free documents each month, pricing starts at $0.50 per document and steps down to $0.10 across volume tiers, charged marginally so growth never repriced your existing volume. No mapping invoice, no setup fee, and a flat $100/month Production minimum applied entirely to usage — the ladder is published and the AS2 connection to CVS is part of it.

FAQ