Big Lots EDI
across every channel.
Stacksync wires the full Big Lots trading-partner footprint, Big Lots Stores Inc. (Transportation) (via Manhattan Associates), Big Lots Stores Inc., into your ERP, WMS, or warehouse from one workspace.
Adopted by fast-scaling companies moving mission-critical data in real time
Document catalog
EDI documents we support for Big Lots
7 transactions across 2 channels.
Big Lots Stores Inc.
4 docsDocument flow
How EDI documents flow with Big Lots
Where each document sits in its trading cycle, based on the 7 document types Big Lots trades across 2 channels.
Order-to-cash
Partial cycle- 850 Purchase Order
- 855 Purchase Order Acknowledgment not required by Big Lots
- 856 Ship Notice Manifest
- 810 Invoice
Logistics
Partial cycle- 204 Motor Carrier Load Tender
- 990 Response To A Load Tender
- 214 Transportation Carrier Shipment Status Message
- 210 Motor Carrier Freight Details and Invoice not required by Big Lots
- 204 Motor Carrier Load Tender — runs on 1 of Big Lots's 2 channels
- 214 Transportation Carrier Shipment Status Message — runs on 1 of Big Lots's 2 channels
- 810 Invoice — runs on 1 of Big Lots's 2 channels
- 850 Purchase Order — runs on 1 of Big Lots's 2 channels
- 856 Ship Notice Manifest — runs on 1 of Big Lots's 2 channels
- 860 Purchase Order Change Request Buyer Initiated — runs on 1 of Big Lots's 2 channels
- 990 Response To A Load Tender — runs on 1 of Big Lots's 2 channels
Network context
Big Lots trades through Manhattan Associates
EDI traffic with Big Lots is routed over this network. Stacksync maintains certified connections to each, so one integration covers every partner reachable on them.
Manhattan Associates
17 channels · 16 trading partners on Stacksync
Manhattan Associates is a supply chain software vendor, not a traditional VAN; its Manhattan Active Transportation Management TMS is what large shippers use to plan, tender, track, and settle freight. Partners that appear behind this gateway are exchanging transportation documents, 204 load tenders, 990 tender responses, 214 shipment statuses, and 210 freight invoices, with a shipper's Manhattan TMS instance. Manhattan also offers a pre-built carrier network intended to simplify carrier onboarding for its shipper customers.
Big Lots channel on this network: Big Lots Stores Inc. (Transportation) (via Manhattan Associates)
- 204 17 ch
- 214 17 ch
- 990 17 ch
- 210 9 ch
How it works
Three steps to live Big Lots EDI.
Stacksync handles the complexity of Big Lots EDI so your team doesn't have to. Connect your ERP, WMS, or database through a simple API, we translate, validate, and deliver every transaction automatically.
- 01
Connect your systems
Plug Stacksync into your ERP, WMS, or database with a no-code connector. We handle authentication, schema discovery, and field mapping.
- 02
Map to Big Lots guidelines
We ship pre-built mappings for every Big Lots document type. Override any field, add custom validation, or extend with custom code.
- 03
Send & receive in real time
Stacksync translates, validates, and delivers every transaction over AS2, SFTP, or API. Watch every document flow live in the dashboard.
Why Stacksync
Built for EDI suppliers, not enterprise legacy.
From pre-built Big Lots mappings to real-time compliance checks, Stacksync removes the friction from EDI, so you can focus on growing your business.
-
Pre-built mappings
Stacksync ships native mappings for every Big Lots document type. No more 6-week field-mapping projects.
-
Real-time monitoring
Every transaction shows up in the dashboard the second it lands, with retry, revert, and replay built in.
-
No vendor lock-in
Your data lives in your ERP/WMS/database. Stacksync is the translation layer, not the system of record.
-
Days, not months
Most Big Lots suppliers go live in under a week. We migrate from SPS Commerce, TrueCommerce, Cleo and IBM Sterling.
Still with a legacy EDI vendor? We cover the buyout.
Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.
Check your eligibility for the EDI migration fundSecurity teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Trading partners
5,000+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
FAQ
Big Lots EDI questions
How long does it take to set up Big Lots EDI with Stacksync?
Most suppliers are fully connected and processing live Big Lots EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.
What is Big Lots EDI?
Big Lots accepts EDI for 7 document types across 2 channels. Trading partners use EDI to exchange purchase orders, invoices, shipping notices, and acknowledgements with Big Lots programmatically, Stacksync handles the entire EDI exchange, validation, and translation into your ERP, WMS, or database.
Which EDI standards does Big Lots use?
Big Lots uses X12. Stacksync supports both X12 (the dominant North American standard) and EDIFACT (the dominant European and global shipping standard) for every connected trading partner. Channel-specific implementation guidelines from Big Lots are pre-built into the Stacksync connector and validated on every outbound transaction.
Which transaction codes does Big Lots support?
Big Lots supports 7 transaction codes in total. The most common include: 204, 990, 214, 856, 810, 850, 860. Each code is mapped to its business-record equivalent (purchase order, ASN, invoice, etc.) inside Stacksync, so EDI exchanges land directly in your ERP or warehouse without manual translation.
How long does Big Lots EDI integration take with Stacksync?
Most Big Lots EDI integrations go live in 3 to 10 business days. The Stacksync team handles partner enrolment, channel certification, transaction-set mapping per Big Lots's implementation guide, and end-to-end testing. Complex multi-channel deployments or custom transaction sets take 2 to 4 weeks. Cutover is zero-downtime and parallel-run validated.