Skip to content

Lineage, Inc. EDI
integration guide.

Plan your Lineage, Inc. EDI integration using 4 listed document types across 1 channel. Compare channels, map business records and test the operational handoff.

Listed documents
4
Partner document references
Listed channels
1
Lineage
Implementation
Plan
Map, validate and reconcile

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Implementation guide

Lineage, Inc.: EDI implementation plan

Build a reliable EDI workflow for Lineage, Inc.. Use 4 document types across 1 channel to plan record mapping, prevent duplicate processing and reconcile results in your business systems.

The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 945 Warehouse Shipping AdviceListed on 1 channel: Lineage warehouse shipment confirmation

warehouse order, shipment and shipped line

  • Test partial fulfillment and leave the unshipped order quantity open.
  • Reconcile shipped units and tracking references before preparing a customer-facing shipment notice.
X12 943 Warehouse Stock Transfer Shipment AdviceListed on 1 channel: Lineage warehouse transfer shipment

transfer, sending location and shipped item

  • Test a transfer split across several shipments.
  • Record stock in transit without prematurely increasing available stock at the receiving warehouse.
X12 940 Warehouse Shipping OrderListed on 1 channel: Lineage warehouse fulfillment order

warehouse order, owner, ship-to and item

  • Test a cancellation after picking and define who approves any warehouse reversal.
  • Validate owner-specific SKU and unit mappings before allocating stock.
X12 944 Warehouse Stock Transfer Receipt AdviceListed on 1 channel: Lineage warehouse transfer receipt

transfer, receipt location and received item

  • Reconcile a short receipt with the shipped quantity and leave the difference open.
  • Separate damaged stock from saleable stock in the receiving balance.

Implementation steps

  1. Choose the trading account and channel

    Choose among Lineage. Confirm the business unit and account before copying a mapping from another channel.

  2. Map records and assign owners

    Start with warehouse shipment confirmation, warehouse transfer shipment, warehouse fulfillment order. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.

  3. Test a complete exchange

    Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Lineage, Inc. production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using warehouse order, shipment and shipped line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document flow

Example document relationships for Lineage, Inc.

Where each document sits in its trading cycle, based on the 4 document types listed for Lineage, Inc. across 1 channel. These are example relationships; the trading agreement determines the required sequence.

LEGACY EDI MIGRATION FUND

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 fund
Migrate from SPS Commerce
Migrate from Cleo
Migrate from TrueCommerce
Migrate from OpenText
SECURITY

Security 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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

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:

FAQ

Lineage, Inc. EDI questions

Which EDI documents are listed for Lineage, Inc.?

X12 945 Warehouse Shipping Advice; X12 943 Warehouse Stock Transfer Shipment Advice; X12 940 Warehouse Shipping Order; X12 944 Warehouse Stock Transfer Receipt Advice. Confirm which documents, directions and versions apply to your account.

How should I choose the Lineage, Inc. EDI channel?

The directory lists 1 channels for Lineage, Inc., including Lineage. Match the channel to your actual trading relationship and compare its document list before reusing a mapping.

Which identifiers should the Lineage, Inc. mapping preserve?

For X12 945 Warehouse Shipping Advice, plan around warehouse order, shipment and shipped line. For X12 943 Warehouse Stock Transfer Shipment Advice, use transfer, sending location and shipped item. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Lineage, Inc. accepted the business document?

Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.

What should be tested before launching Lineage, Inc. EDI?

Test partial fulfillment and leave the unshipped order quantity open. Reconcile shipped units and tracking references before preparing a customer-facing shipment notice. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.