To start and identify an interchange of zero or more functional groups and interchange-related control segments
Nebraska Furniture Mart (NFM) X12 852 Product Activity Data
X12 852 (Product Activity Data) is the EDI transaction exchanged between Nebraska Furniture Mart (NFM) (Nebraska Furniture Mart (via Blue Yonder)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 11
- Loops
- 3
- X12 852
- All partners ↗
Transaction context
Where 852 Product Activity Data fits on Nebraska Furniture Mart (via Blue Yonder)
On Nebraska Furniture Mart (via Blue Yonder), the X12 852 Product Activity Data follows the 846 Inventory Inquiry Advice in the Catalog & inventory cycle.
- Nebraska Furniture Mart (NFM) channels
- 1 of 1
- Trading partners
- 33
- Channels
- 38
1 of Nebraska Furniture Mart (NFM)'s 1 channel carries 852
partners across the Stacksync network trade 852
channels network-wide carry 852
Most common alongside 852
On Blue Yonder, 852 runs on 1 channel.
The 852 carries product movement data by item and location: quantity sold (QS), quantity on hand (QA), quantity returned (QU), and related adjustment figures. Suppliers use it for demand forecasting, replenishment planning, and vendor-managed inventory programs, since it gives them sell-through visibility without direct access to the retailer's POS systems. Trading partners require it because retail allocation and production planning depend on knowing what actually moved at store or DC level. Sent by a retailer or distributor to its supplier, typically as a recurring feed of store-level or distribution-center-level activity.
When it fires: The close of a retailer's sales reporting period, commonly a Saturday-ending week with transmission between Sunday and Tuesday, though daily and monthly cadences also occur.
Common 852 rejection causes
- Some partners report on-hand quantities only for items with sales that week, so zero-sale items drop out of the feed and skew inventory figures.
- Discontinued or obsolete items continuing to appear in the feed, polluting forecasts.
- Inconsistent department codes, field usage, and multi-location consolidation across trading partners, so each retailer's 852 needs its own mapping.
- Missing or inaccurate vendor IDs and SKU data, plus duplicate entries, that break reconciliation against the supplier's item master.
Specification summary
X12 852 Product Activity Data at the element level
The X12 852 specification defines 24 segments carrying 100 data elements, 46 of which are mandatory.
- 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 |
Key identifiers in 852
- Transaction Handling Code
- Date
- Purchase Order Number
- Reference Identification Qualifier
- Contact Function Code
- Entity Identifier Code
- Name
- Address Information
Full segment guideline — 11 segments 3 loops · X12 852 Product Activity Data
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To specify reporting date and action to be taken
N1 Loop Repeat: 200
To identify a party by type of organization, name, and code
LIN Loop Repeat: 999,999
To specify basic item identification data
To transmit identifying information as specified by the Reference Identification Qualifier
ZA Loop
To provide activity details concerning product being reported
To specify destination and quantity detail
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Trading partners
6+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
PU Purchase Order PU Purchase Order Change Request Buyer Initiated PU Purchase Order Acknowledgment SH Ship Notice Manifest IN Invoice IN Inventory Inquiry Advice
No trading partner matches your search.
Browse the full directory
Nebraska Furniture Mart (NFM) Nebraska Furniture Mart (via Blue Yonder) EDI 852 FAQ
Common questions about 852 Product Activity Data on the Nebraska Furniture Mart (via Blue Yonder) channel.
What is X12 852 Product Activity Data?
X12 852 (Product Activity Data) is the EDI transaction set used to exchange product activity data data. Nebraska Furniture Mart (NFM)'s Nebraska Furniture Mart (via Blue Yonder) channel requires it from trading partners.
Does Nebraska Furniture Mart (NFM) Nebraska Furniture Mart (via Blue Yonder) require 852 for trading partners?
Yes, Nebraska Furniture Mart (NFM) (Nebraska Furniture Mart (via Blue Yonder)) supports X12 852 Product Activity Data. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Nebraska Furniture Mart (NFM) 852 with Stacksync?
Most companies go live with Nebraska Furniture Mart (NFM) 852 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 852 on Nebraska Furniture Mart (via Blue Yonder)?
On Nebraska Furniture Mart (via Blue Yonder), X12 852 is typically exchanged alongside 810 Invoice, 850 Purchase Order, 856 Ship Notice Manifest, 855 Purchase Order Acknowledgment. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Nebraska Furniture Mart (NFM) EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
