EDIFACT SLSRPT — Sales Report
SLSRPT delivers sales movement by item, location, and period so suppliers align production and promotions to actual demand.
✦ What It Does
QTY segments distinguish sell-in, sell-out, returns, and sometimes lost sales codes per retailer MIG.
High-frequency SLSRPT underpins CPFR-style collaboration between retailer and brand.
Data quality (calendar alignment, store openings) is a common integration pain point.
⚡ When It's Used
- Weekly closed-period POS feed to suppliers.
- Promotion post-mortem analysis by SKU.
- Allocation programs for constrained supply.
- New item sell-through tracking first weeks.
- E-commerce channel sales split for omnichannel brands.
Who Uses EDIFACT SLSRPT
European retail & brands
Common in EDIFACT-first programs where sales report flows between HQ, DCs, and suppliers across the EU and APAC.
Global manufacturers
Automotive, industrial, and CPG companies standardize on EDIFACT for plants and suppliers outside North America.
3PLs & carriers
Logistics service providers consume or produce the message when the contract mandates UN/EDIFACT syntax and directories.
Key Segments & Constructs
EDIFACT uses a hierarchical structure: UNH (message header) opens the transaction; BGM (beginning of message) carries the document name and reference; party data uses NAD; lines often use LIN with QTY, PRI, and MOA. Exact segment requirements depend on the message directory (D.96A, etc.) and your trading partner's implementation guide.
BGM
Report type and reporting period.
NAD
Reporting party (retailer) and hierarchy context.
LIN / QTY
Product and sales quantities by bucket.
MOA
Sales value when monetary movement is included.
Related Messages
Need Help with EDIFACT SLSRPT?
Better EDI maps, tests, and operates EDIFACT alongside X12—same platform, translation when partners use different standards.
Talk to an EDI Expert