Skip to content

X12 transaction code

X12 852 Product Activity Data

X12 852 Product Activity Data: explore its business purpose, mapping identifiers, validation tests and 33 partner references across 38 listed channels.

Standard
X12
Code
852
Partner references
33

Implementation guide

X12 852 mapping and validation

X12 852 Product Activity Data is used when product sales or inventory activity is reported. Preserve item, location, activity type and reporting period so the product activity report in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record product activity report

item, location, activity type and reporting period

  • Define which combination of item, location, activity type and reporting period identifies one business record, its lines and any later revision.
Update the receiving system Processing the product activity report

ID assigned by the receiving system and processing result

  • Keep sales, returns and stock movements in separate measures.
  • Replace a corrected reporting period without counting the original activity twice.
Check the processing result Processing status for the product activity report

Original document reference and matching response

  • Reconcile the product activity report with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when product sales or inventory activity is reported. Name the operational owner of the product activity report and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map item, location, activity type and reporting period. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic product activity report data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful product activity report processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 852 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic product activity report data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out product activity report without processing it twice.

Document structure

X12 852 Product Activity Data at the element level

The X12 852 reference contains 24 segment entries and 100 data elements; 46 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
24
Data elements
100
Mandatory elements
46
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
XQ 3 2
XPO 4 1
N9 2 1
PER 4 1
N1 4 1
N2 2 1
N3 2 1
FOB 1 1
DTM 2 1
LIN 9 2
AMT 2 2
ZA 3 1
Key identifiers in 852
  • Transaction Handling Code
  • Date
  • Purchase Order Number
  • Reference Identification Qualifier
  • Contact Function Code
  • Entity Identifier Code
  • Name
  • Address Information

Find your trading partner for X12 852

33 partners, 38 channels. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where X12 852 Product Activity Data appears in this catalog

The largest groups of classified 852 catalog entries are in retail, grocery & food and apparel & footwear.

By industry

  • retail 13 channels
  • grocery & food 7 channels
  • apparel & footwear 6 channels
  • consumer goods 4 channels
  • healthcare & pharma 4 channels
  • building & hardware 2 channels

By network

  • SPS Commerce 4 channels
  • Epicor Eclipse 1 channel
  • 1EDISource 1 channel
  • Blue Yonder 1 channel
  • OpenText 1 channel

FAQ

X12 852 questions

What is X12 852 Product Activity Data used for?

852 is used when product sales or inventory activity is reported. It carries information for the product activity report. Match it to your business system using item, location, activity type and reporting period.

Which partners list X12 852?

The directory on this page links 33 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for X12 852?

Start with item, location, activity type and reporting period and the target product activity report. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 852 error handling?

Keep sales, returns and stock movements in separate measures. Replace a corrected reporting period without counting the original activity twice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 852 relate to other EDI messages?

X12 846 Inventory Inquiry Advice; X12 832 Price Sales Catalog are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 852 and 846?

852 is used when product sales or inventory activity is reported. 846 is used when stock availability is reported or requested. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

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