Using the UBL ProductActivity Message for Sales and Inventory Reporting

We use the OASIS UBL ProductActivity message as the standardized document format for exchanging both Sales Reporting (SLSRPT) and Inventory Reporting (INVRPT).
The ProductActivity document provides a flexible and internationally recognized structure for describing product‑related activities across the supply chain.

More details on the document can be found here: UBL ProductActivity

Why ProductActivity?

The UBL ProductActivity message contains components that naturally fit the information required for sales and inventory processes. It allows us to represent:

• Sales reporting data, such as quantities sold, reporting periods, and product identifiers.
• Inventory reporting data, including stock levels, receipts, withdrawals, adjustments, and availability.

How the UBL Structure Is Used

The ProductActivity message includes the following relevant elements:

• ActivityDataLine – captures reporting periods, product quantities, and activity type
• SupplyChainActivityTypeCode – specifies the nature of the activity (e.g., SALES, INVENTORY)
• Item / ItemIdentification – supports standardized product codes such as EAN, SKU, or manufacturer part numbers

Using these components, we can map all required fields for both Sales and Inventory Reporting into a single consistent UBL structure.

Benefits of Using UBL ProductActivity

• Standards‑based: ensures compatibility with global supply‑chain systems
• Flexible and extensible: supports a wide range of reporting scenarios
• Interoperable: simplifies integration with partners, suppliers, and customer platforms
• Future‑proof: aligns with OASIS UBL and related schema updates

By adopting the UBL ProductActivity document, we ensure that our reporting processes are structured, interoperable, and aligned with international best practices.

Examples

📄Example 1 — UBL ProductActivity (Sales Report)

📄 Example 2 — UBL ProductActivity (Inventory Report)