# Burlington Stores

> Burlington Stores, Inc. (NYSE: BURL) is a US national off-price retailer of brand-name
> apparel, footwear, accessories, baby products and home decor, operating more than 1,200
> stores. Burlington publishes NO public developer API — no OpenAPI, GraphQL, gRPC, SOAP
> or event contract exists on any host it controls. Its only documented machine-to-machine
> integration surface is ASC X12 version 4010 EDI for merchandise vendors and freight
> carriers, and those implementation guides ARE public.

## Provenance

- Generated by the API Evangelist enrichment pipeline on 2026-09-05.
- method: generated — assembled from apis.yml and the artifacts in this repo, all of which
  were probed or searched on 2026-09-05. Burlington serves no llms.txt of its own:
  https://www.burlington.com/llms.txt returns HTTP 200 with the site's Next.js shell titled
  "404 Not Found | Burlington", which is a soft-404 and not a document.
- Burlington's robots.txt explicitly disallows AI crawlers, including ClaudeBot,
  Claude-Web, anthropic-ai, GPTBot, CCBot, Bytespider, cohere-ai and Applebot. This file
  describes the company for catalog purposes; it is not an invitation to crawl
  burlington.com. Honor https://www.burlington.com/robots.txt.

## What exists

- [EDI specifications](https://www.burlington.com/vendors/edi): the real integration
  contract. Seventeen ASC X12 4010 implementation guides as public PDFs with sample
  interchanges — 001 control segments, 810 invoice, 824 application advice, 850 purchase
  order, 852 product activity, 856 ASN, 860 PO change, 997 functional acknowledgment,
  832 price/sales catalog, 846 inventory availability, 858 shipment information, 204/210/
  211/214/990 motor carrier sets, and 855 non-merchandise POA.
- [GS1-128 bar code label specification](https://cdn.sanity.io/files/k5c6l842/production/cfa0f13b59c0668c1101af15dcb2e54da95cc9b4.pdf): serial shipping container label companion report, v3.0 Final.
- [Vendor manuals](https://www.burlington.com/vendors/vendor-manual): domestic and import
  vendor manuals, carton specs, chemical compliance, code of conduct — public PDFs.
- [Vendor Relations](https://www.burlington.com/vendors) and
  [Portals](https://www.burlington.com/vendors/portals): the three systems a Burlington
  vendor uses — Gateway (EDI, https://edi.coat.com), Traverse (compliance chargebacks,
  https://burl.traversesystems.com) and TMS (https://mip.logistics.com).
- [Burlington Vendor Portal](https://vendors.burlington.com): invite-only vendor login.

## What does not exist

- No developer portal, API reference, quickstart, sandbox, console or sign-up.
- No OpenAPI, Swagger, GraphQL SDL, AsyncAPI, .proto or WSDL on www.burlington.com,
  burlington.com, vendors.burlington.com or edi.coat.com.
- No MCP server, no A2A agent card, no llms.txt, no /.well-known/ documents of any kind.
- No first-party SDK on npm, PyPI, Maven Central, NuGet, RubyGems, crates.io or
  pkg.go.dev, and no Burlington GitHub organization.
- No public status page, changelog, deprecation policy, rate limits or developer pricing.
- No published security.txt, vulnerability disclosure programme or trust center.

## Company

- [Burlington.com](https://www.burlington.com): storefront and store locator.
- [Help Center](https://www.burlington.com/helpcenter)
- [Contact Us](https://www.burlington.com/helpcenter/contact-us)
- [Terms of Use](https://www.burlington.com/helpcenter/terms-of-use)
- [Privacy Policy](https://www.burlington.com/helpcenter/privacy-policy)
- [Your Privacy Choices](https://www.burlington.com/helpcenter/your-privacy-choices)
- [Media Room](https://www.burlington.com/media-room)
- [Investor Relations](https://www.burlingtoninvestors.com/)
- [Doing Business with Burlington](https://www.burlington.com/about/doing-business-with-burlington)

## Integration contacts

- EDI support: EDI.Support@burlington.com — (609) 387-7800 ext. 3340
- Vendor setup / Gateway access: vendor.setup@burlington.com
- Vendor relations: vendor.relations@burlington.com
- Vendor portal support: vendors@burlington.com

## How to integrate

There is no self-service path. Becoming a Burlington trading partner runs through Vendor
Relations; the EDI specification library is readable in advance without an account, but
the Gateway runtime that carries the interchanges requires credentials Burlington issues.
Read the contract first, then contact vendor.setup@burlington.com.