Setup guides · October 5, 2026

How to Set Up EDI with CVS (Step by Step)

CVS EDI setup from prerequisites to go-live: AS2 connection, department and promo reference echoing, ASN timing tests, and monitoring.

A CVS EDI project has a short critical path: one AS2 connection, one set of cross-references, and a pair of echo rules that decide whether your documents match downstream. Suppliers who nail the echo rules in setup week never think about them again; suppliers who don't meet them one deduction at a time. Here's the build sequence for CVS, which typically runs 2–3 days — with the requirements background in the CVS EDI requirements guide.

Line up the prerequisites

From CVS: your supplier agreement, vendor identifiers, and item setup, since order lines carry the CVS item number alongside the UPC and your cross-reference must resolve both. From your side: decide where orders will land (NetSuite, Sage Intacct, or another of the 30+ supported systems) and confirm your warehouse can supply carton-level pack data for ASNs.

Stand up AS2 and attach the ERP

CVS trades AS2 direct — no VAN in the path. EDISQ owns the certificates, MDN handling, and endpoint upkeep, so your part of this step is pointing the connector at your business system and verifying that a test 850 becomes a sales order with items and ship-tos resolved, untouched by human hands.

Configure the echo rules

This is the CVS-specific heart of the setup. Inbound orders carry department and promotion references in REF*DP, and CVS expects those exact values echoed onto the 856 and the 810. Configure the maps to inherit them rather than rebuild documents from scratch — inheritance can't forget. Second, teach intake to recognize promotional buys, which arrive as separate POs rather than blended into replenishment; routing them correctly keeps their references, quantities, and timing distinct all the way to the invoice.

Test the two things CVS receiving checks

CVS supplier compliance concentrates on the ASN and the appointment, so the sandbox should prove two behaviors. Timing: the 856 must be transmitted before the DC appointment window opens, which in practice means generation fires at warehouse ship-confirm — test that the trigger works, not just that the document validates. Structure: the HL hierarchy runs shipment → order → pack → item, and mixed cartons get flagged at receiving, so run a mixed-carton scenario and inspect how the document describes it. Finish with a full order-to-invoice pass confirming the department and promo references arrived intact at both destinations.

Go live; watch the echoes and the clock

Certification with pre-built CVS maps is usually quick. In production, monitor three signals: 997 acknowledgments on every transmission, ASN generation latency from ship-confirm, and a periodic audit that REF values are still echoing — the failure mode after a map change is silent, and silent failures are the expensive kind.

Where CVS setups actually stall

Three delays account for nearly every CVS project that runs past its estimate, and none of them is technical. Item setup on the CVS side finishing later than expected — the EDI build completes and then idles until the item file is live. Warehouse pack data turning out to exist only on paper, which blocks realistic ASN testing until someone wires carton-level capture. And promotional PO handling deferred as an edge case, then arriving in production during the first promotion. Front-load all three conversations in the kickoff and the 2–3 day estimate holds; discover them in week two and it doesn't. The pattern generalizes across pharmacy retail — the technical work is rarely the schedule risk.

The running cost

CVS documents bill on the standard EDISQ meter: nothing for the first 25 documents each month, then from $0.50 per document with the rate declining to $0.10 at the highest volume tier, marginal-tier accounting throughout. The AS2 infrastructure, certified maps, sandbox, and monitoring are all part of that price — no setup or mapping invoices, with live trading on the Production plan's $100/month minimum applied entirely to usage. Tiers and examples at pricing.

FAQ

How does CVS connect for EDI?

AS2 direct. EDISQ maintains the connection and certificates as part of the per-document price, so the connectivity step is configuration rather than a project.

How long does the CVS EDI build take?

Around 2–3 days with certified maps. Reference echoing and ASN timing are the parts worth testing hardest.

What references must round-trip on CVS documents?

Department and promotion references from the REF*DP on the 850 must echo onto the 856 and the 810. Dropping them breaks matching downstream.

How do promotional orders differ at CVS?

Promotional buys arrive as separate POs rather than folded into replenishment orders. Your intake process should recognize and route them accordingly.