Sign In
Book a Demo

Anthropologie EDI Integration for Lifestyle Vendors

On URBN’s EDI program, Anthropologie vendors send the ship notice that serves as the packing list, and the invoice, from Pipe17 instead of building them in Tradestone, with every PO filled from shared stock.
Book a demo
Pipe17 integration connector tile

The Challenge of Lifestyle Retail EDI

Portal Steps, Channel Rules, and Shared Stock

Icon of 3 stacked files next to 4 stacked database

Tradestone Paperwork on Every PO

Without EDI, every Anthropologie PO means a packing list, carton labels, an ASN, and an invoice built by hand in URBN's Tradestone portal.

Stacked user icons, representing sub-accounts or team access

Rules That Change by Sell Channel

Packaging and pre-ticketing rules follow each PO's sell channel, Retail, Direct, or Omni. One shipment can follow different rules than the last.

Shelved boxes, symbolizing warehouse inventory or fulfillment center

Stock Split Across Channels

Anthropologie orders, your own site, and other wholesale accounts pull from the same pieces. Separate counts oversell a best seller in one channel.

The Solution for Anthropologie EDI Integration & Order Management

Anthropologie Chooses the Pieces. Pipe17 Moves the Orders.

Send Anthropologie documents over Pipe17’s managed EDI, or keep them with your current EDI provider. Friction starts afterward, when scripts and a legacy OMS work orders from stock figures your web store never sees. Both jobs move to Pipe17’s Order Operations Platform, filling each PO from one stock pool.
iPaaS & Custom Builds Legacy OMS Pipe17
Native API-First Connectivity ✅ ❌ ✅
Pre-Configured 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) ❌ ❌ ✅

Leading Brands and Fulfillment Providers are Powered By Pipe17

Olly logo horizontal black svg
Follett Higher Education logo horizontal svg black
Mary Ruths horizontal svg logo black
CGK Linens Horizontal SVG Logo
Ryder horizontal svg black logo
AS Beauty logo horizontal svg black
Dude Wipes horizontal logo black svg
FedEx horizontal svg logo black
Wyze horizontal svg logo black
Melin horizontal svg logo black
Barrett Distribution Centers horizontal svg logo
Sacheu Beauty horizontal svg logo black
Made In Cookware horizontal svg logo black
Azalea Wang logo horizontal black svg
Radial fulfillment horizontal svg logo black
Black Rifle Coffee Company logo horizontal black svg

Anthropologie Orders on the Same Record as Everything Else

Odometer turned up all the way over webpage representing immediate speed

Documents from the Shipped Order

URBN receives ship notices (856) and invoices (810) straight from the shipped order, with no packing lists or invoices to re-key.

Interlocking circles and lines, symbolizing seamless integration

One Pool for Every Piece

Stock behind each Anthropologie purchase order is the same stock your storefront, marketplaces, and other retail accounts sell. A piece sold in any of them comes out of that one count.

Magnifying glass over graph, representing analytics across any data source

Drop Ship Beside Wholesale

Rithum (DSCO) drop-ship orders and EDI purchase orders from Anthropologie run through one order queue with shared routing rules.

Automated Anthropologie EDI Flows

Through managed EDI, Pipe17 joins your account on URBN’s EDI program for Anthropologie. The documents below stand in for the packing list, ASN, and invoice steps you would otherwise complete in Tradestone.
  • Pull Orders from Anthropologie. Pipe17 records each Anthropologie purchase order (850) as an order headed for the URBN facility named on it, such as a retail distribution center or the direct fulfillment center.
  • Push Order Confirmations to Anthropologie. URBN has vendors accept each PO in Tradestone before its ship date rather than by 855, and acceptance stays there. Pipe17 can return an 855 if your URBN setup asks for one.
  • Push Fulfillments to Anthropologie. One 856 per purchase order carries the ship notice and the packing list URBN would otherwise take in Tradestone, built from the cartons your warehouse confirms.
  • Push Inventory to Anthropologie. URBN’s EDI program names the 850, 856, and 810 only. An 846 goes out just when URBN requests inventory advice, drawn from the same pool as your other channels.
  • Push Invoices to Anthropologie. Pipe17 issues the 810 for every shipped Anthropologie PO. EDI vendors cannot mix in Tradestone invoices, which means the whole account bills this way.
  • Answer URBN Transmissions with a 997. Pipe17 returns a functional acknowledgment (997) for every Anthropologie document it takes in.
  • Take In Replacement POs. URBN revises a purchase order by sending a replacement 850 instead of an 860. Pipe17 receives each one and answers with a 997.
  • Share Carton Label Data with the Warehouse. Pipe17’s API serves the GS1-128 (UCC-128) label content your warehouse or 3PL needs for every Anthropologie carton. They print and apply it, and URBN tests the label before go-live.
  • Route to the Location Holding the Pieces. Routing rules send each PO to the warehouse or 3PL with the stock, whichever URBN facility it ships to.
  • Run Anthropologie Drop Ship on Rithum. Drop-ship orders URBN sends through Rithum’s DSCO platform enter Pipe17 through its CommerceHub DSCO connector, next to the EDI purchase orders.
  • Post Orders to Your ERP. NetSuite, or whichever ERP you use, can receive each Anthropologie order as a sales order.
  • Hold Orders That Fail a Check. An Anthropologie order that trips a rule you set is kept out of the warehouse queue by the Automation Engine, and your team gets an alert.

Connect Anthropologie EDI to Your Creative Network

If you also sell to Free People or Urban Outfitters, one URBN vendor site sets the rules for all three. Pipe17 runs those accounts, your own site, and marketplaces from a single inventory pool.

Send Anthropologie Ship Notices and Invoices Straight from Your Orders

Walk us through your URBN vendor setup, your ship-from locations, and where else you sell. We will show an Anthropologie PO moving through Pipe17 step by step, purchase order to invoice.
Book a demo
Anthropologie horizontal svg logo black

is better with

Pipe17 horizontal svg logo black

Anthropologie EDI Integration FAQs

On URBN's EDI program, the ship notice (856) replaces the packing list and advance ship notice built in Tradestone, and the EDI invoice (810) replaces the Tradestone invoice, according to URBN's vendor site. Tradestone still handles PO acceptance, country of origin, and customs descriptions. Pipe17 sends both documents from the shipped order, drawing on its core X12 documents, and the advance ship notice is built from cartons your warehouse confirms.

No, URBN's vendor site says EDI is closed to URBN Import Vendors, where URBN acts as importer of record. It suits vendors who ship domestically to URBN facilities themselves. Vendors who qualify ask URBN US Vendor Relations to start the EDI setup, and the account then joins the Pipe17 Network, where Pipe17 handles the mapping and testing in its EDI onboarding steps.

URBN tests each EDI vendor's UCC-128 carton labels with SPS Commerce before go-live, and it requires the label on every carton plus a printed packing list on the first one, per its vendor site. Pipe17 provides GS1-128 carton label data by API. Printing and applying each label falls to your warehouse or to a 3PL like ShipBob, and URBN's test confirms the result.

URBN sends a changed purchase order as a replacement purchase order (850) rather than a PO change (860), per its EDI program page, and a PO must be accepted in Tradestone before its ship date to transmit. Pipe17 receives every replacement 850 and answers with a 997 functional acknowledgment. Setup decides how a replacement lines up with the original along the EDI order flow and in NetSuite or your ERP.

Yes, Pipe17 connects to Rithum (DSCO), URBN's platform for vendors shipping to its customers, through its CommerceHub DSCO connection, separate from the EDI program. URBN's drop-ship routing guide asks vendors to post tracking in Rithum within 24 hours of shipping and to include a vendor invoice number, mapped during setup. Pipe17 returns tracking once your warehouse confirms the shipment, keeping drop ship alongside EDI in one order queue.

Vendors who also sell on their own site, whether on Shopify or another platform, on marketplaces, or to other wholesale accounts get the most, because managed EDI from Pipe17 comes bundled with its full platform. A vendor whose only channel is URBN, with no direct or marketplace orders to manage, can check who managed EDI is built for first.