Master data

The gross price of the product. Note that there are different columns for Gross price depending on currency. For more information, see https://big.btwentyfour.com/.

An integrated supplier might face a situation when a buyer require more information in a publication than they can provide from within their business system. A validation error have occured when a publication have been validated, saying there are data missing. With the possibility in the portal to download an uploaded PRICAT in Excel format, an integrated supplier can download a publication and add information that cannot be provided from within their business system.

When mapping sizes under "Data mapping" the process is to first select a target set and then a target value within this set. Below is a list of all size sets available, and examples of sizes available in each set. Apparel/Gear - Age (Category) Adult, Infant, Kids Apparel/Gear - Age (Months) 0-3, 18, 24-36 Apparel/Gear - Age (Years) 0-1, 8, 15-16 Apparel/Gear - Areal (m2) 1.0, 5.5, 10.0 Apparel/Gear - Ball Size 3, 5, Futsal Apparel/Gear - Blade Curve (special) 24R, 96L, 120L Apparel/Gear - Bra Size (Cm/Cup) 60A, 75CD, 90F Apparel/Gear - Bra Size (Inch/Cup) 28A, 38DD, 54F Apparel/Gear - Bra Size (Uni/Cup) S/A, M/CD, 2XL/E Apparel/Gear - Cross-Country Skis (cm/kg-kg) 147/20-30, 182/65-80, 207/95+ Apparel/Gear - Flexion 35, 135, Stiff Apparel/Gear - Handwear (Hand/Size/Fingers) Right/Youth S, Left/M-L/Cadet, Right/3XL Apparel/Gear - Handwear (Num) 1-2, 8.5, 20 Apparel/Gear - Hat Size (Num) 6, 7 1/8, 8 Apparel/Gear - Ice Skates (Adult Size & Fit) 6 D, 10.5 R, 15 FIT3 Apparel/Gear - Ice Skates (Holder/Steel Size) 1, 7, 14 Apparel/Gear - Ice Skates (Youth/Junior Size & Fit) 1 D, 5.5 R, 13Y EE Apparel/Gear - Infant (uni) 2XS, M, XL Apparel/Gear - Kids/Child/JR (centi) 104, 122/128, 158-164 Apparel/Gear - Kids/Child/Jr (Plus) 1X, 3X/Long, M+ Apparel/Gear - Kids/Child/Jr (Uni) XS, M-L, 2XL/Short Apparel/Gear - Kids/Child/Jr (Uni/Inch) 2XS/4, M/32, 2XL/36 Apparel/Gear - Kids/Child/JR (US) 1, 8-10, 20 Apparel/Gear - Left/Straight/Right LEFT, RIGHT, STRAIGHT Apparel/Gear - Men/Unisex (EU) 27, 36/Capri, 74 Apparel/Gear - Men/Unisex (Plus) 1X, 2X/Capri, 4X/Long Apparel/Gear - Men/Unisex (UK) 4, 22-24, 56/Long Apparel/Gear - Men/Unisex (Uni) 2XS, M-L, 4XL/Long Apparel/Gear - Men/Unisex (Uni/Inch) 2XS/6, M/30, 5XL/36 Apparel/Gear - Men/Unisex (US) 2, 8/Capri, 16/X-Long Apparel/Gear - Neutral (no unit of measure) 0,1-0,2, 24.5, 50 Apparel/Gear - No Size No Size Apparel/Gear - One Size OneSize, OS Child, Adjustable Apparel/Gear - Pets/Dogs (Uni) XS, M, XL Apparel/Gear - Quality Grade 1, 5, 10 Apparel/Gear - Resistance (level) HARD, Light Apparel/Gear - Roman Size I, IV, X Apparel/Gear - Rope Size (mm/m) 2/150, 4/7, 8/50 Apparel/Gear - Speed Extra Fast, Regular, Ultra super slow Apparel/Gear - Waist/Length (Inch/Inch) 21/10, 30/32, 66/38 Apparel/Gear - Women (EU) 20, 38/Short, 62 Apparel/Gear - Women (Plus) 1X, 2X/Capri, 4X/Short Apparel/Gear - Women (UK) 2, 16-18, 26/Short Apparel/Gear - Women (Uni) 2XS, M-L, 5XL/2X-Long Apparel/Gear - Women (Uni/Inch) 2XS/2, M/24, 4XL/34 Apparel/Gear - Women (US) 4, 12-14, 26/Short Apparel/Gear - Youth/Intermediate (Uni) XS, M/Short, L-XL Apparel/Gear - Youth/Intermediate (Uni/inch) 2XS/24, M/26, 3XL/34 End Plug - Ice Hockey Stick F-Shape, R-Shape, T-Shape Footwear - Children/Youth Size (Left/Right) Left, Right Footwear - Children/Youth Size (UK) 1.5C, 6C-8C, 12C Footwear - Children/Youth Size (US) 2, 5.5W, 10C-12.5C Footwear - Euro Size 15.5, 38-39, 46 2/3 Footwear - Men/Unisex Size (UK) 2, 6.5-8, 13.5W Footwear - Men/Unisex Size (US) 5, 10.5W, 12-14 Footwear - Mondo Size (Cm) 13, 24.5, 35.5 Footwear - No Size No Size Footwear - One Size OneSize, OS Infant, OS Women Footwear - Women Size (UK) 5.5, 9N, 15XW Footwear - Women Size (US) 3, 9.5N, 19XXW Size Not Applicable No Size Unites - Measurement (cm*cm*cm) 185*60*1.5, 300*100*10, 400*100*10 Units - Circumference (cm) 10, 56-58, 174 Units - Circumference (Inch) 1 1/4, 7 7/8, 24 Units - Diameter (mm) 26, 42.5, 246 Units - Measurement (cm) 2.5, 198, 368 Units - Measurement (cm*cm) 2.5*500, 120*60, 210*210 Units - Measurement (Foot) 1'2, 6', 24'8 Units - Measurement (Inch) 1/4, 24, 62 Units - Measurement (m) 2.5, 90, 450 Units - Measurement (mm) 2, 94, 3500 Units - Measurement (mm*mm) 10*145, 32*590, 47*559 Units - Volume (cl) 1, 48, 100 Units - Volume (dl) 1, 5, 10 Units - Volume (Litre) 0.125, 45-50, 95 Units - Volume (ml) 2, 100, 450 Units - Weight (g) 1.5, 425, >900 Units - Weight (kg) 1.25, 50-60, >2.0

Go to https://www.sgidho.com/ to read more about FEDAS and to search for FEDAS codes. As a member on their site you can download a list of FEDAS codes.

The delivery end date for the first delivery period (1st delivery window). For more information, see https://big.btwentyfour.com/.

The delivery from date for orders with delivery in the first delivery period (1st delivery window). For more information, see https://big.btwentyfour.com/.

The last possible delivery date for the product. Format YYYY-MM-DD. For more information, see https://big.btwentyfour.com/.

The first possible delivery date for the product. Format YYYY-MM-DD. For more information, see https://big.btwentyfour.com/.

The last possible supplementary order date for product. Format YYYY-MM-DD. For more information, see https://big.btwentyfour.com/.

The first possible supplementary order date for product. Format YYYY-MM-DD. For more information, see https://big.btwentyfour.com/.

The message template for master data (PRICAT) contains a lot of columns where data can be added. Not all columns must have data. There are a few columns marked with "B24 Mandatory", where data are mandatory to be filled in. Columns marked with "B24 Recommended" are the recommended columns to add data into. Please note that different buyers might have different requirements regarding what data is to be added. The master data template consists of two sections: Header section (data to be added in row 4) Data added in the header section will be valid for all items. * Make sure to add a correct GLN number. For more information: What is a GLN? * "Period" must be mapped in the portal under "Data" - "Seasons" before importing the master data. For more information: How to map seasons? * Make sure "Valid from date" and "Valid to date" are before and after all dates regarding order in the items section. Item lines section (data to be added from row 9) The data added at row 9 and 10 in the master data message template are examples only and should be deleted. Please note that it is mandatory to add data for each item line in one of the two columns for barcodes, "Barcode EAN13" or "Barcode UPCA". It is not mandatory to add data in both columns. The "B24 Mandatory" and "B24 Recommended" columns in the item lines section are listed below. Click on each link for more information. What data should be added in the PRICAT message template for: Action Model no Product name Size Size set Color code Color ItemID Barcode EAN13 Barcode UPCA Description Goods class FEDAS Goods class Supplier Brand Gender Model color id Unit of measure Gross price Pre net price Invoice method Pre valid order date from Pre valid order date to Pre valid ship date from Pre valid ship date to Supplementary valid order date from Supplementary valid order date to Supplementary valid ship date from Supplementary valid ship date to Delivery date from 1st d w Delivery date to 1st d w More information: Step by step guide from uploading to publishing master data.

The last possible delivery date for the product. Format YYYY-MM-DD. For more information, see https://big.btwentyfour.com/.

The first possible delivery date for the product. Format YYYY-MM-DD. For more information, see https://big.btwentyfour.com/.

The end date for buying at the pre order price specified in the price catalogue. For more information, see https://big.btwentyfour.com/.

The first possible order/pre order date for the product. Format YYYY-MM-DD. For more information, see https://big.btwentyfour.com/.

Specification on how the product will be invoiced. For more information, see https://big.btwentyfour.com/.

The net price (field used for pre order net price when relevant), with discount applied for the product. Note that there are different columns for Pre net price depending on currency. For more information, see https://big.btwentyfour.com/.

The unit of measure for the product: such as PCE, PAIR etc. For more information, see https://big.btwentyfour.com/.

The gender category, such as: Men, Woman, Unisex. For more information, see https://big.btwentyfour.com/.

The brand of the product. For more information, see https://big.btwentyfour.com/.

A file that has failed on import will have a "Status" saying "Rejected", and will be marked red. Example of error "Reason" could be “Failed validation”. Whatever causes the validation error, it needs to be corrected, and the file uploaded again.

A "Pack PRICAT" can contain products that can be sold as packages to their customers. For example, a supplier wants to sell to a certain Buyer a package that contains 2 shirts, 2 hats and 1 sweater. If the buyer is interested to buy some of the products of the package, the buyer will be obligated to buy the whole package and will not be able to buy these products individually. The articles can be sold individually to the final consumer. Please follow below requirements: 1. The PRICAT should have the same structure as a the normal PRICAT. 2. Each of the articles and packages should contain their own Barcode. 3. Unit of Measure can be: * PACK= Package * PCS= Pieces 4. Logistic Unit should be: * TU = Trade Unit (Package) * CU = Consumer Unit (Pieces) 5. Num Units CU in TU should be: * For the TUs: Please write the sum of all the articles that a package contains. * For the CUs: Please write the quantity of each of the articles in the package. 6. Product Set ID should be represented with a unique number for each box and their articles.  

Perceived main/base/indicative/dominating color of the product.  - IndicationColor is typically used for color-categorization and filtering products in webshops and other B2C sales surfaces.  Ex: White shoes with red laces and red logo can have the color "White/Red" however, indication color "Basic White". For updated information, see https://big.btwentyfour.com then click on "PRICAT" For codes, see: https://big.btwentyfour.com/sets or https://www.sgidho.com/SitePages/FEDAS%20Color%20Code%20Concept%20(New%20Oct.2018).aspx 

When Btwentyfour speaks of "Master data" we mean product information. Think of it as an excel-sheet containing all items you as a supplier sell.   The word "SKU" (stock keeping unit) is often used and contains of different propertys, attributes, descriptions, references etc.  The three standard ones are:  * Item ID     (often modelNO+size+color) * Barcode   (EAN13, UPCA) * ModelNO Please note, when published to a buyer, Barcode and ModelNO are locked for the season and cannot be changed without deleting the SKUs first. (see "How to delete items from the database?"). Regarding the above, master data is shared between buyers, except for sales prices (netPrice). This means one item has determined data for each season: one barcode, one modelNO to all customers. This makes handling master data easier. A supplier can have a master data file with their whole catalougue, without prices. By uploading that in BOP with your own GLN as BuyerGLN, the masterdata is only uploaded once per season. Then, separate catalogues (PRICAT) with only barcode and prices can be uploaded to each buyer. This could save time, by working with the same masterdata file internally, and using BOP to send the master data + prices to the buyers. 

Click on the tab for "Validation errors", for more information about the validation errors. The validation errors will be listed. There are four columns with information regarding the validation errors: * Description * Properties * Locations * Owners Click the arrow after each numbered row to expand that row for more information. Description A description about what is causing the validation error. Could be for example that specified data is required or that mapping is needed towards a B24 set or a set uploaded by the buyer. When expanded, for example all sizes needed to be mapped are shown. Properties Defines which properties that are affected by the validation errors. Locations Collapsed it will show the affected model numbers*. Expanded it will also show the affected item id´s. *Note that it will currently only show the model numbers for the 30 first affected item id´s, same as for the item id´s listed. This means that not all affected model numbers might be listed. Owners Shows the owner of the validation rules. If B24, it means that the validation rules are something the platform requires. If a buyer, it means that the buyer has requirements that need to be fulfilled. It could be that they need certain information to be included in the file, or information to be mapped in a specific way. More information: How to see that a publication has been validated with errors?

When validation errors have been corrected, for example mappings have been made, it is possible to re-validate the publication. Click the three dotted icon on the row for that publication and select "Validate" in the pop-up menu. The current number of validation errors will be shown in the pop-up window. Click "Validate". More information: Step by step guide from uploading to publishing master data. How to see that a publication has been validated with errors? How to see that a publication has been validated with no errors?

A notification saying the publication has been validated means that there are no validation errors, and the publication is ready to be published. More information: Step by step guide from uploading to publishing master data. How to see that a publication has been validated with errors?

A notification will say if any validation errors have been found. An icon will be visible in the "Validation errors" column, saying how many validation errors there are in the publication. More information: Step by step guide from uploading to publishing master data. How to re-validate a publication? How to see that a publication has been validated with no errors?

To see why a has failed on import, click on the message number. The "Message" will open, with more information about the message. Scroll down to "Validation logs", for more information about the validation errors. Under "Description" it´s possible to see an explanation of the validation error. In this example it says that "Timespan must be created manually, mapping to universal timespan". "Location" says that "season" is affected, and "Value" shows that "All season 2024" has not been mapped. The season needs to be mapped, and the file uploaded again. More information: How to map seasons?

If no error occurs on import, "Status" will be shown as "Complete” and marked green. “Complete” means that the file has been imported with no generic validation errors. Note that a uploaded master data file needs to be published for the recipients to receive it. Preferably the data should be validated first.

The goods class of the product as a FEDAS product classification key. Search for FEDAS product classification keys here: https://www.sgidho.com/ For more information, see https://big.btwentyfour.com/.

To see why not all items have been imported, click on the message number. The "Message" will open, with more information about the message. Scroll down to "Validation logs", for more information about the validation errors. Under "Description" it´s possible to see an explanation of the validation error. "Properties" will show any property affected and "Location" will list the items that have not been imported. In this example the barcode checksum validation have found incorrect barcodes. Could be that they are added to the wrong column in the template, have the wrong barcode type. These items needs to be corrected and uploaded again. Could be in the same file that has previously been uploaded, with the items already been imported, or in a new file. More information: How to see in "Messages" that not all items have been imported?

When a master data file has been uploaded with validation errors for one or several items, "Status" will be "Incomplete", and marked orange. "Reason" will say how many items that has been rejected on import from the total items in the master data file. In this example, 12 items have been rejected and not imported to the portal. A total of 112 items have been imported and can be validated and published. The rejected items needs to be corrected and uploaded again. Could be in the same file that has previously been uploaded, with the items already been imported, or in a new file. More information: How to see in "Messages" why not all items have been imported?

It is possible to delete items from the database by uploading a PRICAT with action "Delete" on item lines. Enter "Delete" for the items to be deleted in the column for "Action". To delete items from the database, PRICAT´s with action "Delete" must be directed to the suppliers own GLN as the "Buyer" GLN. Enter the same GLN for "Buyer" GLN... ...as for the "Supplier" GLN. Items will be deleted from the database according to the "B24 season" that the season in the uploaded PRICAT have been mapped to in the portal. Make sure the season in the PRICAT is the same as the season the items should be deleted from. Save the file, and upload it to the portal. Note: For item lines with action "Delete", only item id or a barcode is necessary.

Go to "Documentation" - "Message Templates". Messages templates are listed. Click the "Download" icon for the "ExcelDeclTemplate_PRICAT.xlsx". The Message template for PRICAT will be downloaded. More information: Step by step guide from uploading to publishing master data.

Statistical toll number for product, (a.k.a. "intra-stat number", "Harmonized System Code", "HS-code"). Should be 10 digits. For more information, see https://big.btwentyfour.com/.

Follow these steps for a guide on how to upload and publish a master data file (PRICAT): * How to download a message template for master data (PRICAT)? * How to add data in the master data (PRICAT) message template? * How to map seasons? * How to setup currency rules in "Supplier settings"? * How to upload a master data file (PRICAT)? * How to map data? * How to validate a publication? * How to publish a publication?

Yes, the PRICAT should preferably be validated, and needs to be published to be send to the receiver. Go to “Products” – “Publications” to validate and publish the PRICAT. “IMPORTED – OK” means that the PRICAT have been imported with no generic validation errors. Generic validations exist for all messages and all message senders in BOP. Generic validations are in place to make sure that all messages are uniform and follow the same logic. Some examples are check sum validation on EAN or GLN codes, legal currency code checks or that the supplier segment is present in the message header. All messages, except for PRICAT, that fails the generic validations in BOP will be stopped prior import into the platform.

The supplier's own goods class of the product. This goods class must be mapped to "B24GC6" or "FEDAS" in the Btwentyfour Open Commerce Platform if the receiver of the masterdata has such validations. For more information, see https://big.btwentyfour.com/.

It´s possible to filter by published or not published publications. By default, nothing is selected. All publications are visible in the publications list. Click to view the filter options. To filter by published publications, select "Published". Click "Search". Only published publications will be shown. To filter by not published publications, select "Not published". Click "Search". Only not published publications will be shown.

Click the sub model to open the product detail window.

Click the checkbox for a model to select that model, and all underlying sub models and sizes. The checkbox will be checked, and a floating bar appears saying how many products that has been selected. If expanding the model and clicking the size run it is noticeable that all underlying sub models and sizes has been selected. It is possible to select several models by clicking the checkbox for each model.

Click the "arrow right" icon for a model to expand that model. That model will be expanded. Click the "arrow down" icon for that model to collapse the model. The model will be collapsed.

Click the "arrow right" icon on column heading level to expand all models. All models will be expanded. Click the "arrow down" icon on column heading level to collapse all models. All models will be collapsed and listed as by default.

Click the "list view" icon to view models listed ordinal by the model number. This is the default view.

Click the tab for "Recipients", to see recipients of a publication.

Click the "Models" tab for a list of all models in a publication. All models are listed by default.

A link to the message that was imported to the platform. Click on the "Message in" number to go to that message under "Communication" - "Messages". Via this link it´s for example possible to download the original file that was imported to the platform.

Click on a publications "Name" to view more detailed information about the publication.

Click the size run to view available sizes for that sub model. Available sizes will be listed in a pop-up menu.

It´s possible to filter publications by season. By default, there are no selected season. All publications are visible in the publications list. Click to view available seasons. For a supplier the suppliers season name will be listed, with the B24 season names in parentheses. On the buyer side the "Select season" function uses the buyers season name. Click to select a season to filter by. Click "Search". The result will be shown.

A list of imported PRICAT´s, sorted in chronological order based on search. All publications visible by default. Publications can be validated and published in this section. * State – Show the state of a publication. * (Timestamp) – TBC. * Name – The name of the publication as stated in the PRICAT as “Name”. Click on a publications name to open that publication and view more information about the publication. * Season – Name of the season. * For suppliers, the season "Name" as stated in the PRICAT, with the mapped "B24 season" in parentheses. * For buyers, the buyers season name if mapped from a "B24 season", with the "B24 season" as mapped by a supplier in parentheses, or the "B24 season" as mapped by a supplier in both locations, if season is not mapped by the buyer. * Checked out products – A value for how many products of all products in a publication that have been checked out by a buyer. * Updates – TBC. * Validation errors – An orange-colored triangle will be visible to notify if there are any validation errors in a publication. A number to the right of the triangle will inform about the number of validation errors.

This is where to search for products, validate and/or publish publications to a receiving party. It´s also possible to create product and/or media selections. These selections will also be listed in this section.

To upload a master data file (PRICAT), go to “Communication” – “Messages”. Drop a file from the computer into the “Drop a file here or click to browse…”-field, or click the same field to browse for a file on the computer. “Pricat” is selected by default in the drop-down list. Click the drop-down list and select the corresponding format for which the file was saved in. There are different formats available depending on which message type to be uploaded. Select “Excel Declarative…” if uploading an Btwentyfour Excel template. The Btwentyfour Excel template can be found at https://big.btwentyfour.com/. Click “Upload” to upload the file. More information: Step by step guide from uploading to publishing master data.

There are several message types that can be uploaded manually to the platform, and in different formats depending on message type. The most common situation is that a party does not have a system integration to the platform and need to manually upload a master data file (PRICAT) to the platform. To upload a file, go to “Communication” – “Messages”. Drop a file from the computer into the “Drop a file here or click to browse…”-field, or click the same field to browse for a file on the computer. Select message type for the file to be uploaded. PRICAT is selected by default. Click the drop-down list and select the corresponding format for which the file was saved in. There are different formats available depending on which message type to be uploaded. Select “Excel Declarative…” if uploading an Btwentyfour Excel template. The Btwentyfour Excel template can be found at https://big.btwentyfour.com/. Click “Upload” to upload the file.

Statistical toll number for product, (a.k.a. "intra-stat number", "Harmonized System Code", "HS-code"). Should be 10 digits. For more information, see https://big.btwentyfour.com/.

The model color id of the product. A model color id could be a concatenation of Model no + Color code. For more information, see https://big.btwentyfour.com/.

The supplier's own goods class of the product. This goods class must be mapped to "B24GC6" or "FEDAS" in the Btwentyfour Open Commerce Platform if the receiver of the masterdata has such validations. For more information: What is goods class? For more information, see https://big.btwentyfour.com/.

The supplier's unique item ID of the product. An item ID could be a concatenation of Model no + Color code + Size. For more information, see https://big.btwentyfour.com/.

Describes the status of the product, use "Add" for new or updated products and "Delete" to remove a product from BOP. If a product is already checked out by a buyer, and re-uploaded by the supplier, the product will receive action "change" upon the next export. For more information, see https://big.btwentyfour.com/.

Goods glasses comes in many standards, could be FEDAS, very common in the sports- and outdoor sector, DTB/BTE commonly used by European fashion suppliers or any other standard or supplier specific value. Buyers tend to use standards such as FEDAS or their own internal values and will usually require the supplier to map the goods classes towards a universal set. BOP handles many of the common standards such as FEDAS, BTE and DTB but also holds two internal set's; b24gc (old standard) and b24gc6 (new standard). FEDAS Read more about it here: https://www.sgidho.com/ B24gc6 The b24gc6 standard covers the need for most sectors within retail and is constantly evolving to cover even more segments of the industry. The standard is divided into four levels, looking like this: Position 1 - Product Category Example: 2 - Clothing W Position 2-3 - Product Category Sub-class Example: 03 - Vests Position 4-5 - Style Example: 12 - Fleece Position 6 - Style Sub-class Example: 1 - Windproof B24gc6 Code: 203121 - Wmns Vests Fleece Windproof Conversions in BOP BOP supports automatic conversions of some goods class standards into b24gc6 eaning that suppliers will not have to map towards b24gc6 themselves. To summarize it looks like the table below.   If a supplier sends goods classes with BTE/DTB or b24gc set we will automatically translate them into b24gc6 codes with b24-registry. If a supplier sends goods classes with FEDAS, it will not be translated into b24gc6, such mapping can be done on the buyer side if requested.   If a supplier sends goods classes with any other set they will be forced to map the codes to either b24gc6 or FEDAS codes in the Btwentyfour Omnichannel Platform if the receiver of the masterdata has such validations.

The supplier's UPC-A code of the product. The UPC-A format is 12 digits. For more information, see https://big.btwentyfour.com/.

The supplier's EAN-13 code of the product. The EAN-13 format is 13 digits. For more information, see https://big.btwentyfour.com/.

The product color in plain text. For more information, see https://big.btwentyfour.com/.

The size set of the product. Size set is an identification table for the size. Ex: "38" is a womens' euro shoe size, but value "38" set out of context could indicate any kind of size. Size sets should be used and ideally describe the kind of product and what intended target group the size is meant for, or at least help to categorize the size value so it can be easily distinguished from other size values in your product data feed. For more information, see https://big.btwentyfour.com/.

The name of the product. In difference to "Description", "Product name" usually does not include color or size. For more information, see https://big.btwentyfour.com/.

Description of the product, preferably including: model name, colour and size. For more information, see https://big.btwentyfour.com/.

The size of the product. For more information, see https://big.btwentyfour.com/.

The code of the product color. For more information, see https://big.btwentyfour.com/.

The model number of the product. Same product in different sizes and colors, should share the same model number for any sorting to work properly.  In difference to "ItemID" a model number doesn't have to be unique. For more information, see https://big.btwentyfour.com/.

Selections can be used by both buyers and suppliers in BOP. The purpose of the selection is to create an excerpt of product from one or many publications, narrowing master data down to a relevant choice of products for the user. Selections can be downloaded or exported in BOP via a standard PRICAT integration or be sent as a publication from a supplier to a buyer. Suppliers tend to use Selections as a way of highlighting products within their master data to buyers, could be a new running segment or all gloves within a winter collection etc. Buyers tend to use selections as a filter, letting them only export products relevant to them to their ERP, could be all product from a supplier and season that the buyer intends to order etc. NOTE: Products in a selection will be subject to updates just as products in a publication, meaning that product properties and/or dimensions can be added or changed via new master data uploads from the supplier.

A "Proposal" is a selection of products from one or many publications, created by a supplier and can be published to a buyer.

A private selection can only be viewed by the user who created it. A public selection can be viewed by all users within the organisation.

PRICAT (Price/Sales Catalogue) The PRICAT message enable the transmission of information regarding pricing and catalogue details for goods and services offered by a seller to a buyer. General usage * The Price/Sales Catalogue message indicates descriptive, logistic and pricing information by individual product. * Depending on the agreement between trading partners, the message might indicate only general information about the products, valid for all customers. * The message can be used to provide a specific customer with information regarding prices and special conditions. * Product information can be provided as a complete listing of all supplier's products or as an advance warning of particular changes. * The Price/Sales Catalogue message can also be used by suppliers to feed a central catalogue of products, making the information available to all interested parties.

If a publication has validation errors, there is a possibility to select scope when downloading. All products Select "All products" to download all products in the publication. A notification will show how many products will be exported. In this example 72/72 products will be exported. Valid products only Select "Valid products only" to download only the valid products in the publication. A notification will show how many products will be exported. In this example 0/72 products will be exported as all products have validation errors. The "Download" button will be grayed out. Invalid products only Select "Invalid products only" to download only the invalid products in the publication. A notification will show how many products will be exported. In this example 72/72 products will be exported as all products have validation errors.

This functionality could be useful for integrated suppliers if a buyer requires data the supplier cannot provide from within their business system. Note that if using a buyer specific template for uploading master data, that template will not be used when exporting data in Excel format. Btwentyfour´s original template will be used. Go to "Products" - "Publications". To start downloading a publication, click the three dotted icon on the row for that publication. Click "Download/Export to EDI". Or, for a published publication, click the "Download/Export to EDI" icon. A pop-up window appears. Click to select format. To download in Excel format, select "Excel Declarative...". Click "Download".

Go to "Products" - "Publications". To start publishing a publication, click the three dotted icon on the row for that publication. Click "Publish" in the pop-up menu. A pop-up window appears. Click the checkbox for the buyer. If publishing a publication uploaded to a GLN belonging to a group, all buyers in that group will be listed, and will be selectable via checkboxes. Click "Publish". A notification will show telling a publishing task has been scheduled. The publishing process will start and run in the background. A notification saying the publication has been published means that the publication has been published, or partially published, to the selected buyer(s). Note that if a publication has been validated with no errors, there will be no errors if publishing to the same buyer(s). If a publication has not been validated at first, there could still be validation errors in the publication, even though it says published. As long as one item has been published with no validation errors the publication will have a status as "Published". More information: Step by step guide from uploading to publishing master data.

Note that publications can be validated automatically after import if a setting called “Auto validate” is activated in the background. To activate this setting contact support@btwentyfour.com. To start validating a publication, go to "Products" - "Publications". Click the three dotted icon on the row for that publication. Click "Validate" in the pop-up menu. A pop-up window appears. Click the checkbox for the buyer. If validating a publication uploaded to a GLN belonging to a group, all buyers in that group will be listed, and will be selectable via checkboxes. The validation will run towards the selected buyer´s validation rules for PRICAT. Click "Validate". A notification will show telling the validation has been queued and will begin shortly. The validation process will start and run in the background. More information: Step by step guide from uploading to publishing master data. How to see that a publication has been validated with errors? How to see that a publication has been validated with no errors?