Column Matching Tips + Common Aliases to our Brainbase Data Points

Created by Francesco Ilardi, Modified on Mon, 01 May 2023 at 09:28 PM by Francesco Ilardi

Column matching may be overwhelming at times, especially for new Brainbase users. In this guide, we will provide several useful tips on how you should match your columns for the best-detailed end result. Read below for some crucial tips on how to best column match to get the best results in your sales reports. 

 

Note: If you are unfamiliar with column matching for uploading sales reports entirely, see our step-by-step guide HERE, then consider returning to this article to learn more about the best methods and tips. 

 

Compare the sales report to the contract

Before submitting a sales report, it is recommended that you compare your sales report to the associated contract uploaded into Brainbase. This way, you will be able to make any necessary adjustments to your sales report spreadsheet to be compatible with the data within the contract. This will also prevent you from going back to fix the spreadsheet in the middle of the upload process, which will save a lot of time.

 

The most crucial data points that should be compared between contracts and sales reports are:

  1. Properties

  2. Categories

  3. Territories

  4. Distribution channels

 

You can find these terms below the 'Rights' section of the 'Contract Details' view. For example, when comparing the contract to the sales report, it is important to make sure that the category trees are valid with the ones in the sales report. If you find that a category is included within a sales report that is not in the contract, you will need to adjust the report accordingly or utilize the 'Resolve' feature mentioned below this article. 

 

Here is an example of the contract's rights terms in the 'Contract Details' view.

 

Here is an example of a sales report associated with the contract above. All data points within the columns are valid since they are included in the list of options shown within the contract terms above.

 

 

 

Utilizing the Resolve Feature

Minor differences or grammatical errors in names or terms in your spreadsheet will not have to be fixed manually within the spreadsheet. That would be a huge pain! Luckily for you, Brainbase offers a resolve feature within the sales reporting process. If Brainbase detects that there are any discrepancies between the sales report and contract, the resolve component will appear and allow you to match the unidentified data point as an alias or a replacement to one found within the contract. This feature is especially useful with large spreadsheets that may have hundreds or even thousands of rows that may not have the exact naming convention within the contract. No need to worry about fixing each word individually - we have the 'Resolve' feature for that!

 

Column Skipping

The moment you land on the 'Column Matching' page, you should focus on matching the required data points that are located at the top of the column matching component shown in the image below. This list of data points is crucial for generating an accurate sales report and moving forward to the next step. 

 

Once you have matched these columns, all other columns that you matched thereafter will be used for a more detailed report. That being said, if a sales report contains a column that you are unsure about or if you find redundant, feel free to click on the ‘Skip’ option. It is common for the skip option to be used often during this process, so don’t hesitate to use it for optional columns.

 

 

 

Columns that are commonly ignored

Some column types may appear consistently within your sales reports that may be ignored altogether. Here are the two that are commonly included that may be ignored within the column matching process:

  1. Royalty Rate – Does not need to be matched in the columns since the royalty rate will take the percentage entered within the contract and apply it based on the condition configured.

  2. Royalties reported – Brainbase will calculate the royalties using all the data points you’ve provided once the report is submitted.

 

Common Aliases

  1. SKU – Unique ID for a product. Usually, a SKU looks like a serial number or a set of random characters.

  2. Sale type – Either Standard or F.O.B (Free On Board).

  3. Product name – The name or description of the product. 

  4. Category – A term used to describe the product type. The category list that should be used for a sales report can be found within the details view of the associated contract. Categories may be configured in nested in parent category trees within the contract.

    Examples of common category types:

    a. Apparel & Accessories
    b. Toys & Games
    c. Business & Industrial  > Advertising & Marketing
    d. Baby & Toddler > Baby Toys & Activity

  5. Distribution channel – Where a shipment of products is delivered before reaching the end consumer.

    Examples of common distribution channels:

    a. Wholesale
    b. Retail
    c. E-commerce
    d. Mass Merchandise
    e. Department Stores

  6. Unit sales – Amount of items sold. This number should always be a positive whole number. Returns will be calculated in another column. 

  7. Return – Amount of items that were returned. These numbers will be calculated as a negative against the gross sales. These numbers should be a positive whole number. Avoid using negatives as the system will automatically subtract this number to the number of Unit Sales. 

  8. Unit price – Price of each item in the currency stated in the contract.

  9. Gross sales – Total sales of the item in currency amount.

  10. Sales deduction – Discounts in the currency amount.

  11. Territories - Countries where the products will be shipped.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article