Retail integration

Walgreens EDI integration for suppliers

A guide for suppliers connecting with Walgreens, covering distribution center and direct store delivery flows, the documents involved and ERP integration.

At a glance

Walgreens integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Walgreens program or a customer relationship.

Illustration of a retail storefront with an awning and a shopping bag, representing the retail industry that Walgreens operates in.
Industry. Retail: where Walgreens operates.
Workflow diagram: your ERP and warehouse systems exchange documents with Walgreens through ECOM. You send 855, 856, 810, 846; you receive 850, 860, 820, 852; 997 acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor Walgreens 855 856 810 846 855 856 810 846 850 860 820 852 850 860 820 852 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Walgreens

Tell us which documents you exchange with Walgreens, 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 Walgreens.

  • Review of Walgreens' 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.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Walgreens

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Walgreens integration fits your systems

Your systemsERP, WMS and accounting
ECOMMapping, validation, connectivity and monitoringVAN AS2 or FTP · Supplier portal
WalgreensIts program, documents and requirements
  1. ConfirmConfirm your Walgreens program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Walgreens integration

Who this is for: Consumer health, beauty, pharmacy and general merchandise suppliers shipping to Walgreens distribution centers or delivering directly to stores.

Walgreens communicates with established suppliers through SupplierNet, its supplier portal. We could not verify Walgreens' EDI requirements from a public source, so this guide describes common practice for retail suppliers. For retail suppliers, the purchase order, advance ship notice and invoice are usually the core documents, with functional acknowledgments confirming receipt, and invoices are matched against the order and the shipment.

Walgreens supports more than one delivery model. Suppliers shipping to distribution centers follow one flow, while direct store delivery suppliers deliver to individual stores and invoice each delivery. Direct store delivery invoices usually represent a single delivery to a store with line item detail, and retailers generally accept EDI invoices only from vendors who have passed testing and who re-test after changes to their EDI software, mapping or versions. Confirm the current rules in SupplierNet.

Suppliers should confirm their specific requirements, documents and testing steps through Walgreens' supplier portal.

Program summary

What Walgreens asks of suppliers

A summary in ECOM's own words. Requirements vary by program and change over time, so confirm the details with Walgreens during setup.

Standard
X12 4010
Order types
Distribution centers · Direct store delivery · Pharmacy inventory · Import · Adult beverage DSD

Ship notices

  • Separate ship notices apply to domestic, import and pharmacy shipments, and pharmacy notices carry DSCSA drug-traceability data.
  • A ship notice is expected at least four hours before arrival so the GS1-128 label can drive automated receiving.

Labels and pallets

  • The pallet level of the ship notice repeats the SSCC-18 printed on the GS1-128 pallet label.

Invoices and payment

  • Short payments can arise when the invoiced quantity exceeds what was received, or the invoiced cost exceeds the order cost.

Workflows

Typical Walgreens business workflows

A typical flow built from the documents below; your own program may differ.

Distribution center replenishment

  1. 1Receive 850 purchase order
  2. 2Ship to the distribution center
  3. 3Send 856 ship notice
  4. 4Send 810 invoice

Direct store delivery

  1. 1Receive store order
  2. 2Deliver to the store
  3. 3Send one invoice per delivery
  4. 4Reconcile payment

Documents and APIs

Walgreens documents by program

Documents used in Walgreens' EDI program, seen from the supplier's side. Which ones apply depends on your program, so confirm the list with Walgreens.

DocumentNameDirectionStatusPurpose
850 Purchase Order You receive from Walgreens Program document Places an order for goods.
855 Purchase Order Acknowledgment You send to Walgreens Program document Confirms, changes or rejects an order.
860 Purchase Order Change You receive from Walgreens Program document Changes an existing order.
856 Ship Notice/Manifest You send to Walgreens Program document Describes a shipment before it arrives.
810 Invoice You send to Walgreens Program document Bills for what shipped.
820 Payment Order/Remittance Advice You receive from Walgreens Program document Explains what a payment covers.
846 Inventory Inquiry/Advice You send to Walgreens Program document Reports inventory available to sell or ship.
852 Product Activity Data You receive from Walgreens Program document Shares sales and on-hand activity by item.
861 Receiving Advice You receive from Walgreens Program document Reports what was received, including variances.
997 Functional Acknowledgment Both directions Program document Confirms each file was received and readable.

Connectivity

How companies connect

  • VAN AS2 or FTP

    VAN, AS2 and FTP-based connections are the usual options for retail EDI; confirm which Walgreens accepts through SupplierNet.

    General guidance

  • Supplier portal

    Walgreens manages supplier onboarding and offers a web-based option for suppliers that are not EDI capable.

    General guidance

Challenges

Common integration challenges

  • Two delivery models

    Distribution center and direct store delivery flows have different document rules.

  • Three-way matching

    Invoices must reconcile with the purchase order and the shipment.

  • Re-testing after changes

    Changes to EDI software or maps can require re-testing with Walgreens.

Automation options for Walgreens suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet Walgreens' labeling and ship notice requirements, and see what needs action. Walgreens sets its program's rules; ECOM confirms which options fit yours.

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.

Discuss Your Trading Partner Requirements

Connect Walgreens documents to your ERP

ECOM integrates Walgreens documents with ERP and route accounting or warehouse systems, so distribution center and store delivery invoices are generated correctly from each delivery.

Product

PRISM-SCV

Monitor ship notices and invoice matches across Walgreens orders.

Service

Mapping and Translation

Maintain Walgreens maps and manage re-testing when changes are needed.

Zero Trust for supplier data exchange

Zero Trust EDI and MFT for your Walgreens connection

Supplier exchanges with Walgreens 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.

  • Authentication

    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.

  • Least privilege

    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.

  • Isolation

    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.

  • Encryption

    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.

  • Certificate and key management

    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.

  • Monitoring and access controls

    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.

  • Audit trail

    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.

What this means for your data

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.

Orders, ship notices and invoices

Documents are verified when they arrive and every transfer is logged, so a missing or altered file shows up quickly.

Portals and file drops

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. Walgreens may set its own security requirements, which come first.

Next step

Get help with your Walgreens program

Each request goes to an ECOM EDI specialist with Walgreens' name attached, so the reply starts from your program.

  • Review Walgreens' requirements

    Send us Walgreens' guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Walgreens 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 Walgreens document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match Walgreens' rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

Walgreens integration FAQs

Which EDI documents does Walgreens use?

Retail suppliers typically exchange the 850 purchase order, 856 ship notice, 810 invoice and 997 functional acknowledgment. Confirm Walgreens' list through SupplierNet, its supplier portal.

How does direct store delivery invoicing work with Walgreens?

Direct store delivery invoices usually cover a single delivery to a store, with line item detail. Confirm Walgreens' current rules in SupplierNet.

Do we need to re-test after changing EDI software?

Walgreens' guide asks vendors to notify Walgreens and re-test after changes to EDI software, mapping or versions.

Is ECOM an approved Walgreens provider?

This page is an integration guide and does not indicate an approval or partnership with Walgreens. ECOM builds integrations to Walgreens' published requirements.

Accuracy

This guide describes Walgreens' program in ECOM's own words as of October 2026. Walgreens sets its own requirements and can change them at any time; your Walgreens implementation guide, supplier portal or account contact is the authoritative source for your program.

Request Walgreens integration assistance

Tell us about your Walgreens program, documents and ERP. We will outline the connection, mapping and testing plan.