This guide shows you how to handle the errors in the email, you will receive after POS upload.
When uploading the Zoo SE POS report to effectmanager, we validate the format and data in the file.
This is to ensure that your data imported to effectmanager is not corrupted.
If your file ha corrupted data, you will receive an email that details the error.
Below is how to handle them:
- VAT rules in the file
- Chain rule in the file
- Mandatory fields validation
- Period Validation in the file
- EAN Validation in the file
- Zero Sales Validation in the file
VAT rule in the file
Zoo SE Sales files exclude VAT. However, all Turnover in the POS cubes includes VAT. If the data in the sales file lacks VAT information, we automatically add VAT to the Turnover when displayed in the cube.
We apply VAT rates based on the following rules.
If data in the following columns does not match the rules, the rows are rejected for import.
| Column F if rule | VAT rate % |
| If Column F = Online Sverige | 25% |
| If Column F = Online Norge | 25% |
| If Column F = Online Finland | 14% |
|
If Column F = Does not contain "Online" |
25% |
|
If Column F = Empty or does not match the rules above |
Rows are rejected |
Chain rule in the file
Chains on Zoo SE are based on the data in the following columns: E and F.
If data in the following columns does not match the rules, the rows are rejected for import.
| Rule | Chain Name |
| If Column E = Retail | Retail SE |
| If Column E = Online | Column F - E.g Online Norge, Online Finland or Online Sverige |
Mandatory fields validation
The following columns are mandatory: A, B, D, E, F, G, I, J, L, O, R, S
To ensure high data quality, the file will be rejected if mandatory fields are empty.
Please check the file on the rows mentioned from the alert and fix the data issue in the file before reloading the file to effectmanager.
Period Validation in the file
In the file, the period of the Sales data is provided in Column A (Year), Column B (Month), and Column D (Date).
The following validates are put in place for each column.
If data in the following columns does not match the rules, the rows are rejected for import.
| Column | Validation |
| A - Year | Must be a numerical value of no more than 4 digits. |
| B - Month |
Must be one of the accepted values: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, and Dec (both upper and lower cases). Values are imported based on the following rule: Jan = January = 01 Month |
| D - Date |
Must be a numerical value of no more than 2 digits. Values between 01-31 are accepted. |
EAN Validation in the file
We have two validations of EAN for the import, these will return two different messages in the email.
- Invalid EAN format
- Blank or 0 EAN format
Invalid EAN format / 0
The EAN format must be numerical, if the cell contains any other value, the lines are rejected for import. You will get the below alert in the email.
You can either input a random numerical value or insert the correct EAN to import the lines of sales data.
Blank EAN format
If there are any Products where EAN is BLANK, the products are added to the EAN Mapping file. Here you can input your Product EAN to get the POS data categorized with your data.
Products added to the EAN Mapping file will look like this in the Email.
Zero Sales Validation in the file
To ensure we do not import zero sales to the database, there is a rule to reject the lines without any Turnover and Volume for the last 6 periods in the import.
If you want to report on Zero Sales, please use the POS cubes Key figures.
The rule:
-
Volume 0 + Turnover 0 = Both Columns have 0 → DO NOT IMPORT
-
Volume BLANK + Turnover BLANK = Both columns have BLANK → DO NOT IMPORT
-
Volume is different from 0 + Turnover 0 → Import the data.
-
Volume 0 + Turnover is different from 0 → Import the data.
Email Message
