9 Partner Feedback: Assortment Analysis
- Digitec Galaxus AG
INTRODUCTION
The assortment analysis is a detailed evaluation of all articles supplied by the partner and thus offers. The file provides information about the status of each item accordingly. We offer the file in English only.
The file provided is in Excel format and consists of three tabs:
Howto Short introduction about the Excel file.
Report Overview with article status and number of affected records (products).
Basis Detailed list of all partner items with all possible additional information.
Depending on the partner type - merchant or supplier, different technical conflicts can occur in the data processing procedures. All these conflicts are explained below.
EXPLANATION ASSORTMENT ANALYSIS
The partner is shown at the top, as well as the date and version of the analysis. The report for the analysis runs regularly. A report should be no more than 48 hours old.
All conflicts that arise during data processing are shown. This means that all conflicts generated by an article can be seen and not just the most important conflict of the article.
The first step of the processing is the assignment. Here it is checked whether a product already exists or whether it must be newly created. Here, all minimum requirements are checked and, if positive, a product is created. At the same time, the offer data such as price and inventory are checked and the offer is attached to the product. After each update of the offer data, the data runs through the offer data check again.
REPORT
This tab shows an overview of all existing conflicts. The cause of the conflict can be found in the "Conflict" column. The "Is Buyable" column shows whether the affected items are buyable. The "assortmentState" column describes the import level at which the conflict arose and the "No. item" column shows the number of affected items
BASIS
In the Basic tab, the individual conflicts are displayed at data record level. This allows you to see exactly which data record is causing which conflict.
To do this, we recommend using the filter function to reduce the list and address individual conflicts.
PRIORITIZATION AND RESOLUTION OF CONFLICTS
We are aware that it is challenging to have all offered products purchasable. Therefore, it is recommended to address the points that allow assignment to existing products first (Assignment = Not Assigned).
We provide our partners with the Feedchecker to identify the errors even before the import.
Below you will find a detailed list of all possible conflicts.
Please note that conflicts marked with a yellow resolution suggestion can only be resolved by Digitec Galaxus.
Proposed solutions which are marked in blue can be solved by yourself. Here you usually have to optimize your data in the feed and let the solutions flow directly into the feed.
Recommended prioritization
Allow assignment through valid GTIN
Resolve offer conflicts
Create all products
IMPORT AND VALIDATION CONFLICTS
For information on technical import and validation conflict resolution, click here:
8 Troubleshooting for active datafeeds
OFFER DATA CONFLICTS
The following is an overview of all conflicts that arise due to assigned offers.
Please note the model you are working with Digitec Galaxus!
OC - Supplier (Retail)
Conflict | Error | Solve conflict |
|---|---|---|
SPD is deactivated | internAL The offer is excluded from Digitec Galaxus / Galaxus Germany. | |
Purchase price is outside of the anticipated price range | The purchase price is below or above the permissible price range of the corresponding product. | |
Purchase price is smaller or equal to 0.01 | The purchase price of the is less than 0.01 or greater than 100'000. | |
Minimum order value exceeds the limit | Minimum order quantity * Purchase price → may have a maximum purchase value of CHF 50,000. | |
Product is deactivated | internAL No offer with positive availability | |
| RestockDate limit exceeded (InStock) Restock date no later than now + 3 months (OnDemand) | |
Orders without restock date are not allowed | Offers are not used in buying and selling because there is no availability. Orders without stock are not carried out. | |
Digital products are not supported | Digital products are only permitted for partners with the appropriate configuration. | |
Assortment is deactivated | internAL "Use assortment" is deactivated in the assortment control. The partner is currently not in a productive state. | |
The minimum order quantity is not a multiple of the order quantity step | The maximum permitted minimum order quantity and order quantity step is 200 for direct deliveries and 500 for warehouse deliveries. | |
Orders on restock date are forbidden | Offers are not used in purchase and sales if stock = 0 (regardless of RestockDate). | |
Product not storable | INTERN We are not allowed to store certain products for various reasons. |
OC - Merchant
Conflict | Error | Solve conflict |
|---|---|---|
Sales price is not between 0.01 and 100'000 | The sales price is less than 0.01 or greater than 100'000. | |
Currency is not supported | We receive a different currency than we expect. | |
Multiple offers available from same merchant | More than one active offer per merchant on the same product is not allowed. | |
VAT rate is not valid | The VAT of the offer does not match the product or product type. | |
Manual deactivation of the merchant offer | internAL The marketplace offer is deliberately ignored by Digitec Galaxus / Galaxus Germany. | |
Cancelation of the merchant offer by the merchant | internAL Offer cancelled via CMI or EDI messages. The offer is automatically reactivated after 2 weeks if stock has been updated. | |
Restock date range exceeded | Stock = 0 AND Restock Date > today + 3 months | |
Orders without restock date are not allowed | The partner configuration blocks all offers for sale in the absence of availability. | |
Digital products are not supported | Digital products are only allowed for partners with the appropriate configuration. | |
The supplier's assortment is deactivated | internAL Digital products are only permitted for partners with the appropriate configuration. | |
Minimum order quantity or increment order quantity exceeding the threshold | Maximum allowed minimum order quantity and order quantity step is 500. | |
Minimum order quantity is not a multiple of increment order quantity | Minimum order quantity must be a multiple of the order quantity step. Here, for example, it would not be allowed if the minimum order quantity is 2 and the order quantity step is 5. | |
Orders with restock date are not allowed | Offers are not used in purchase and sales if stock = 0 (regardless of RestockDate). | |
No stock information | Offers are not used in the sale as no availability is indicated. |
PRODUCT DATA CONFLICTS
The following is an overview of all conflicts that have to do with product data and product creation
The minimum criteria for the product data, you can find here:
PC - Provider Product Conflicts
Conflict | Error | How to solve Conflict |
|---|---|---|
Gtin has no global validity | Gtin is not globally valid according to the GS1 standard. | |
Gtin is missing | No Gtin available. | |
Null | ProviderKey appears in the assortment, but we have no GTIN or other product data for this data set |
PC - Product Data Conflicts purchasing
Conflict | Error | How to solve Conflict |
|---|---|---|
TitleDe missing | Product creation pending, as the product title in German is missing. This is a minimum criterion for product creation. | |
Images missing | Product creation pending, as pictures are missing. | *The image is a minimum criterion for product creation. |
ExclusionCriteriaMatch | internAL Product type and / or brand is excluded from product creation. Certain brands and product types are deliberately excluded. This is due to compliance requirements, NDAs and non-physical products. | |
Brand missing | Product creation pending, as the brand is missing. | *The brand is a minimum criterion for product creation. New brands are created within a few days |
ProductType missing | Product creation pending, as the product type could not be determined. | *The product type is a minimum criterion for product creation. The assignment usually takes place within a few days. |
PC - Product Data Conflicts sales
Conflict | Error | How to solve Conflict |
|---|---|---|
Images missing | Product clearance denied as images are missing. | *The image is a minimum criterion for product clearance. |
QualiltyProperty missing | Important (gatekeeper) features are missing that are essential for the customer to purchase the item. | |
Compliance | Important compliance data is missing, which is absolutely necessary for the customer to purchase the item. |
*these conflicts are dependent on technical processes, these can take a few days and delay further processing, thus the correct conflict.