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 bool 0/1 indicator specifying whether the price is promotional 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 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 https //en wikipedia org/wiki/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 if you only have png/jpeg, you can use an online converter https //www google com/search?q=online+svg+converter to create an svg