Skip to content
EDI NEXCOM (Navy Exchange Service Command) NEXCOM Trans 852
X12 EDI

NEXCOM (Navy Exchange Service Command) X12 852 Product Activity Data

X12 852 (Product Activity Data) is the EDI transaction exchanged between NEXCOM (Navy Exchange Service Command) (NEXCOM Trans) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
11
Loops
2
X12 852
All partners ↗
Book a demo ← All NEXCOM Trans transactions

Transaction context

Where 852 Product Activity Data fits on NEXCOM Trans

On NEXCOM Trans, the X12 852 Product Activity Data follows the 846 Inventory Inquiry Advice in the Catalog & inventory cycle.

NEXCOM (Navy Exchange Service Command) channels
1 of 1

1 of NEXCOM (Navy Exchange Service Command)'s 1 channel carries 852

Trading partners
33

partners across the Stacksync network trade 852

Channels
38

channels network-wide carry 852

Most common alongside 852

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
Segments with mandatory elements
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 2 loops · X12 852 Product Activity Data
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

XQ Reporting Date/Action 3 elements

To specify reporting date and action to be taken

N9 Reference Identification 2 elements

To transmit identifying information as specified by the Reference Identification Qualifier

LIN Loop Repeat: 999,999
LIN Item Identification 4 elements

To specify basic item identification data

CTP Pricing Information 2 elements

To specify pricing information

ZA Loop
ZA Product Activity Reporting 1 element

To provide activity details concerning product being reported

SDQ Destination Quantity 22 elements

To specify destination and quantity detail

CTT Transaction Totals 1 element

To transmit a hash total for a specific element in the transaction set

SE Transaction Set Trailer 2 elements

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

10+ 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.

Browse the full directory

NEXCOM (Navy Exchange Service Command) NEXCOM Trans EDI 852 FAQ

Common questions about 852 Product Activity Data on the NEXCOM Trans 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. NEXCOM (Navy Exchange Service Command)'s NEXCOM Trans channel requires it from trading partners.
Does NEXCOM (Navy Exchange Service Command) NEXCOM Trans require 852 for trading partners?
Yes, NEXCOM (Navy Exchange Service Command) (NEXCOM Trans) supports X12 852 Product Activity Data. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate NEXCOM (Navy Exchange Service Command) 852 with Stacksync?
Most companies go live with NEXCOM (Navy Exchange Service Command) 852 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 852 on NEXCOM Trans?
On NEXCOM Trans, 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 NEXCOM (Navy Exchange Service Command) EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a NEXCOM (Navy Exchange Service Command) EDI demo Tour the platform on your own