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.