The Sales Template feature in RASA provides users with a way to ingest sales report data that may not have been successfully imported through automated file mappings. This knowledge base article aims to explain how the Sales Template works within our application, providing guidelines and requirements for each field.
Please note that the system expects the data to be in UTF-8 format. There is also a general limit of 255 characters per field and numerical values are accepted as smart decimals, which accept ‘.' or ',’ as separators.
- Platform Name and Service Name: In the first row of the sales template, you are required to insert the name of the digital streaming platform next to the box service name. This allows for accurate identification and categorization of sales data. This is a mandatory field and cannot be left blank.
- Start Date: Always provide the date in the format of the day, then month, and optionally, the year can be placed at the beginning or the end (YY-)D-M(-YYYY)—for example, 5-12-2023 or 5-12-23.
- End Date: Always provide the date in the format of the day, then month, and optionally, the year can be placed at the beginning or the end (YY-)D-M(-YYYY)—for example, 5-12-2023 or 5-12-23.
Country: The country field should be stored as plain text. While the system is quite liberal in accepting values, it validates them using a country lookup mechanism. It attempts to match two-letter codes (such as 'IE' for Ireland or 'UK' for the United Kingdom) based on the ISO-3166 Alpha 2 standard.
- Continents/regions are sometimes provided (EMEA etc.), don’t block revenue being ingested, but should be updated if territory-specific terms need to be applied.
- EAN (shown as UPC): The EAN (European Article Number) is displayed as the UPC (Universal Product Code) in the sales template. The EAN/UPC is limited to 12 or 13 characters. If the original EAN is shorter than 12 or 13 characters, zeros can be added at the beginning to meet the required length.
- ISRC (International Standard Recording Code): The ISRC field is used to uniquely identify sound recordings. It should be limited to 12 characters. Please ensure that the provided ISRCs are correct, as incorrect or invalid codes may cause issues.
- Song/Asset Title: The Song Title field has no specific limitations. You can input the title of the song without any restrictions.
- Net PPD: Not imported.
- Total Net PPD: Net Publisher Price to Dealer is the price per album for those that buy in bulk.
- Gross PPD: Gross Publisher Price to Dealer is the price per album for those who buy in bulk.
- Total Gross PPD: Not imported.
- Gross Royalty: Not imported.
- Net Revenue: The total end revenue made.
- Consumer Price: The total paid by the end consumer.
- Total Consumer Price: Not imported.
- Net Royalty: The total royalty to be paid out.
- Currency: The Currency field specifies the currency used for all monetary values in the sales template. It follows the ISO-4217 Alpha3 standard for currency codes (e.g., USD for United States Dollar, EUR for Euro).
- Quantity: This must be an integer. If the value is null, the system will impose the number 1 in its place.
- Sale Type: The system tries to find sale types stored in the database and if not, uses the value ‘Other’.
- User Type: This field denotes the type of user listening to the music. They could be a premium subscriber for example. If this field is empty or the value is incorrect the system will store it as nil, i.e. empty.
- Artist: Stored as the artist’s name in plain text.
- Release Name: Stored as the product title in plain text.
- Store Name: Stored as the store name in plain text.
- Device: The system attempts to transform the value into a stored device type, if it is not successful it stores it as nil, i.e. empty.
- Label: Stored as the label name in plain text.
- DSP Asset: Stored as the Digital Streaming Platform Asset Identifier in plain text.
- DSP Product: Stored as the Digital Streaming Platform Product Identifier in plain text.
- DSP Vendor: Stored as the Digital Streaming Platform Vendor Identifier in plain text.
The Sales Template in RASA allows users to manually ingest sales report data that may not have been successfully imported through automated sale report mappings. By following the guidelines for each field, you can ensure accurate and organized data entry within the template. Please consult our support team for assistance if you encounter any issues or have further questions.