Sign In
Book a Demo

REI Co-op EDI Integration for Outdoor Vendors

Outdoor brands selling to REI Co-op put its purchase orders on Pipe17 managed EDI and fill each one from the stock that also serves their own site, marketplaces, and specialty retail accounts.
Book a demo
REI Pipe17 Connector Icon

The Challenge of Outdoor Co-op EDI

Account-Specific Rules and Seasonal Demand

Upset person icon with exclamation mark, representing frustrated user or customer issue

Rules Set Account by Account

EDI providers describe REI vendors working to an account-specific Order Management Manual. Keeping every order, label, and ship notice in line by hand invites misses.

Lock over database file cabinets, symbolizing secure data protection

Seasonal Gear, Tight Windows

Outdoor demand peaks by season. An inventory feed built from stale counts can promise REI tents or jackets your storefront already sold.

Icon of 3 stacked files next to 4 stacked database

Labels and ASNs Under Scrutiny

Late or mismatched ship notices and carton labels are a reported source of REI chargebacks. Every 856 needs to match what was packed.

The Solution for REI EDI Integration & Order Management

REI Writes Your Order Manual. Pipe17 Follows It on Every Order.

Pipe17’s managed EDI can run your REI Co-op documents, or stay with your provider. Trouble starts after the 850: hand-rolled code and a legacy OMS working REI orders from a count your web store never sees. Pipe17’s Order Operations Platform supersedes both, filling every REI order from one stock pool.
iPaaS & Custom Builds Legacy OMS Pipe17
Native API-First Connectivity ✅ ❌ ✅
Pre-Built Commerce Connectors ❌ ❌ ✅
Custom Integration Mappings ✅ ❌ ✅
Advanced Order Orchestration ❌ ✅ ✅
Exception Management & Alerts ❌ ❌ ✅
Unified Inventory Management ❌ ✅ ✅
Rapid to Implement & Go-Live ❌ ❌ ✅
Easy to Add / Swap Channels & Flows ❌ ❌ ✅
Low Total Cost of Ownership (TCO) ❌ ❌ ✅

Modern Brands and Fulfillment Providers Rely on Pipe17

Partner with Purpose at REI through Pipe17

Supply REI from the platform already running your direct and marketplace orders. One stock pool serves every channel, and each REI order stays traceable from PO to invoice.
Decision tree of rectangle boxes representing rules-based automation

Manual Rules Built In

Each REI document is mapped to your account's Order Management Manual once, and every order after that follows it.

Order box on shield with upward arrow around it symbolizing future-proof order operations

One Stock Pool for the Co-op and Your Site

REI orders and your direct sales draw on the same live inventory. Gear sold online is not promised to REI as well.

Odometer turned up all the way over webpage representing immediate speed

Labels and ASNs from One Shipment

GS1-128 label data and the 856 both come from the cartons your warehouse confirmed. Both describe the same shipment.

Automated REI EDI Flows

Through managed EDI, Pipe17 links to your REI trading-partner connection and maps each document below to your account’s REI Order Management Manual.
  • Pull Orders from REI. REI purchase orders (850) for its stores, distribution centers, or drop-ship customers come into Pipe17 as orders, each tied to the rules in your account’s manual.
  • Push Order Confirmations to REI. If your manual asks for an 855, Pipe17 returns it for each REI PO, accepting every line or confirming the smaller quantity you are able to ship.
  • Push Fulfillments to REI. Your 856 is assembled from cartons the warehouse has confirmed, mapped so each carton’s SSCC-18 lines up with the GS1-128 label your team or 3PL puts on it.
  • Push Inventory to REI. When REI calls for inventory advice on your account, Pipe17 sends an 846 drawn from the warehouses you choose to supply the co-op.
  • Push Invoices to REI. Pipe17 issues the 810 against the REI PO once cartons are confirmed shipped, and the invoice reconciles to both the PO and the ship notice.
  • Answer Each REI Transmission with a 997. REI receives a functional acknowledgment (997) for every document Pipe17 takes in.
  • Accept REI Change Requests. An 860 purchase order change from REI is received in Pipe17 and answered with a 997.
  • Supply Carton Labels to the Packing Line. Pipe17’s API gives your warehouse or 3PL the GS1-128 (UCC-128) content for each REI carton to print and apply, scoped to what your REI program requires.
  • Pick the Warehouse for Each PO. Every REI order goes to a location with the gear in stock, your own building or a 3PL.
  • Record REI Orders in Your ERP. Each REI PO can land in NetSuite, or any ERP you run, as a sales order, with co-op revenue beside your other wholesale and online sales.
  • Run 3PL Orders over Warehouse EDI. A 3PL working from EDI gets a 940 from Pipe17 for each REI order and sends a 945 back when it ships.
  • Catch REI Orders That Break a Rule. When an REI order breaks one of your rules, the Automation Engine parks it and alerts your team instead of sending it on.

Connect REI EDI to Your Outdoor Business

REI is one account in a wider outdoor business that includes specialty shops, your direct site, and marketplaces. Pipe17 runs every one of them from a single inventory pool with shared routing rules.

Supply REI Co-op from the Stock Your Whole Business Shares

Show us your REI Order Management Manual and the channels you sell through. We will walk through how each REI document and order would run on Pipe17.
Book a demo
REI horizontal svg logo black

is better with

Pipe17 horizontal svg logo black

REI Co-op EDI Integration FAQs

Pipe17 maps your documents to the Order Management Manual (OMM) that EDI providers describe REI assigning each account, a rulebook covering orders, labeling, shipping, and ship notice timing. Purchase orders (850), invoices (810), and advance ship notices (856) follow its field rules, and test exchanges run until REI signs off. The managed EDI setup process lists what your team supplies, such as vendor details and item lists.

EDI providers report that REI requires a GS1-128 (UCC-128) label on each carton and pallet, with an SSCC-18 that matches the advance ship notice (ASN, 856) exactly. Pipe17 supplies the GS1-128 label data through its API, your warehouse or 3PL prints it, and Pipe17 fills the 856 from the same confirmed cartons. Label scope is set for each REI program before go-live.

Pipe17's managed EDI, which runs on the Order Operations Platform, exchanges the REI purchase order (850), invoice (810), and ship notice (856), and takes in purchase order changes (860), answering each with a 997. Where your REI account also asks for a PO acknowledgment (855) or inventory advice (846), those come from Pipe17's core X12 documents as well, beside the rest of your orders.

Yes, Pipe17 can run both, with bulk REI purchase orders (850) for stores or distribution centers and any REI drop-ship orders on separate connections. Bulk orders follow the EDI order path from purchase order to invoice, routed to the location that stocks them. Setup confirms how your drop-ship lane transmits, and those orders ship straight to the REI customer from your building or ShipBob or another 3PL.

No, Pipe17 sells managed EDI for REI together with its full platform, so it suits outdoor brands that also sell direct or on marketplaces such as Amazon. Brands whose sales are all EDI wholesale can check the managed EDI fit breakdown for a better option.