REI EDI Integration for Outdoor & Apparel Suppliers

SBSA Technology handles complete REI Co-op EDI compliance — Distribution Center, store replenishment, and drop ship. 850 → 855 → 856 → 810, fully automated and connected to your ERP.

REI Supplier EDI Setup

Select your fulfillment path to see what's required

1
850 Purchase Order — Inbound

REI sends PO specifying DC address, items, quantities, and required ship dates. SBSA routes into your ERP as a sales order automatically.

2
855 Acknowledgment — within 24 hours

Confirm ability to fulfill at the line level. Quantity, pricing, or date changes must be reflected. Missing the window is a compliance event.

3
GS1-128 carton labels required

Every carton must carry a compliant GS1-128 label. SBSA generates labels from ASN data before shipment departs.

4
856 ASN prior to arrival

Transmitted the moment goods leave your facility. Missing or late ASNs result in compliance chargebacks.

5
810 Invoice — one per PO

Issued electronically after shipment. Credit memos and allowances handled separately per REI instructions.

1
Ship-to is an REI store address

The 850 will route to an REI retail location. Same document suite as DC shipments applies in full.

2
REI packing slip required

Retail-store shipments require REI-branded packing documentation generated from your ASN data.

3
GS1-128 labels on every carton

Retail store receiving requires the same label compliance as DC shipments — no exceptions.

4
Same 24-hour 855 window

REI's PO acknowledgment deadline applies equally to store replenishment orders.

5
SBSA maps both paths identically

DC and store ship-to logic is handled in the same workflow — no separate setup required.

1
Member address embedded in 850

REI's PO includes the end customer's name, address, and contact. You ship directly to the member on REI's behalf.

2
REI-branded packing slip mandatory

All drop ship orders must include REI's packing document. Your brand must not appear on packaging at any point.

3
UPS or FedEx tracking required in ASN

Parcel tracking number must appear in the 856 ASN. No tracking = potential chargeback and member escalation.

4
One ASN per shipment — no combining

Each shipment to each member address requires its own ASN. Volumes are high — automation is essential.

5
SBSA bridges drop ship into your ERP

Member-level order volume requires real-time automation. SBSA connects REI drop ship POs directly to your fulfillment system.

Who REI EDI Compliance Applies To

REI sources from a broad range of outdoor and lifestyle product suppliers. If you are active or pursuing a supplier agreement with REI, you will be required to meet their EDI compliance standards across all trading activity.

Apparel & Footwear Brands

Clothing, base layers, waterproof outerwear, trail and approach footwear, and lifestyle apparel. REI requires full EDI for all seasonal and replenishment orders, with line-level ship date confirmations on every 855.

Apparel Footwear Seasonal POs

Hardgoods & Equipment Suppliers

Tents, sleeping bags, packs, climbing hardware, kayaks, bikes, and technical equipment. Often subject to higher-value POs with strict ship date windows and GS1-128 labeling requirements tied to warehouse receiving systems.

Hardgoods High-Value Items GS1-128 Labels

Accessories & Consumables

Navigation tools, lighting, hydration, nutrition, first aid, and travel accessories. Higher order frequency with drop ship potential — automation is especially important for this category to manage volume without manual intervention.

Accessories Drop Ship Eligible High Frequency
23M+ REI Co-op members who expect reliable product availability and fulfillment
24 hrs Maximum window to transmit your 855 PO Acknowledgment after PO receipt
180+ REI retail stores across North America requiring store-level replenishment
Chargeback Shipments without a prior ASN or missing GS1-128 labels incur compliance chargebacks

Three Ways to Connect with REI

REI supports AS2, SFTP, and VAN for EDI document exchange. SBSA Technology handles complete setup, testing, certificate management, and ongoing compliance monitoring for all three protocols.

SFTP

Secure File Transfer

Secure FTP-based document exchange. A practical option for suppliers with existing SFTP infrastructure who are transitioning to fully automated EDI with REI.

  • Protocol: SFTP (SSH File Transfer Protocol)
  • Standard: ANSI X12 flat files
  • Best for: Mid-volume suppliers with existing SFTP
  • SBSA manages: SFTP config, file routing & monitoring

EDI VAN

Managed Network

Value-Added Network for suppliers who prefer a fully managed, intermediary-based connection. SBSA acts as your complete EDI department through the VAN — routing, translating, and monitoring all REI documents.

  • Protocol: EDI VAN — SBSA provides EDI ID
  • Best for: Smaller or less-technical suppliers
  • Monitoring: 24/7 document tracking and alerts
  • SBSA manages: Full VAN setup, routing & compliance

REI EDI Integration EDI Transaction Set

SBSA Technology supports core and supplemental REI EDI Integration EDI documents. Critical transactions are highlighted because they carry the highest compliance risk when transmitted incorrectly or late.

850

Purchase Order

REI's PO initiates the fulfillment cycle. Specifies ship-to location (DC, store, or member), items, quantities, ship dates, and pricing. Drop ship POs embed the member's address directly in the 850.

Inbound
855

PO Acknowledgment

Must be sent within 24 hours of PO creation date. Confirms ability to fulfill at the line level. Used to report quantity changes, revised ship dates, or pricing discrepancies.

Outbound 24-hour acknowledgment deadline
856

Advance Ship Notice

Transmitted when shipment leaves your facility — before it arrives at any REI location. Must match GS1-128 label data exactly. Drop ship ASNs must include member tracking numbers.

Outbound Transmit prior to physical arrival — chargeback risk
810

Invoice

One invoice per PO only. Standard EDI 810 for all product invoices. Credit memos and allowance adjustments are processed separately per REI Vendor Operations guidelines.

Outbound One invoice per PO — duplicates trigger deductions
997

Functional Acknowledgment

Confirms syntactic validity of every transmitted document. SBSA monitors all 997 responses and surfaces rejections before they become compliance issues.

Outbound
820

Payment Remittance

REI's payment and remittance advice document — auto-reconciles against open invoices in your accounting system when received.

Inbound
860

PO Change Request

Buyer-initiated PO modifications from REI. Quantity, pricing, or delivery changes are flagged and applied at the line item level in your ERP automatically.

Inbound
753

Routing Request

Supplier-initiated routing request sent to REI Logistics when carrier assignment is required before shipment. Used for select hardgoods and freight shipments.

Outbound
852

Product Activity Data

Sales and inventory activity data shared with REI for demand planning and replenishment — helps REI optimize stocking decisions and open buy for your product category.

Outbound

Connect REI EDI to Your Business System

SBSA integrates REI's EDI transactions directly with your ERP, accounting, or warehouse management system. REI 850 POs become sales orders. Shipment data drives the 856 ASN. Invoice data flows from your ERP to REI — no manual entry at any step.

QuickBooks Online

REI 850 POs map to QuickBooks Online sales orders. Fulfillment data triggers ASN generation. Invoices post to QBO automatically — no duplicate entry between REI and your books.

QuickBooks Enterprise

Full EDI-to-QBE integration for suppliers running QuickBooks Enterprise. Advanced inventory, assembly, and fulfillment workflows supported with REI's DC, store, and drop ship paths.

NetSuite

REI EDI transactions mapped natively to NetSuite sales orders, fulfillments, and invoices. Multi-subsidiary and multi-location NetSuite environments fully supported.

SAP Business One / S/4HANA

SBSA delivers REI POs as SAP sales orders and triggers outbound ASN and invoice documents from SAP data — across both Business One and S/4HANA environments.

Microsoft Dynamics 365

REI EDI fully integrated with Dynamics 365 Business Central and Finance & Operations — sales orders, warehouse picks, shipment confirmations, and AP/AR automation.

Custom & Legacy Systems

If your ERP or WMS isn't listed, SBSA builds a custom integration. We've connected EDI to hundreds of systems — flat-file imports, AS/400 mainframes, proprietary ERPs, and everything in between.

Built to Protect You from Chargebacks

REI's chargeback program applies financial deductions directly to your invoices when EDI or labeling requirements are not met. SBSA automates every compliance step so your REI account stays clean and every shipment reaches full payment.

855 PO Acknowledgment auto-fired within minutes of PO receipt — never miss the 24-hour window

856 ASN generated and transmitted at carrier pickup — not after goods arrive at REI

GS1-128 carton labels auto-generated from ASN data and validated for field completeness before dispatch

ASN-to-label cross-check — mismatches flagged and corrected before shipment leaves your facility

Drop ship REI-branded packing slip auto-generated from ASN data — your brand kept off the packaging

UPS/FedEx tracking numbers automatically pulled and inserted into drop ship ASNs

One-ASN-per-shipment enforcement — no accidental combining of multiple destinations

810 invoice auto-generated per PO — one invoice only, preventing duplicate deduction scenarios

Partial shipment handling — unfulfilled lines flagged in 855 with revised dates, never silently dropped

997 functional acknowledgment monitoring — every rejection surfaced before it becomes a compliance record

REI EDI FAQ

Common questions from outdoor and apparel suppliers beginning their REI EDI compliance journey.

REI requires four core EDI documents for all suppliers: the 850 Purchase Order (inbound from REI), the 855 PO Acknowledgment (outbound, within 24 hours of the PO date), the 856 Advance Ship Notice (outbound, before the shipment arrives at any REI facility), and the 810 Invoice (outbound, one per PO). The 997 Functional Acknowledgment is also exchanged for every document transmitted. SBSA handles all of these with full automation and ERP integration.

REI requires the 856 ASN to arrive before the physical goods reach any REI receiving location. An ASN that is absent or arrives after the shipment is a compliance violation and triggers a chargeback — a financial deduction from your invoice. This is one of the most common and costly supplier compliance failures with REI. SBSA transmits the ASN automatically at carrier pickup, preventing this scenario entirely.

No — REI uses a single EDI trading partner connection regardless of your fulfillment path. The 850 PO itself specifies whether the shipment goes to a Distribution Center, a retail store, or directly to a member. SBSA's mapping layer handles all three destinations in the same workflow, generating the correct documents (packing slips, labels, ASN structure) for each path automatically based on the 850 ship-to information.

REI requires GS1-128 (formerly UCC-128) compliant carton labels on all inbound shipments to DCs and stores. Labels must include the PO number, REI vendor number, REI item number, UPC, ship-to location, and carton count. The data on the label must match the ASN data exactly — REI's receiving systems cross-reference both electronically. Discrepancies trigger receiving exceptions and may result in chargebacks. SBSA generates all labels automatically from your ASN data to ensure the two always match.

Partial shipments are permitted, but must be communicated in the 855 PO Acknowledgment before you ship. You must reflect the quantity change and provide a revised ship date at the affected line item level in the 855. Do not ship partial without notifying REI in the 855 first — an unexpected partial shipment against a PO expecting full quantities is a compliance event. Backordered items should be noted with a revised date, not cancelled.

Yes — SBSA is an Intuit Silver Partner for both QuickBooks Online and QuickBooks Enterprise. Our REI EDI integration maps incoming 850 POs to QuickBooks sales orders, triggers ASN generation from fulfillment events, and posts invoices back to REI directly from your QuickBooks data. The integration is pre-validated against current QBO and QBE API versions, which means faster setup and lower compliance risk compared to generic EDI providers building the connection from scratch.

Ready to Become REI EDI Compliant?

Tell us your fulfillment path — DC, store, or drop ship — and your ERP system, and we'll build a complete REI integration plan for you.