Sign In
Book a Demo

TJX Companies EDI Integration for Off-Price Vendors

Vendors selling closeouts, overruns, and in-season goods to TJ Maxx, Marshalls, and HomeGoods run each banner’s purchase orders on Pipe17 managed EDI, filled from the stock behind their other channels.
Book a demo
TJX Pipe17 Connector Icon

The Challenge of Off-Price Retail EDI

Closeout Lots, Separate Banners, and Early Ship Notices

Snail with a swirl black shell

Closeout Lots That Move Fast

TJX buys closeouts and overruns as they come up. If the same units still show available online, a lot sold to TJX gets sold twice.

Stacked user icons, representing sub-accounts or team access

Three Banners, Three Setups

TJ Maxx, Marshalls, and HomeGoods trade as separate EDI partners. Each banner's orders, ship notices, and invoices need their own connection and testing.

Shelved boxes, symbolizing warehouse inventory or fulfillment center

Ship Notices Ahead of the Freight

Supplier guides from EDI providers say TJX expects the 856 accepted before cartons reach its distribution center, with labels matching the ASN. Keyed ship notices fall behind the truck.

The Solution for TJX EDI Integration & Order Management

TJX Makes the Buy. Pipe17 Works Every Order After It.

Your TJX purchase orders have two homes: Pipe17’s managed EDI, or the EDI provider already running them. Once the document lands, scripts and a legacy OMS often track TJX lots apart from online stock. Pipe17 retires both with its Order Operations Platform, and every banner draws from one inventory 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) ❌ ❌ ✅

Future-Ready Brands and Fulfillment Providers Run on Pipe17

Sell to TJX from the Same Stock as Every Channel

Simple rocket icon, symbolizing launch or operational lift-off

One Count for Every Lot

Units committed to a TJX purchase order leave the pool your storefront and marketplaces sell from. A closeout committed to TJX stops appearing there as available stock.

Magnifying glass over graph, representing analytics across any data source

Each Banner on Its Own Connection

TJ Maxx, Marshalls, and HomeGoods orders run on separate trading-partner setups and land in one order queue alongside your other sales channels.

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

Ship Notices from Packed Cartons

The 856 builds from what your warehouse actually packed, with SSCCs matching the GS1-128 label data your team or 3PL applies.

Automated TJX Companies EDI Flows

Pipe17 connects to each TJX banner’s trading-partner setup through managed EDI. Every document below follows the specification your TJX EDI contact issues for your account.
  • Pull Orders from TJX. A TJ Maxx, Marshalls, or HomeGoods purchase order (850) shows up in Pipe17 as a separate order that keeps the banner and the TJX distribution center it ships to.
  • Push Order Confirmations to TJX. If your TJX program asks for an 855 acknowledgment, Pipe17 returns one confirming the full quantity or the smaller share of a closeout lot you can still ship.
  • Push Fulfillments to TJX. Because EDI provider guides say TJX wants the 856 accepted before freight reaches its distribution center, Pipe17 builds it from cartons as your warehouse confirms them, each SSCC matching that carton’s GS1-128 label.
  • Push Inventory to TJX. Where a TJX buyer requests inventory advice, Pipe17 sends an 846 counting only units not yet committed in your pool, which keeps a lot offered to TJX off your online count.
  • Push Invoices to TJX. When your TJX program bills over EDI, Pipe17 sends the 810 against each shipped PO. Setup confirms the invoicing method with TJX first.
  • Confirm Every TJX Transmission. Each TJX document Pipe17 takes in gets a 997 functional acknowledgment in return.
  • Log TJX Purchase Order Changes. When a TJX banner sends an 860 to revise a purchase order, Pipe17 takes the change request in and sends back a 997.
  • Hand Carton Label Data to the Dock. For each TJX carton, your warehouse or 3PL asks Pipe17’s API for the GS1-128 (UCC-128) content, then prints and applies it within the scope of your TJX program.
  • Send Each PO to the Building with the Lot. Routing rules pass every TJX order to whichever warehouse or 3PL is holding the goods TJX bought.
  • Book TJX Sales in Your ERP. Each TJX order can post to NetSuite or another ERP as a sales order, booked beside your other wholesale revenue.
  • Pass TJX Orders to an EDI-Based 3PL. If the 3PL shipping TJX orders works over EDI, Pipe17 issues it a 940 per order and it returns a 945 when the cartons leave.
  • Stop Orders That Miss a Rule. The Automation Engine holds a TJX order that fails one of your checks, such as a missing ship-to location, and alerts your team.

Connect TJX EDI to Your Off-Price Strategy

Closeouts and overruns sold to TJX share shelves with your direct site, marketplaces, and full-price accounts. One stock count covers them all, and a unit sold to TJX drops from the count other channels see.

Sell Your Surplus to TJX Without Selling It Twice

Bring your TJX setup, the banners you ship to, and your other sales channels. We will map how each TJX purchase order would run through Pipe17, from the 850 to carton labels and the ship notice.
Book a demo
TJX Companies horizontal svg logo black

is better with

Pipe17 horizontal svg logo black

TJX Companies EDI Integration FAQs

Yes, EDI providers list TJ Maxx, Marshalls, and HomeGoods as separate TJX trading partners with their own IDs, though all three follow the same TJX onboarding steps. Pipe17 sets up each banner you sell to as its own connection on the Pipe17 Network, following the managed EDI onboarding sequence, and orders from every banner fill from one pool. Other TJX banners, such as Sierra or Homesense, are confirmed during setup.

TJX expects the advance ship notice (856) to be transmitted and accepted before a shipment arrives at its distribution center, EDI providers report, and payment terms run from the date the DC receives the goods. Pipe17 builds each advance ship notice from cartons your warehouse confirms, ready as the freight leaves, one step on the path of an EDI order from purchase order to invoice.

Wherever your TJX program bills over EDI, the invoice travels as an 810, so confirm the invoicing method with your TJX EDI contact during setup. Pipe17 builds each 810 from the cartons that actually shipped, part of its core X12 document set, and the same order can post to NetSuite so your finance team can match payments to it.

Pipe17 treats a closeout, overrun, or canceled-order lot sold to TJX as stock in one shared pool. Units committed to a TJX purchase order (850) stop counting as available to your other channels. Your storefront, whether on Shopify or another ecommerce platform, and marketplaces such as Amazon read the same count, which also feeds inventory shared across EDI and DTC.

EDI providers report that TJX wants GS1-128 (UCC-128) carton labels built to its specification, no more than one purchase order and one distribution center per pallet, and no retail price tickets unless a TJX buyer orders pre-ticketed goods. Pipe17's API hands over the GS1-128 label data, while labels get printed, and pallets built to those rules, by your own warehouse or a 3PL like ShipBob.

Yes, your TJX banners can stay on SPS Commerce or whichever provider runs them now, and Pipe17 connects to that provider or to the ERP that provider feeds TJX orders into, such as Acumatica, with no retesting. Vendors with no provider for TJX use Pipe17's managed EDI, and the notes on keeping TJX with the provider you have cover both cases.