Skip to content

Channel

Target Direct Vendor Ship

Plan a reliable EDI exchange for Target Direct Vendor Ship. Explore 8 document references, map them to your business records and test the complete workflow before launch.

Documents
8 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

Target Direct Vendor Ship: EDI implementation plan

Build a reliable EDI workflow for Target Direct Vendor Ship. Use 8 document types 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 860 Purchase Order Change Request Buyer InitiatedListed for Target Direct Vendor Ship buyer order-change request

original purchase order, change revision and affected line

  • Apply a quantity reduction to the existing order instead of creating another order.
  • Test a cancellation arriving after allocation or shipment and route it to an exception owner.
X12 214 Transportation Carrier Shipment Status MessageListed for Target Direct Vendor Ship shipment status event

shipment reference, event code, event time and location

  • Deliver an older status after a newer one and retain event history without moving the current status backward.
  • Send one milestone twice and avoid duplicate customer notifications.
X12 850 Purchase OrderListed for Target Direct Vendor Ship purchase order or sales order

buyer purchase order, order line and trading-party identifiers

  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.
X12 864 Text MessageListed for Target Direct Vendor Ship business message

message reference, subject and related business document

  • Preserve line breaks and readable content in the receiving work queue.
  • Test an urgent message linked to an order and assign a human owner instead of silently filing it.
X12 856 Ship Notice ManifestListed for Target Direct Vendor Ship shipment notice (ASN)

shipment, order, package and item references

  • Reconcile item quantities through shipment, order and packaging levels against the physical shipment.
  • Test split shipments for one purchase order and prevent the second ASN from replacing the first.
X12 855 Purchase Order AcknowledgmentListed for Target Direct Vendor Ship purchase-order response

original purchase order, response revision and order line

  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 846 Inventory Inquiry AdviceListed for Target Direct Vendor Ship inventory availability record

item, location, quantity type and snapshot time

  • Distinguish on-hand, available and reserved quantities before publishing availability.
  • Deliver an old snapshot after a new one and prevent stale stock from replacing current values.
X12 865 Purchase Order Change Acknowledgment Request Seller InitiatedListed for Target Direct Vendor Ship seller order-change response or request

original purchase order, change reference and affected line

  • Distinguish a seller-proposed change from acceptance of a buyer-requested change.
  • Reject an outdated revision that would overwrite a later agreed quantity.

Implementation steps

  1. Choose the trading account and channel

    Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Target Direct Vendor Ship. Compare other Target channels before reusing a mapping.

  2. Map records and assign owners

    Start with buyer order-change request, shipment status event, purchase order or sales 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 Target production handoff and save the results of each approved test.

  4. Check results after launch

    Match records between systems using original purchase order, change revision and affected 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 on this channel

Document relationships on Target Direct Vendor Ship

This channel lists 8 of the 14Target document types; other entries appear on Target channels (listed below). Example relationships are shown below; confirm the required sequence in the channel guide.

Logistics

Some example steps listed
  1. 204 Motor Carrier Load Tender not listed on Target Direct Vendor Ship
  2. 990 Response to a Load Tender not listed on Target Direct Vendor Ship
  3. 214 Transportation Carrier Shipment Status Message
  4. 210 Motor Carrier Freight Details and Invoice not listed on Target Direct Vendor Ship

Catalog & inventory

Some example steps listed
  1. 832 Price / Sales Catalog not listed on Target Direct Vendor Ship
  2. 846 Inventory Inquiry Advice
  3. 852 Product Activity Data not listed on Target Direct Vendor Ship

Target Direct Vendor Ship questions

Which EDI documents are listed for Target Direct Vendor Ship?

X12 860 Purchase Order Change Request Buyer Initiated; X12 214 Transportation Carrier Shipment Status Message; X12 850 Purchase Order; X12 864 Text Message; X12 856 Ship Notice Manifest; X12 855 Purchase Order Acknowledgment; X12 846 Inventory Inquiry Advice; additional documents are shown in the mapping plan. Confirm which documents, directions and versions apply to your account.

How should I choose the Target EDI channel?

Target Direct Vendor Ship lists 8 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.

Which identifiers should the Target mapping preserve?

For X12 860 Purchase Order Change Request Buyer Initiated, plan around original purchase order, change revision and affected line. For X12 214 Transportation Carrier Shipment Status Message, use shipment reference, event code, event time and location. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean Target 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 Target Direct Vendor Ship EDI?

Apply a quantity reduction to the existing order instead of creating another order. Test a cancellation arriving after allocation or shipment and route it to an exception owner. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Related references

Other Target channels

Compare the document lists for other Target channels.

Connect Target EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.