Skip to content

System Configurations

Overview

This page allows administrators to manage critical platform-wide settings. These include financial parameters like commission rates and transfer fees, the designated Wise account for platform payouts, public-facing announcements for various services, predefined reasons for content moderation, and mappings for importing external distribution reports.

The configuration is typically divided into logical sections for clarity and ease of management.

Commission and Financial Settings

These settings directly impact how revenue is shared and how financial transactions are processed.

  1. YouTube MCN Third Party Commission (mcn_outside_commission)

    • Purpose: Defines the percentage of revenue Distromotion retains from content managed through third-party Multi-Channel Networks (MCNs) on behalf of users.
    • Input: Enter a numerical value (e.g., 5 for 5%). This is stored internally as a decimal (e.g., 0.05).
    • Impact: Affects earnings calculations for users utilizing MCN services via external partners.
  2. Transfer Fees Commission (transfer_fees)

    • Purpose: Sets the percentage Distromotion earns from any fees charged to users for processing payouts or other transfers.
    • Input: Enter a numerical value (e.g., 3 for 3%). Stored internally as a decimal.
    • Impact: Determines the platform’s revenue share from transaction-related charges.
  3. Flat Transfer Fees (falt_transfer_fee)

    • Purpose: Specifies a fixed amount charged per user payout or transfer, in addition to any percentage-based fees.
    • Input: Enter a numerical value (e.g., 1 for a 1 EUR flat fee).
    • Impact: Adds a standard cost to user transactions.
  4. Minimum Payout Balance (minimum_payout_balance)

    • Purpose: Establishes the minimum accumulated earnings a user must have before they can request a payout.
    • Input: Enter a numerical value (e.g., 2 for 2 EUR).
    • Impact: Controls payout eligibility and frequency.
  5. Wise Admin Account ID (wise_admin_account)

    • Purpose: Designates the specific Wise business account owned by Distromotion that will be used to send payouts to users.
    • Selection: This is typically chosen from a dropdown list of Distromotion’s available Wise accounts, fetched via the Wise API.
    • Impact: Ensures payouts are disbursed from the correct platform account.

Announcements

This section allows administrators to display custom messages or important information to users within specific areas of the platform.

  1. Music Distribution Announcement

    • Purpose: Display a message on pages related to music distribution services.
    • Action: Enter the announcement text. To remove an existing announcement, clear the text field.
  2. YouTube MCN Announcement

    • Purpose: Show an announcement within the YouTube MCN section of the user dashboard.
    • Action: Enter text or clear to remove.
  3. Payouts Announcement

    • Purpose: Provide information or alerts on payout-related pages.
    • Action: Enter text or clear to remove.
  4. Rights Administration Announcement

    • Purpose: Display messages concerning rights administration services.
    • Action: Enter text or clear to remove.
  5. Other Services Announcement

    • Purpose: A general announcement area for any services not covered above.
    • Action: Enter text or clear to remove.

Changes to announcements are saved and will be reflected on the user-facing dashboard sections.


Fix Needed Reasons

This section allows administrators to define and manage a list of predefined reasons that can be used when a music submission or other items require corrections from the user. These reasons help standardize feedback and clarify what aspects need to be addressed.

  1. Reasons List:

    • Displays a list of existing reasons. Each reason is an editable text field.
    • Admins can modify the text of any existing reason.
    • A “Remove” button (represented by a minus icon) is available next to each reason to delete it from the list.
  2. Add New Reason:

    • A button, typically labeled “Add new Reason”, allows administrators to add a new blank reason field to the list. This new field can then be filled in with the desired text.
  3. Update Button:

    • A general “Update” button for this section saves all changes made to the Fix Needed Reasons, including new additions, modifications to existing reasons, and deletions.

Internal Process: These reasons are stored as an array of strings. When an admin marks an item as “fix needed,” they can select from this list, and the chosen reason is often communicated to the user, for example, via email notification.

Example Reasons visible in the interface:

  • “Audio File does not match specifed requirements, Please make sure it is in this specific requirements: Wav files at 16bit 44.1kHz”
  • “The audio quality does not meet the standard required by stores. Please re-record, produce or remix the release in a qualifying quality.”
  • “Proof of ownership required. Please provide a video of the DAW project with the sound on to check the legitimacy of the release, also if you have any contracts stating the ownership send them too. Send us all in a ticket via the contact us section.”

Distribution Reports Sheet Mapping

This sub-page within the Configuration section is crucial for standardizing the import of sales and distribution reports from various providers. Since each provider might use different column names (headers) in their Excel or CSV reports, this tool allows administrators to map those provider-specific column names to the system’s standard column names. This ensures that data can be consistently and accurately imported regardless of the source format.

Purpose

The primary goal of this page is to create and manage templates that define how to interpret report files from different distribution providers. By mapping their column headers to the internal system headers, the platform can correctly process and ingest the data. This mapping is essential for the “Import Reports” functionality.

Key Features and UI Elements

As seen in the interface:

  1. Navigation Tabs:

    • “All Configurations”: Navigates back to the main configuration page.
    • “Distribution Reports Sheet Mapping”: The current active sub-page.
  2. Action Buttons:

    • Create: Opens a form or interface to define a new mapping for a provider.
    • Filter requests…: A search input field to find specific mappings.
    • Search: Executes the search.
    • Reset: Clears the search filter.
  3. Mappings Table:

    • Lists all configured provider sheet mappings. Each row represents a mapping for a specific provider.
    • Columns Displayed (Mapping from Provider’s Sheet to System Field):
      • ID: Unique identifier for the mapping.
      • Header Row: The row number in the provider’s sheet containing column headers (e.g., row 1). This tells the system where to start reading column titles.
      • Provider: The name of the distribution provider (e.g., Horus Music). This links the mapping to a specific provider record.
      • Date Of Sales: Provider’s column for ‘Date of Sales’.
      • Data Entered: Provider’s column for ‘Data Entered’.
      • Sales Period: Provider’s column for ‘Sales Period’.
      • Store: Provider’s column for ‘Store’.
      • Store Type: Provider’s column for ‘Store Type’.
      • Country Of Sale: Provider’s column for ‘Country of Sale’.
      • Barcode: Provider’s column for ‘Barcode’.
      • Catalogue Number: Provider’s column for ‘Catalogue Number’.
      • ISRC: Provider’s column for ‘ISRC’. (Required for processing)
      • Quantity: Provider’s column for ‘Quantity’. (Required for processing)
      • Total: Provider’s column for ‘Total Amount/Earnings’. (Required for processing)
      • Currency: Provider’s column for ‘Currency’. (Required for processing)
      • Edit: A link/button to modify the existing mapping.
  4. Pagination: Standard controls for navigating through multiple pages of mappings.

Workflow

  1. Creating a New Mapping:

    • Admin clicks “Create”.
    • Selects the Distribution Provider from a dropdown.
    • Enters the Header Row number.
    • For each system field (ISRC, Barcode, Quantity, Total, Currency, Sales Dates, Store Info, etc.), the admin enters the corresponding column name or letter exactly as it appears in that provider’s report files.
    • Core financial fields (ISRC, Quantity, Total, Currency) are mandatory for the system to calculate earnings.
    • Saves the new mapping.
  2. Editing an Existing Mapping:

    • Admin clicks “Edit” on a mapping.
    • The form is pre-filled. Admin makes changes and saves.

Internal Process: When a report file is uploaded via the “Import Reports” page, the system uses the mapping defined here for the selected provider to correctly parse the data. This allows Distromotion to integrate with new distribution partners by adding a new provider and a corresponding sheet mapping without extensive code changes to the core report processing logic.