X12 transaction code
EDI 852 Product Activity Data (X12 852)
EDI 852 is the X12 Product Activity Data transaction set, used when product sales or inventory activity is reported. A retailer or distributor sends the 852 to its supplier, typically as a recurring feed of store-level or distribution-center-level activity.
- Standard
- X12
- Code
- 852
- Partner references
- 33
At a glance
EDI 852 at a glance
What the 852 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 852 Product Activity Data |
|---|---|
| Business record | Product activity report |
| Who sends it to whom | A retailer or distributor sends the 852 to its supplier, typically as a recurring feed of store-level or distribution-center-level activity. |
| When it is sent | A retailer's sales reporting period closes, commonly a Saturday-ending week with transmission between Sunday and Tuesday, though daily and monthly cadences also occur. |
| Match on | Item, location, activity type and reporting period |
| Partner references | 33 trading partners in this directory |
| Related documents | X12 846 Inventory Inquiry/Advice, X12 832 Price/Sales Catalog |
Key segments in an EDI 852
The business segments that appear in at least half of the 38 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| XQ | Reporting Date/Action | To specify reporting dates, actions to be taken and an identifying number. | 38 of 38 |
| LIN | Item Identification | To specify basic item identification data. | 38 of 38 |
| ZA | Product Activity Reporting | To provide activity details concerning product being reported. | 38 of 38 |
| CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 34 of 38 |
| N9 | Extended Reference Information | To transmit identifying information as specified by the Reference Identification Qualifier. | 29 of 38 |
| SDQ | Destination Quantity | To specify destination and quantity detail. | 26 of 38 |
| N1 | Name | To identify a party by type of organization, name, and code. | 19 of 38 |
Stacksync connects EDI documents such as the X12 852 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
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.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | product activity report item, location, activity type and reporting period |
|
| Update the receiving system | Processing the product activity report ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the product activity report Original document reference and matching response |
|
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.
- X12 846 Inventory Inquiry/Advice
inventory availability record: stock availability is reported or requested.
- X12 832 Price/Sales Catalog
product and price catalog: catalog entries or commercial details are published.
Implementation steps
-
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.
-
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.
-
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.
-
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
| 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 |
- 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.
- Academy Sports + Outdoors
- BioCare, Inc.
- Bloomingdale's
- Bluemercury, Inc.
- Boscov's Department Stores
- Burlington Coat Factory
- Cardinal Health, Inc.
- Cencora (ASD Health Care) (formerly AmerisourceBergen)
- Core-Mark (via SPS Commerce)
- CuraScript SD
- DUNHAM'S SPORTS
- Fred Meyer Group
- Granite City Electric
- Holt, Renfrew & Co., Limited
- JCPenney
- Kroger Modernized Systems
- Macy's
- McLane Company, Inc.
- Nebraska Furniture Mart (NFM)
- NEXCOM (Navy Exchange Service Command)
- Nordstrom
- PetSmart
- Quaker Oats Company (A Pepsico Company)
- Saks Fifth Avenue & Saks OFF 5th
- Sazerac Company
- Sephora
- Sportsman's Warehouse
- Stater Bros. Markets
- Superior Communications
- Target
- The Home Depot
- Ulta Beauty
- Von Maur
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
EDI 852 questions
What is an EDI 852?
EDI 852 is the X12 Product Activity Data transaction set. Trading partners use it when product sales or inventory activity is reported. It carries the data for the product activity report, and your system matches it on item, location, activity type and reporting period.
Who sends an EDI 852 and who receives it?
A retailer or distributor sends the 852 to its supplier, typically as a recurring feed of store-level or distribution-center-level activity. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 852 sent?
A retailer's sales reporting period closes, commonly a Saturday-ending week with transmission between Sunday and Tuesday, though daily and monthly cadences also occur. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 852?
Across 38 partner document references listed here, the business segments that appear most often include XQ (Reporting Date/Action), LIN (Item Identification), ZA (Product Activity Reporting), CTT (Transaction Totals), N9 (Extended Reference Information), SDQ (Destination Quantity). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 852 and EDI 846?
The 852 carries the product activity report and is used when product sales or inventory activity is reported. The 846 carries the inventory availability record and is used when stock availability is reported or requested.
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.
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.
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.
