Trade with Big Lots – Fast, Easy, Scalable EDI Integration

Big Lots EDI 810 Invoices must include the invoice number and date in the BIG segment, the original PO reference number, line-item detail with UPCs, quantities shipped, and unit prices in the IT1 segments, plus the total monetary value in TDS. Big Lots requires exact alignment between the 810 Invoice, the original 850 Purchase Order, and the 856 ASN — this three-way match prevents deductions and chargebacks. Stacksync cross-validates all three documents automatically before transmitting the 810 to ensure every field matches Big Lots's accounts payable validation rules.

Big Lots typically requires the EDI 856 Advance Ship Notice to be transmitted within hours of shipment — not days before delivery. The ASN must be sent after the carrier picks up the freight but before the shipment arrives at Big Lots's receiving dock. Late or missing ASNs often result in compliance chargebacks and can cause receiving delays at the distribution center. Stacksync triggers 856 generation automatically when your WMS or shipping system confirms dispatch, ensuring the ASN reaches Big Lots within the required window without manual intervention from your logistics team.

Big Lots expects EDI 214 Shipment Status Messages at key milestones: pickup (status code X3), in-transit checkpoints (X1), delivery appointment scheduled (X6), arrived at delivery (X1), and delivered (D1). Some Big Lots programs also require departure from origin, border crossing for international loads, and out-for-delivery notifications. Each 214 includes a timestamp, location, and the shipment reference number linking it to the original 204 tender. Stacksync generates 214 updates automatically from your GPS tracking or TMS milestone events, keeping Big Lots's visibility platform current without manual status entry.

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.

Big Lots EDI 810 Invoices must include the invoice number and date in the BIG segment, the original PO reference number, line-item detail with UPCs, quantities shipped, and unit prices in the IT1 segments, plus the total monetary value in TDS. Big Lots requires exact alignment between the 810 Invoice, the original 850 Purchase Order, and the 856 ASN — this three-way match prevents deductions and chargebacks. Stacksync cross-validates all three documents automatically before transmitting the 810 to ensure every field matches Big Lots's accounts payable validation rules.

Big Lots typically requires the EDI 856 Advance Ship Notice to be transmitted within hours of shipment — not days before delivery. The ASN must be sent after the carrier picks up the freight but before the shipment arrives at Big Lots's receiving dock. Late or missing ASNs often result in compliance chargebacks and can cause receiving delays at the distribution center. Stacksync triggers 856 generation automatically when your WMS or shipping system confirms dispatch, ensuring the ASN reaches Big Lots within the required window without manual intervention from your logistics team.

A Big Lots EDI 204 is an electronic request from a shipper or broker to a carrier to transport a load. It contains the pickup and delivery locations, commodity descriptions, weight, equipment requirements, and requested dates. Big Lots sends 204s to carriers in their network to tender freight for acceptance. The carrier responds with a 990 (Response to a Load Tender) to accept or decline. Stacksync processes Big Lots 204 tenders automatically, extracting shipment details and routing them to your TMS or dispatch system for immediate action by your operations team.

A Big Lots EDI 860 Purchase Order Change can modify quantities, prices, delivery dates, ship-to addresses, item substitutions, and add or cancel individual line items on an existing PO. The BCH segment specifies the change type — full replacement, partial change, or cancellation. Big Lots uses 860s instead of canceling and reissuing entire 850s for efficiency, especially when only a few lines need adjustment. Stacksync processes incoming Big Lots 860s by automatically updating the original PO record in your system, maintaining a change history for audit purposes.

Big Lots expects EDI 214 Shipment Status Messages at key milestones: pickup (status code X3), in-transit checkpoints (X1), delivery appointment scheduled (X6), arrived at delivery (X1), and delivered (D1). Some Big Lots programs also require departure from origin, border crossing for international loads, and out-for-delivery notifications. Each 214 includes a timestamp, location, and the shipment reference number linking it to the original 204 tender. Stacksync generates 214 updates automatically from your GPS tracking or TMS milestone events, keeping Big Lots's visibility platform current without manual status entry.

A Big Lots EDI 990 is the carrier's response to a 204 Motor Carrier Load Tender. It communicates whether the carrier accepts, rejects, or conditionally accepts the tendered load. The B1 segment contains the response code: A (accepted), D (declined), or other qualifiers for conditional responses. The 990 references the original 204 by shipment ID so Big Lots can match the response to the correct load. Stacksync generates 990 responses automatically based on your fleet capacity and lane preferences, ensuring timely tender responses that protect your preferred carrier standing with Big Lots.

A Big Lots EDI 204 is an electronic request from a shipper or broker to a carrier to transport a load. It contains the pickup and delivery locations, commodity descriptions, weight, equipment requirements, and requested dates. Big Lots sends 204s to carriers in their network to tender freight for acceptance. The carrier responds with a 990 (Response to a Load Tender) to accept or decline. Stacksync processes Big Lots 204 tenders automatically, extracting shipment details and routing them to your TMS or dispatch system for immediate action by your operations team.

A Big Lots EDI 860 Purchase Order Change can modify quantities, prices, delivery dates, ship-to addresses, item substitutions, and add or cancel individual line items on an existing PO. The BCH segment specifies the change type — full replacement, partial change, or cancellation. Big Lots uses 860s instead of canceling and reissuing entire 850s for efficiency, especially when only a few lines need adjustment. Stacksync processes incoming Big Lots 860s by automatically updating the original PO record in your system, maintaining a change history for audit purposes.

A Big Lots EDI 990 is the carrier's response to a 204 Motor Carrier Load Tender. It communicates whether the carrier accepts, rejects, or conditionally accepts the tendered load. The B1 segment contains the response code: A (accepted), D (declined), or other qualifiers for conditional responses. The 990 references the original 204 by shipment ID so Big Lots can match the response to the correct load. Stacksync generates 990 responses automatically based on your fleet capacity and lane preferences, ensuring timely tender responses that protect your preferred carrier standing with Big Lots.

Big Lots EDI 850 Purchase Orders contain item-level detail including UPCs or GTINs, ordered quantities, unit pricing, ship-to addresses, and requested delivery dates. Key segments like BEG (beginning of the PO), PO1 (line items), N1 (party identification), and CTT (transaction totals) structure the document. Big Lots sends 850s electronically through their EDI network, and each PO must be acknowledged with an 855 to confirm receipt. Stacksync parses these fields and maps them directly to your ERP or database so orders appear automatically without manual data entry or CSV imports.

Big Lots EDI 850 Purchase Orders contain item-level detail including UPCs or GTINs, ordered quantities, unit pricing, ship-to addresses, and requested delivery dates. Key segments like BEG (beginning of the PO), PO1 (line items), N1 (party identification), and CTT (transaction totals) structure the document. Big Lots sends 850s electronically through their EDI network, and each PO must be acknowledged with an 855 to confirm receipt. Stacksync parses these fields and maps them directly to your ERP or database so orders appear automatically without manual data entry or CSV imports.

Most Big Lots programs expect EDI 214 updates at every significant milestone — typically pickup, each major transit point, and delivery. Some high-priority Big Lots lanes require periodic in-transit updates every 4 to 8 hours, regardless of milestone events. The key is that Big Lots should never need to call your dispatch for a status check. Stacksync integrates with your ELD or GPS provider and sends 214 updates automatically based on geofence triggers or scheduled intervals, ensuring Big Lots has continuous visibility without your dispatch team manually generating status messages.

No. Stacksync handles the entire EDI transport layer. We connect directly to Big Lots's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

Carriers respond to a Big Lots 204 Load Tender with an EDI 990 (Response to a Load Tender). The 990 includes an acceptance or rejection code — carriers can accept the load as tendered, accept with modifications, or decline. Big Lots typically expects a 990 response within a specific timeframe (often 30 minutes to 2 hours). Failure to respond may result in the load being retendered to another carrier. Stacksync automates 990 responses based on your fleet capacity and dispatch rules, ensuring timely acceptance of profitable loads and automatic declination when capacity is full.

Big Lots typically expects an EDI 990 response within 30 minutes to 2 hours of sending the 204 Load Tender. The exact window depends on Big Lots's tender process — some use a waterfall approach where the load is automatically retendered to the next carrier if no 990 is received within the time limit. Slow responses mean lost loads and reduced tender volume over time. Stacksync processes incoming Big Lots 204 tenders and generates 990 responses in real time, often within seconds, based on your pre-configured acceptance rules so you never miss a tender deadline.

The Big Lots EDI 856 uses hierarchical levels (HL segments) to describe the shipment structure from top to bottom: shipment level, order level, pack level (cartons or pallets), and item level. Each level contains specific data — the shipment level holds carrier and BOL information, the pack level includes SSCC-18 barcodes and carton dimensions, and the item level lists UPCs and quantities per package. Stacksync builds this hierarchy automatically from your WMS packing data, mapping carton contents and pallet configurations into the correct HL structure required by Big Lots.

Stacksync prevents Big Lots 810 rejections through automated three-way matching. Before generating an invoice, Stacksync compares line-item quantities and pricing against the original 850 Purchase Order and the 856 ASN. Discrepancies in UPCs, unit prices, quantities, or allowance amounts are flagged before the 810 is transmitted, giving your team a chance to correct errors. The platform also validates Big Lots-specific formatting requirements like date formats, decimal precision, and required qualifier codes. This preemptive validation eliminates the most common causes of Big Lots invoice chargebacks.

Stacksync processes incoming Big Lots 850 Purchase Orders in real time, typically within seconds of receipt. The platform validates the X12 envelope, parses all segments, maps fields to your system's schema, and inserts the order record automatically. Unlike batch-processing EDI providers that run on scheduled intervals, Stacksync's event-driven architecture means your team sees new Big Lots POs immediately. This speed is critical for meeting Big Lots's tight fulfillment windows and maintaining high on-time in-full compliance scores.

Big Lots generally prefers EDI 860 for modifications to existing POs rather than canceling and reissuing the entire 850. The 860 is more efficient because it targets specific changes — a quantity adjustment on one line item, a revised ship date, or an added line — without disrupting the rest of the order. Canceling and reissuing creates a new PO number and can cause confusion in warehouse operations. Stacksync handles both workflows, but when a Big Lots 860 arrives, it applies the changes incrementally to your existing order record rather than creating a duplicate entry.

Carriers respond to a Big Lots 204 Load Tender with an EDI 990 (Response to a Load Tender). The 990 includes an acceptance or rejection code — carriers can accept the load as tendered, accept with modifications, or decline. Big Lots typically expects a 990 response within a specific timeframe (often 30 minutes to 2 hours). Failure to respond may result in the load being retendered to another carrier. Stacksync automates 990 responses based on your fleet capacity and dispatch rules, ensuring timely acceptance of profitable loads and automatic declination when capacity is full.

Big Lots typically expects an EDI 990 response within 30 minutes to 2 hours of sending the 204 Load Tender. The exact window depends on Big Lots's tender process — some use a waterfall approach where the load is automatically retendered to the next carrier if no 990 is received within the time limit. Slow responses mean lost loads and reduced tender volume over time. Stacksync processes incoming Big Lots 204 tenders and generates 990 responses in real time, often within seconds, based on your pre-configured acceptance rules so you never miss a tender deadline.

Most Big Lots programs expect EDI 214 updates at every significant milestone — typically pickup, each major transit point, and delivery. Some high-priority Big Lots lanes require periodic in-transit updates every 4 to 8 hours, regardless of milestone events. The key is that Big Lots should never need to call your dispatch for a status check. Stacksync integrates with your ELD or GPS provider and sends 214 updates automatically based on geofence triggers or scheduled intervals, ensuring Big Lots has continuous visibility without your dispatch team manually generating status messages.

The Big Lots EDI 856 uses hierarchical levels (HL segments) to describe the shipment structure from top to bottom: shipment level, order level, pack level (cartons or pallets), and item level. Each level contains specific data — the shipment level holds carrier and BOL information, the pack level includes SSCC-18 barcodes and carton dimensions, and the item level lists UPCs and quantities per package. Stacksync builds this hierarchy automatically from your WMS packing data, mapping carton contents and pallet configurations into the correct HL structure required by Big Lots.

Stacksync prevents Big Lots 810 rejections through automated three-way matching. Before generating an invoice, Stacksync compares line-item quantities and pricing against the original 850 Purchase Order and the 856 ASN. Discrepancies in UPCs, unit prices, quantities, or allowance amounts are flagged before the 810 is transmitted, giving your team a chance to correct errors. The platform also validates Big Lots-specific formatting requirements like date formats, decimal precision, and required qualifier codes. This preemptive validation eliminates the most common causes of Big Lots invoice chargebacks.

Stacksync processes incoming Big Lots 850 Purchase Orders in real time, typically within seconds of receipt. The platform validates the X12 envelope, parses all segments, maps fields to your system's schema, and inserts the order record automatically. Unlike batch-processing EDI providers that run on scheduled intervals, Stacksync's event-driven architecture means your team sees new Big Lots POs immediately. This speed is critical for meeting Big Lots's tight fulfillment windows and maintaining high on-time in-full compliance scores.

Big Lots generally prefers EDI 860 for modifications to existing POs rather than canceling and reissuing the entire 850. The 860 is more efficient because it targets specific changes — a quantity adjustment on one line item, a revised ship date, or an added line — without disrupting the rest of the order. Canceling and reissuing creates a new PO number and can cause confusion in warehouse operations. Stacksync handles both workflows, but when a Big Lots 860 arrives, it applies the changes incrementally to your existing order record rather than creating a duplicate entry.

Most Big Lots compliance programs require the EDI 810 Invoice to be sent after the 856 ASN but within a specific window — typically 24 to 72 hours after shipment. Invoicing too early (before the ASN) or too late (beyond the allowed window) can trigger compliance penalties or payment delays. Big Lots may also require that invoice dates match or follow the ship date on the corresponding 856. Stacksync automates this timing by generating the 810 automatically after the 856 is confirmed, ensuring correct sequencing and compliance with Big Lots's deadlines.

When you send a Big Lots 990 with a decline code (D), Big Lots's system removes you from consideration for that specific load and retenders it to the next carrier in their routing guide. Declining loads is normal and expected — carriers cannot accept every tender. However, consistently declining Big Lots tenders may reduce your standing in their carrier ranking and lead to fewer tender opportunities over time. Stacksync tracks your acceptance ratio for Big Lots and alerts you when declining too many loads might impact your preferred carrier status.

The most frequent rejection causes for Big Lots 850s include invalid UPC or GTIN codes, incorrect ship-to location identifiers, quantities that don't match Big Lots's rounding requirements, and missing mandatory segments. Formatting issues like incorrect date formats in the DTM segment or invalid N1 qualifier codes also trigger rejections. Stacksync validates every incoming Big Lots 850 against known compliance requirements before syncing to your system, flagging anomalies immediately rather than silently dropping the transaction.

The most frequent rejection causes for Big Lots 850s include invalid UPC or GTIN codes, incorrect ship-to location identifiers, quantities that don't match Big Lots's rounding requirements, and missing mandatory segments. Formatting issues like incorrect date formats in the DTM segment or invalid N1 qualifier codes also trigger rejections. Stacksync validates every incoming Big Lots 850 against known compliance requirements before syncing to your system, flagging anomalies immediately rather than silently dropping the transaction.

When Stacksync receives a Big Lots 860, it identifies the original PO by reference number, compares the changed fields against the current order in your system, and applies the updates automatically. Quantity increases or decreases are reflected in your ERP's line items, new lines are appended, and canceled lines are flagged. Stacksync maintains a version history showing what changed and when, making it easy to trace modifications for compliance auditing. If a change conflicts with your fulfillment status (e.g., reducing quantity on items already shipped), Stacksync alerts your team immediately.

A SCAC (Standard Carrier Alpha Code) is a unique 2-to-4 letter identifier assigned by the National Motor Freight Traffic Association (NMFTA) to transportation carriers. Big Lots uses SCAC codes in EDI 204 tenders to identify the carrier being tendered the load, and carriers must include their SCAC in the 990 response and subsequent status updates (214). Without a valid SCAC, Big Lots's system cannot route the tender or track the shipment. Stacksync stores your SCAC code and automatically includes it in all outbound EDI documents, ensuring proper carrier identification across all Big Lots transactions.

A SCAC (Standard Carrier Alpha Code) is a unique 2-to-4 letter identifier assigned by the National Motor Freight Traffic Association (NMFTA) to transportation carriers. Big Lots uses SCAC codes in EDI 204 tenders to identify the carrier being tendered the load, and carriers must include their SCAC in the 990 response and subsequent status updates (214). Without a valid SCAC, Big Lots's system cannot route the tender or track the shipment. Stacksync stores your SCAC code and automatically includes it in all outbound EDI documents, ensuring proper carrier identification across all Big Lots transactions.

When you send a Big Lots 990 with a decline code (D), Big Lots's system removes you from consideration for that specific load and retenders it to the next carrier in their routing guide. Declining loads is normal and expected — carriers cannot accept every tender. However, consistently declining Big Lots tenders may reduce your standing in their carrier ranking and lead to fewer tender opportunities over time. Stacksync tracks your acceptance ratio for Big Lots and alerts you when declining too many loads might impact your preferred carrier status.

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

Missing or late EDI 214 updates can result in Big Lots chargebacks, reduced carrier scorecard ratings, and loss of preferred carrier status. Big Lots uses 214 data for dock scheduling, inventory planning, and customer notifications — when status updates are missing, it creates operational blind spots. In some Big Lots programs, consecutive 214 failures trigger automatic load retendering to backup carriers. Stacksync monitors 214 delivery and alerts your team if a status update fails to transmit, allowing you to resend before Big Lots escalates the issue.

Penalties for Big Lots ASN errors vary by the type of mistake and your compliance scorecard tier. Common chargeable errors include missing or late ASNs, incorrect carton counts, wrong item quantities, invalid SSCC-18 labels, and mismatches between the ASN and actual received goods. These penalties can range from flat fees per incident to percentage-based fines on the shipment value. Stacksync validates every 856 against the original PO data and your shipping records before transmission, catching errors that would otherwise result in Big Lots chargebacks. The platform maintains an audit trail for dispute resolution.

When Stacksync receives a Big Lots 860, it identifies the original PO by reference number, compares the changed fields against the current order in your system, and applies the updates automatically. Quantity increases or decreases are reflected in your ERP's line items, new lines are appended, and canceled lines are flagged. Stacksync maintains a version history showing what changed and when, making it easy to trace modifications for compliance auditing. If a change conflicts with your fulfillment status (e.g., reducing quantity on items already shipped), Stacksync alerts your team immediately.

Most Big Lots compliance programs require the EDI 810 Invoice to be sent after the 856 ASN but within a specific window — typically 24 to 72 hours after shipment. Invoicing too early (before the ASN) or too late (beyond the allowed window) can trigger compliance penalties or payment delays. Big Lots may also require that invoice dates match or follow the ship date on the corresponding 856. Stacksync automates this timing by generating the 810 automatically after the 856 is confirmed, ensuring correct sequencing and compliance with Big Lots's deadlines.

Missing or late EDI 214 updates can result in Big Lots chargebacks, reduced carrier scorecard ratings, and loss of preferred carrier status. Big Lots uses 214 data for dock scheduling, inventory planning, and customer notifications — when status updates are missing, it creates operational blind spots. In some Big Lots programs, consecutive 214 failures trigger automatic load retendering to backup carriers. Stacksync monitors 214 delivery and alerts your team if a status update fails to transmit, allowing you to resend before Big Lots escalates the issue.

Penalties for Big Lots ASN errors vary by the type of mistake and your compliance scorecard tier. Common chargeable errors include missing or late ASNs, incorrect carton counts, wrong item quantities, invalid SSCC-18 labels, and mismatches between the ASN and actual received goods. These penalties can range from flat fees per incident to percentage-based fines on the shipment value. Stacksync validates every 856 against the original PO data and your shipping records before transmission, catching errors that would otherwise result in Big Lots chargebacks. The platform maintains an audit trail for dispute resolution.

Stacksync connects to your TMS, ELD, or GPS tracking system and automatically generates Big Lots 214 messages when shipment events occur. When a driver checks in at pickup, crosses a geofence, or completes delivery, Stacksync captures the event, formats the 214 with the correct status code, location, and timestamp, and transmits it to Big Lots's EDI network. The platform handles appointment codes, exception reporting (delays, refused deliveries), and proof-of-delivery confirmation. Your drivers continue using their existing tools while Stacksync handles the EDI compliance layer automatically.

Yes. Stacksync can automatically generate a 990 acceptance response when a Big Lots 204 matches your configured criteria — such as approved lanes, equipment type availability, weight limits, and date range. You define the rules once, and Stacksync evaluates each incoming tender against them. Loads that match are accepted automatically with a 990, while loads outside your criteria are either declined or routed to your dispatch team for manual decision. This hybrid approach ensures you capture desirable Big Lots loads instantly while maintaining human oversight for edge cases.

Stacksync connects to your TMS, ELD, or GPS tracking system and automatically generates Big Lots 214 messages when shipment events occur. When a driver checks in at pickup, crosses a geofence, or completes delivery, Stacksync captures the event, formats the 214 with the correct status code, location, and timestamp, and transmits it to Big Lots's EDI network. The platform handles appointment codes, exception reporting (delays, refused deliveries), and proof-of-delivery confirmation. Your drivers continue using their existing tools while Stacksync handles the EDI compliance layer automatically.

Some Big Lots trading programs require an EDI 865 (Purchase Order Change Acknowledgment) in response to every 860. The 865 confirms that you received the change request and indicates whether you accept the modifications, reject them, or need further negotiation. Even when not mandatory, sending an 865 is good practice because it closes the communication loop and prevents Big Lots from resending the same change. Stacksync can generate 865 responses automatically based on your acceptance rules, similar to how it handles 855 PO acknowledgments.

Yes. Stacksync can automatically generate a 990 acceptance response when a Big Lots 204 matches your configured criteria — such as approved lanes, equipment type availability, weight limits, and date range. You define the rules once, and Stacksync evaluates each incoming tender against them. Loads that match are accepted automatically with a 990, while loads outside your criteria are either declined or routed to your dispatch team for manual decision. This hybrid approach ensures you capture desirable Big Lots loads instantly while maintaining human oversight for edge cases.

Big Lots typically requires an EDI 855 Purchase Order Acknowledgment for every 850 received. The 855 confirms that you received the PO and indicates whether you can fulfill it as ordered, need to modify quantities, or must reject specific line items. Most Big Lots compliance programs expect the 855 within 24 to 48 hours of PO receipt. Stacksync can generate and send 855 acknowledgments automatically based on your acceptance rules, ensuring you never miss a compliance deadline. A 997 Functional Acknowledgment may also be required as a separate technical receipt.

The most common causes of Big Lots 810 chargebacks include price discrepancies between the invoice and the PO, quantity mismatches between the invoice and the ASN, missing or incorrect allowance and charge amounts in the SAC segment, and wrong UPC or item identification codes. Late invoicing beyond Big Lots's deadline also triggers deductions. Stacksync reduces these errors by automatically populating 810 fields from the matched 850 PO and 856 ASN data, ensuring consistency across all three documents and tracking deduction trends for resolution.

Most Big Lots programs require SSCC-18 (Serial Shipping Container Code) labels on every carton and pallet, with the corresponding barcodes referenced in the 856 ASN's MAN (Marks and Numbers) segment. The SSCC-18 is a unique 18-digit identifier that links the physical package to the electronic ASN data, enabling Big Lots's receiving dock to scan and verify shipments against the advance notice. Stacksync generates SSCC-18 numbers that comply with GS1 standards and embeds them in the 856 automatically. If your WMS already assigns SSCC-18s, Stacksync pulls those values directly from your packing records.

The most common causes of Big Lots 810 chargebacks include price discrepancies between the invoice and the PO, quantity mismatches between the invoice and the ASN, missing or incorrect allowance and charge amounts in the SAC segment, and wrong UPC or item identification codes. Late invoicing beyond Big Lots's deadline also triggers deductions. Stacksync reduces these errors by automatically populating 810 fields from the matched 850 PO and 856 ASN data, ensuring consistency across all three documents and tracking deduction trends for resolution.

Stacksync supports all EDI document types required by Big Lots — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Some Big Lots trading programs require an EDI 865 (Purchase Order Change Acknowledgment) in response to every 860. The 865 confirms that you received the change request and indicates whether you accept the modifications, reject them, or need further negotiation. Even when not mandatory, sending an 865 is good practice because it closes the communication loop and prevents Big Lots from resending the same change. Stacksync can generate 865 responses automatically based on your acceptance rules, similar to how it handles 855 PO acknowledgments.

Most Big Lots programs require SSCC-18 (Serial Shipping Container Code) labels on every carton and pallet, with the corresponding barcodes referenced in the 856 ASN's MAN (Marks and Numbers) segment. The SSCC-18 is a unique 18-digit identifier that links the physical package to the electronic ASN data, enabling Big Lots's receiving dock to scan and verify shipments against the advance notice. Stacksync generates SSCC-18 numbers that comply with GS1 standards and embeds them in the 856 automatically. If your WMS already assigns SSCC-18s, Stacksync pulls those values directly from your packing records.

Yes, Big Lots EDI 204 supports multi-stop shipments through multiple S5 (Stop Off Details) segments. Each stop includes the facility address, stop type (pickup or delivery), scheduled date and time window, and the specific freight being handled at that location. The stops are sequenced to define the route order. Stacksync maps multi-stop Big Lots 204 tenders into your TMS routing system, creating individual stop records with proper sequencing so your dispatch team sees the complete route plan without manually parsing the EDI document.

Yes, Big Lots EDI 204 supports multi-stop shipments through multiple S5 (Stop Off Details) segments. Each stop includes the facility address, stop type (pickup or delivery), scheduled date and time window, and the specific freight being handled at that location. The stops are sequenced to define the route order. Stacksync maps multi-stop Big Lots 204 tenders into your TMS routing system, creating individual stop records with proper sequencing so your dispatch team sees the complete route plan without manually parsing the EDI document.

Big Lots typically requires an EDI 855 Purchase Order Acknowledgment for every 850 received. The 855 confirms that you received the PO and indicates whether you can fulfill it as ordered, need to modify quantities, or must reject specific line items. Most Big Lots compliance programs expect the 855 within 24 to 48 hours of PO receipt. Stacksync can generate and send 855 acknowledgments automatically based on your acceptance rules, ensuring you never miss a compliance deadline. A 997 Functional Acknowledgment may also be required as a separate technical receipt.

Stacksync connects to your WMS, ERP, or shipping platform and monitors for shipment confirmations. When an order is marked as shipped, Stacksync extracts the packing details — carton contents, weights, dimensions, carrier information, tracking numbers, and SSCC-18 labels — and constructs the 856 ASN document automatically. The platform maps your warehouse data to Big Lots's required HL hierarchy, populates the BSN, TD1, and REF segments, and validates the complete document before transmitting it. The entire process runs without manual EDI formatting, reducing ASN errors and keeping your Big Lots compliance scores high.

Yes. The EDI 214 provides an independent record of when pickup and delivery actually occurred, which is essential for auditing freight invoices (EDI 210). If a carrier's 210 invoice claims accessorial charges for detention, the 214 timestamps prove how long the driver waited. If a delivery date on the invoice doesn't match the 214 delivery confirmation, it signals a billing discrepancy. Stacksync cross-references 214 data with 210 invoices automatically, flagging mismatches in dates, locations, and service events for your freight audit review.

Stacksync uses a visual field mapping interface to connect Big Lots 850 segments — such as BEG for PO header data, PO1 for line items, and N1 for party identification — to the corresponding fields in your ERP, WMS, or database. You configure the mapping once, and Stacksync applies it to every subsequent Big Lots 850 automatically. The platform handles data type conversions, conditional logic for optional fields, and Big Lots-specific formatting requirements. If Big Lots changes their 850 specification, Stacksync alerts you and suggests mapping updates.

When a Big Lots 204 includes multiple stops (S5 segments), Stacksync evaluates the entire route before generating the 990 response — not just the origin and destination. The platform checks capacity for each stop, validates that pickup and delivery windows are feasible given transit times, and confirms equipment compatibility at every location. If all stops meet your criteria, Stacksync sends a 990 acceptance for the full multi-stop load. If any stop presents a conflict, the platform flags it for your dispatcher rather than auto-declining the entire tender.

When a Big Lots 204 includes multiple stops (S5 segments), Stacksync evaluates the entire route before generating the 990 response — not just the origin and destination. The platform checks capacity for each stop, validates that pickup and delivery windows are feasible given transit times, and confirms equipment compatibility at every location. If all stops meet your criteria, Stacksync sends a 990 acceptance for the full multi-stop load. If any stop presents a conflict, the platform flags it for your dispatcher rather than auto-declining the entire tender.

Yes. Stacksync supports the SAC (Service, Promotion, Allowance, or Charge) and TXI (Tax Information) segments used in Big Lots 810 Invoices. The platform can apply Big Lots-specific allowance schedules, cooperative advertising deductions, and volume rebates automatically based on the terms in the original PO. Tax calculations are handled according to the ship-to jurisdiction. Stacksync maps these calculations from your billing system's output to the correct EDI segment codes and qualifiers, ensuring Big Lots receives properly formatted financial data.

Yes. Stacksync supports the SAC (Service, Promotion, Allowance, or Charge) and TXI (Tax Information) segments used in Big Lots 810 Invoices. The platform can apply Big Lots-specific allowance schedules, cooperative advertising deductions, and volume rebates automatically based on the terms in the original PO. Tax calculations are handled according to the ship-to jurisdiction. Stacksync maps these calculations from your billing system's output to the correct EDI segment codes and qualifiers, ensuring Big Lots receives properly formatted financial data.

Yes. The EDI 214 provides an independent record of when pickup and delivery actually occurred, which is essential for auditing freight invoices (EDI 210). If a carrier's 210 invoice claims accessorial charges for detention, the 214 timestamps prove how long the driver waited. If a delivery date on the invoice doesn't match the 214 delivery confirmation, it signals a billing discrepancy. Stacksync cross-references 214 data with 210 invoices automatically, flagging mismatches in dates, locations, and service events for your freight audit review.

Yes, Big Lots can modify unit pricing on existing PO line items through the EDI 860. Price changes appear in the PO1 segment with updated unit price values. However, pricing changes via 860 may be subject to Big Lots's vendor agreement terms — some programs restrict supplier-initiated price changes and only allow buyer-initiated modifications. Stacksync validates incoming Big Lots 860 price changes against your contracted pricing and flags discrepancies. Your team can review and approve price adjustments before they flow into your billing system, preventing unexpected margin impacts.

Stacksync connects to your TMS or dispatch system and processes incoming Big Lots 204 tenders in real time. When a tender arrives, Stacksync extracts the shipment details — origin, destination, commodity, weight, equipment type, and pickup/delivery windows — and creates a load record in your system. Based on your capacity rules and lane preferences, Stacksync can auto-accept loads with a 990 response or route them to your dispatch queue for manual review. The platform tracks tender acceptance rates and response times to help you maintain preferred carrier status with Big Lots.

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Big Lots's EDI network and your system in real time.

Stacksync connects to your WMS, ERP, or shipping platform and monitors for shipment confirmations. When an order is marked as shipped, Stacksync extracts the packing details — carton contents, weights, dimensions, carrier information, tracking numbers, and SSCC-18 labels — and constructs the 856 ASN document automatically. The platform maps your warehouse data to Big Lots's required HL hierarchy, populates the BSN, TD1, and REF segments, and validates the complete document before transmitting it. The entire process runs without manual EDI formatting, reducing ASN errors and keeping your Big Lots compliance scores high.

Stacksync uses a visual field mapping interface to connect Big Lots 850 segments — such as BEG for PO header data, PO1 for line items, and N1 for party identification — to the corresponding fields in your ERP, WMS, or database. You configure the mapping once, and Stacksync applies it to every subsequent Big Lots 850 automatically. The platform handles data type conversions, conditional logic for optional fields, and Big Lots-specific formatting requirements. If Big Lots changes their 850 specification, Stacksync alerts you and suggests mapping updates.

Stacksync connects to your TMS or dispatch system and processes incoming Big Lots 204 tenders in real time. When a tender arrives, Stacksync extracts the shipment details — origin, destination, commodity, weight, equipment type, and pickup/delivery windows — and creates a load record in your system. Based on your capacity rules and lane preferences, Stacksync can auto-accept loads with a 990 response or route them to your dispatch queue for manual review. The platform tracks tender acceptance rates and response times to help you maintain preferred carrier status with Big Lots.

Yes, Big Lots can modify unit pricing on existing PO line items through the EDI 860. Price changes appear in the PO1 segment with updated unit price values. However, pricing changes via 860 may be subject to Big Lots's vendor agreement terms — some programs restrict supplier-initiated price changes and only allow buyer-initiated modifications. Stacksync validates incoming Big Lots 860 price changes against your contracted pricing and flags discrepancies. Your team can review and approve price adjustments before they flow into your billing system, preventing unexpected margin impacts.

Stacksync monitors Big Lots's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.