If your brand sells through retailers such as Ulta Beauty, Walmart, Target, CVS, or Costco, you’re likely receiving EDI 852 product activity data on a regular schedule. The 852 is the retail industry’s standard mechanism for sharing point-of-sale and inventory data with suppliers. It tells you what’s sold, what’s still on shelves, and what’s running low, at the store-level.
The challenge most brands face isn’t receiving the data. It’s that EDI 852 integration with NetSuite is rarely set up in a way that makes the data usable.
This article explains what EDI 852 product activity data actually contains, how it fits into the broader EDI ecosystem, where manual processes break down, and how a properly architected Celigo-to-NetSuite integration changes what your team can do with it.
What Is EDI 852 Product Activity Data?
EDI 852, also called a product activity report, is a transaction set in the ANSI ASC X12 standard used by retailers to report product sales activity to suppliers.
The file typically contains:
- units sold during the reporting period
- current inventory levels at retail stores
- out of stock quantities
- items currently on order
- consumer returns
Unlike many other EDI transactions that are triggered by a specific business event (an EDI 850 purchase order, an EDI 856 advance ship notice, an EDI 810 invoice), the 852 follows a recurring schedule. It’s not triggered by something your brand does. It arrives because the retailer committed to sending it, on their timeline, covering whatever activity occurred in the prior period.
The data flows in one direction. The retailer generates the report and sends it to the supplier. For brands, this document provides direct visibility into retail demand and is a key input for demand planning and replenishment decisions.
When Do Retailers Send EDI 852 Product Activity Data?
Most retailers transmit 852 data weekly.
The report typically covers the previous week’s activity by showing week ID (Fiscal year & week – YYYYWW) and is delivered through an EDI connection such as a VAN or AS2.
A typical schedule includes:
- reporting period covering the prior week
- transmission between Sunday and Tuesday
- delivery through a trading partner network
During peak retail seasons some retailers increase reporting frequency and send the 852 daily.
What Information Does an EDI 852 File Contain?
An 852 file includes activity metrics tied to specific products and store locations.
The core of an EDI 852 is a set of quantity codes in the ZA segment (the X12 segment carrying per-SKU quantity data), each tagged to a specific activity type. Here are the codes that matter most to a brand’s operations team:
- ZA Segment – Product activity data segment. Contains quantity activity codes
- QS – Quantity sold – Units sold to consumers
- QA – Quantity available – Current inventory available
- QO – Quantity out of stock – Indicates stockouts
- QP – Quantity on order – Inventory ordered but not received
- QR – Quantity returned – Consumer returns
- SDQ Segment – Store detail quantity. Associates activity values with stores
These codes allow retailers to report activity across thousands of store and SKU combinations at once. A Target transmission might show 72 units sold at store 0551, 48 at store 0552, and 12 at store 0553, all for the same item, all in the same week.
That granularity is what makes the 852 valuable for regional assortment decisions, promotional analysis, and Vendor Managed Inventory (VMI) programs. It’s also what makes manual processing unsustainable as a brand adds more retail partners.
Why EDI 852 Data Is Hard to Operationalize Without NetSuite Integration
Receiving EDI 852 files does not mean the data is operational
The failure point is downstream: the data is received but not integrated, so it never reaches the systems or people who could act on it.
The file arrives in a VAN (Value-Added Network) mailbox, someone exports a flat file, it gets manually pieced into a spreadsheet, and by the time it reaches the people who need it (your demand planner, your sales rep, your CFO), it’s already a week old. That cycle doesn’t scale, and the cost of staying with it compounds quietly over time.
This process introduces several problems:
- delays in accessing retail performance data
- manual data processing errors
- limited visibility outside the EDI team
By the time sales or planning teams review the report, the information is already outdated. The 852 data isn’t reaching the people and systems that need it, at least not in a way they can act on within a useful timeframe.
How EDI 852 Fits Into the Retail EDI Ecosystem
EDI 852 is one of several EDI transactions used in retail supply chains.
- EDI 850 (Purchase Order): Retailer sends a PO to the supplier. This is a transactional trigger.
- EDI 856 (Advance Ship Notice): Supplier notifies the retailer of an incoming shipment.
- EDI 810 (Invoice): Supplier bills the retailer for goods shipped.
- EDI 846 (Inventory Inquiry/Advice): A point-in-time inventory snapshot. Narrower than the 852, focused only on current stock.
- EDI 852 (Product Activity Data): The recurring sell-through and inventory report. Covers sales velocity, on-hand stock, out-of-stock events, and returns over a defined period.
The 852 is what makes proactive replenishment possible. Suppliers who only see purchase orders are always reacting. The 852 puts actual consumer demand data in their hands before the next order cycle starts.
For a broader overview of how EDI works across the supply chain, including transaction types, VANs, and standards, see What Is EDI? on the Hairball blog.
Ulta EDI 852 Product Activity Data
Ulta Beauty uses Electronic Data Interchange to exchange operational documents with its suppliers. One of the documents Ulta sends regularly is EDI 852 Product Activity Data, which reports how products are performing across Ulta stores.
For suppliers, the Ulta EDI 852 report provides visibility into the same activity codes covered above (units sold, inventory, stockouts, and on-order quantities).
Ulta typically sends this information weekly through its EDI network. When this data is synced into NetSuite, teams gain visibility into store-level sell-through and inventory conditions across Ulta locations
Below is an example of how Ulta EDI 852 product activity data appears once it is integrated into NetSuite using Celigo.
This eliminates the need to manually export and process EDI files.
Ulta EDI 852 Product Activity Data
NetSuite does not include native EDI functionality. Companies typically use an integration platform such as Celigo B2B Manager.
852 data flows into NetSuite through an integration layer between your trading partner network and your ERP. Celigo’s B2B Manager picks up the raw X12 file from your VAN or AS2 endpoint, translates it into structured data, applies retailer-specific mapping rules, and writes normalized records directly into NetSuite without manual intervention.
The process typically works as follows:
1. The retailer sends the EDI 852 file
The trading partner’s POS and inventory systems generate the product activity data and transmit the X12-formatted file via AS2 (a direct secure protocol for EDI document exchange) or through a VAN. This transmission happens on the retailer’s schedule, typically weekly.
2. Celigo receives and parses the file
Celigo’s B2B Manager picks up the raw X12 file from the VAN or AS2 endpoint and translates it from the standard X12 format into structured data. It handles the retailer-specific variations in field usage, vendor codes, and segment structure automatically.
3. Celigo maps retailer fields to your NetSuite data model
This is where retailer-specific differences are resolved. Walmart’s vendor numbering doesn’t match Ulta’s. Target’s department codes don’t match Kroger’s. Celigo uses prebuilt connectors for major trading partners and resolves approximately 95% of exceptions automatically, with no hands-on work from your team.
4. NetSuite receives clean, structured product activity records
The mapped data lands in NetSuite as structured records your team can actually query. Sell-through by SKU, by store, by week. Inventory levels by location. Out-of-stock flags that can trigger automated workflows.
5. Your team accesses retail performance data directly in the ERP
Demand planners use sell-through data as a forecasting input. Sales teams pull retail performance reports before quarterly business reviews. Finance tracks revenue at the retail level, not just the shipment level. Operations monitors inventory with alerts that fire before chargebacks accumulate.
What Changes When the Data Lives in NetSuite
The most significant change is organizational. EDI 852 data isolated in a VAN or middleware tool that only an EDI analyst can access is effectively invisible to the rest of the business. Sales can’t pull it. Finance can’t query it. Demand planning can’t use it. Bringing it into NetSuite changes that, because the data is now in a system every function already uses.
One of the most practical applications is NetSuite’s saved search functionality. A saved search is a pre-configured query that runs against your 852 records in NetSuite and delivers a formatted report automatically.
For a brand selling through Ulta, that means your sales team receives a weekly Ulta sell-through report: units sold by SKU, on-hand inventory by store, and out-of-stock flags, delivered on a schedule without anyone logging into a system to pull it manually. The same mechanism works for any retail partner whose 852 data is integrated.
Other Retailers That Send EDI 852 Product Activity Data
The EDI 852 transaction is widely used across retail. Major retailers that send product activity data include:
- Walmart
- Target
- CVS
- Costco
- Kroger
- Walgreens
Each retailer publishes its own EDI implementation guide defining how the transaction is structured.
Integration platforms such as Celigo normalize these differences so the data can be stored consistently in NetSuite. For a full breakdown of what Celigo EDI integration covers for NetSuite users, see Celigo EDI NetSuite Integrations.
Quick Summary: EDI 852 and NetSuite Integration
- EDI 852 is a retail sell-through report sent by retailers to suppliers on a weekly schedule.
- Each file covers units sold, on-hand inventory, out-of-stock quantities, and returns, broken down by SKU and store location.
- Without a direct path into NetSuite, 852 data stays locked in a VAN mailbox where no one outside the EDI team can reach it.
- Integrating it with NetSuite enables automated demand planning, out-of-stock alerts, and real-time retail performance reporting.
- Celigo B2B Manager translates raw X12 files and syncs normalized product activity records into NetSuite automatically.
What Hairball Builds: EDI 852 Integration, Reporting, and Monitoring in NetSuite
Hairball builds EDI 852-to-NetSuite integrations for mid-market product brands via Celigo, including the saved search reporting layer that puts Ulta, Walmart, Target, and Costco sell-through data in front of your sales team automatically. If you’re manually processing 852 files or onboarding a major retail account, schedule a call with Hairball. We’ll tell you exactly what the integration looks like and what it will take to get live.
Frequently Asked Questions
What is EDI 852 product activity data?
A standard retail transaction (ANSI X12) that reports units sold, on-hand inventory, stockouts, and returns by SKU and store location. Retailers send it to suppliers on a recurring schedule, typically weekly.
Which retailers send EDI 852 data to suppliers?
Most major retailers, including Walmart, Target, Ulta Beauty, Costco, CVS, and Kroger. Each publishes an EDI implementation guide defining their specific format and transmission schedule.
How often does Ulta send EDI 852 reports?
Ulta typically sends product activity data weekly through its EDI network.
Does NetSuite support EDI natively?
No. Brands use a third-party integration platform like Celigo B2B Manager, which includes prebuilt NetSuite connectors and automated exception handling.
How does Celigo connect EDI 852 data to NetSuite?
Celigo picks up the raw X12 file from your VAN or AS2 endpoint, translates it into structured data, applies retailer-specific mapping rules, and writes normalized records into NetSuite automatically.
When should a growing brand invest in EDI 852 automation?
Before the manual process breaks. Typically when you have three or more active retail partners or you’re onboarding a major account where chargeback exposure starts affecting margin.
How long does it take to implement EDI 852 product activity data?
Most implementations take about one week.
