Optional Dataset
These files are not mandatory, but they help improve the user experience and allow the tool to be customized for each client.
They also enable important features and functions, such as attribute-based filtering and product family creation.
Each table indicates the column name in the file, the data type, and a description. Primary keys (unique values) are highlighted in bold.
Brands
A comprehensive list of brands for each product can be provided as optional data. It makes it possible to set brand-specific constraints and use the brand as a filter.
brand_name must be unique for each brand_id.
Variants such as ‘brand’, ‘Brand’, ‘BRAND’, or ‘brAnd’ must appear in the data as a single brand with a single brand_id.
Column | Data Type | Description |
|---|---|---|
product_id | string | Unique product identifier |
brand_id | string | Brand identifier |
brand_name | string | Name of the brand |
Other Options for Export
Export brand_id as a new column in the products file. The brands file should contain only two fields: brand_id and brand_name.
Export brand_id and brand_name as new columns in the products file (see examples in the Products section).
Suppliers
A comprehensive list of suppliers for each product can be provided as an optional data input. It is visible throughout the UI and allows for filtering by supplier.
supplier_name must be unique for each supplier_id.
Variants such as ‘supplier’, ‘Supplier’, ‘SUPPLIER’, or ‘supPllier’ must appear in the data as a single supplier with a single supplier_id.
Do you have a leading supplier for this product? If multiple suppliers exist, please select only the primary supplier for each zone.
Column | Data Type | Description |
|---|---|---|
product_id | string | Unique product identifier |
zone_id | string | Unique zone identifier |
supplier_id | string | Supplier identifier |
supplier_name | string | Name of the Supplier |
Other Options for Export
Export supplier_id and supplier_name in the actual_prices file.
Export supplier_id and supplier_recommended_sale_price in the actual_prices file. In addition, export both supplier_id and supplier_name in the suppliers file.
Product Classes
Assigning products to different classes helps categorize them according to how clients perceive them or other attributes to be used in the pricing strategy setup. This makes it possible to define the attributes per each product-zone combination.
Typical product classes include: KVI, Tail, Organic, etc.
Column | Data type | Description |
|---|---|---|
product_id | string | Unique product identifier |
class_id | string | Class identifier |
class_name | string | Name of the class |
zone_id | string | Zone identifier. Leave empty if the rule applies to all zones. |
Data Checks
The class_name column should contain only values from a limited, predefined set of options.
Other Options for Export
Export class_id as a new column in the products file. The product_classes file should contain only two fields: class_id and class_name.
Export class_id and class_name as new columns in the products file.
Segments
A list of customer segments, if applicable. The segment_id is referenced in the sales transaction history.
Column | Data type | Description |
|---|---|---|
segment_id | string | Unique segment identifier |
name | string | Name of the segment |
Families
A product family is a group of products that share identical or interdependent pricing. For example, juices of the same brand and type but with different flavors should have the same price.
If no product family records exist, Yieldigo provides a module within the tool to help create them. This module includes a suggestion mechanism that can quickly propose product groups for approval. To use this functionality, please ensure that the unit_count and unit_size fields are filled in the products file.
Family ratio is derived from the combination of unit_size and unit_count in the products table.
If family_ratio is not provided, all products within the same family are expected to have the same price.
Column | Data Type | Description |
|---|---|---|
product_id | string | Unique product identifier |
family_id | string | Family identifier |
Optional Columns
Column | Data Type | Description |
|---|---|---|
family_ratio | decimal | The ratio of products within the same family. If the products in a family are identical, the ratio must be the same. If the products differ in size, the ratio defines their proportion. |
Other Options for Export
Export family_id and family_ratio as new columns in the products file.
Promotions (Planned)
Future promotional data to be used in the regular pricing process. For example, to prevent regular price changes in a set period before a planned promotion or to set up constraints so that the regular prices are at least x% above the planned or most recent promotional price.
It is not needed if the Promotions Planner module is used to plan promotions directly in the integrated system. In that case, the relations to Regular Price Management are kept automatically.
Column | Data type | Description |
|---|---|---|
planned_promo_id | string | Identifier of a planned promotion |
zone_id | string | Pricing zone where the promotion is valid. Use the value -1 if the promotion is always valid for all zones. |
product_id | string | Product identifier |
promo_type_id | string | Identifier of a Promotion Type. Relates to the definition in the Promotion Types table. |
valid_from | date | First day of the promotion. |
valid_to | date | Last day of the promotion. |
promo_price | decimal | Promotional price, incl. VAT |
discount_promotion | bool | 0/1 indicator specifying whether the promotion is a discount. A value of 0 means the promotion is not discount-based (e.g., a free gift), while 1 indicates a discount promotion. |
Data Checks
The promo_type_id must correspond to the values defined in the Promotion Types table.
The promo_price should generally be lower than the current regular price in the price list, if it is a discount_promotion.
Competitor Prices
A summary of competitors and their prices. If available, historical data for e-shops is also highly recommended.
How often do you collect and update competitor data?
How long should the system keep these records, and for how long is a “collected” price considered valid? Are you continuously sending all valid prices?
Which competitors do you consider the most relevant?
Column | Data type | Description |
|---|---|---|
product_id | string | Product identifier |
zone_id | string | Use this field only if the competitor’s price is valid for specific zones. Leave it empty if the price applies to all zones. |
competitor_id | string | Competitor identifier |
date | date | Date when the price was collected. If this field is not provided, the import date will be used as the validity date. |
competitor_price | decimal | Price of the competitor, incl. VAT |
competitor_price_type | integer | 0 - Regular standard price 1 - Regular individual price (VIP customer discount, Golden Card) 2 - Global promotion (discounted price available to all customers - leaflets, special offers) 99 - Other The default value is 0. |
competitor_name | string | Name of the competitor |
Optional Columns
Column | Data type | Description |
|---|---|---|
url | string | The URL links directly to the competitor’s price on their website. |
detail | string | Any additional information |
Data Checks
Regular competitor prices should approximately correspond to the regular sale price.
Locked Products
A list of products that should not be repriced. These products are locked and excluded from the pricing process and will not be exported. Typical examples include items restricted by law (e.g., alcohol, tobacco, medicines) or products with the price printed on the cover (e.g., magazines).
If the products are identical across all zones, the zone_id column is not required.
Column | Data Type | Description |
|---|---|---|
product_id | string | Product identifier |
zone_id | string | The price must be exported for the zone, as the system plans prices at the zone level. |
Product Architecture
Allows pricing teams to define product ladders (such as Good–Better–Best) as reusable rules that enforce minimum and maximum percentage gaps between levels based on item or unit price, applied across custom-defined product groups. It provides item-level visibility and alerts when a rule cannot be met.
Once the Product Architecture, Architecture Groups, and Architecture Levels are set up manually in the application, the assigned product_ids can be imported automatically.
The names of the Product Architecture, Architecture Groups, and Architecture Levels must exactly match those defined in the application.
Column | Data Type | Description |
|---|---|---|
product_id | string | Unique product identifier |
architecture_name | string | Architecture identifier |
architecture_group_name | string | Architecture group identifier |
architecture_level_name | string | Architecture level identifier |
Optional Columns
Column | Data type | Description |
|---|---|---|
min_distance | integer | Minimum distance configured for the specified Architecture Group Level. If omitted together with max_distance, the default defined for the Architecture Level is used. |
max_distance | integer | Maximum distance configured for the specified Architecture Group Level. Can only be provided when min_distance is also specified. |
Data Checks
Min/Max distance values must be greater than 0. All products belonging to the same combination of Architecture + Architecture Group + Architecture Level must have identical distance values. If different values are provided for the same Group Level, the affected Group Level assignments are not imported.
Rounding Rules
Please provide the rounding rules using the rounding_rules.xlsx template.
Logo
You can provide your logo for display in the application; it will appear in the upper-left corner.
Logo Requirements
- Format: SVG (Scalable Vector Graphics, .svg) so the app can scale the logo automatically.
- Size constraint: The logo displays in a 24×24 px area. Avoid long text-only logos—they’ll be hard to read at this size.
- Background: Use a transparent background for colored logos. If the logo is black, provide it with a white background to ensure sufficient contrast and visibility.
If you only have PNG/JPEG, you can use an online converter to create an SVG.