| Status | ||||
|---|---|---|---|---|
|
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)
| View file | ||||
|---|---|---|---|---|
|
📄 Example 2 — UBL ProductActivity (Inventory Report)
| View file | ||||
|---|---|---|---|---|
|
Onetrail enables automated, standardized exchange of Sell-out, Sell-to and Inventory data between channel partners and manufacturers.
Supported Report Types
- Sell-out Report
- Sell-to Report
- Inventory Report
Key Capabilities
- Normalization of diverse partner formats into a unified structure
- Product code translation
- Automated validation and data quality checks
- Multi‑manufacturer ingestion support
Fields – Sell-out Report
| Normalized Field | Notes |
|---|---|
| productIdentifier | Standardized product code |
| quantitySold | Actual sell-out quantity |
| salesDate | ISO‑8601 format |
| customerIdentifier | End‑customer or POS |
| shipToLocation | Normalized location |
| currency | Optional |
| unitPrice | Optional |
Fields – Sell-to Report
| Normalized Field | Notes |
|---|---|
| productIdentifier | product code |
| quantitySoldToChannel | Channel sales |
| shipToPartner | Channel partner identifier |
| shipDate | ISO‑8601 format |
| orderReference | Optional |
Fields – Inventory Report
| Normalized Field | Notes |
|---|---|
| productIdentifier | product code |
| openingStock | Start‑of‑period stock |
| currentStockLevel | Live stock balance |
| damagedStock | Optional |
| qualityControlledStock | Optional |
| goodsReceived | Inbound movements |
| goodsShipped | Outbound movements |
| inventoryDateTime | Snapshot timestamp |
Data Quality & Validation
- Product code consistency
- Complete and valid dates
- Non‑negative numerical quantities
- Required fields depending on the report type
Benefits
...
