Product data quality
Product data quality describes how well information fits its intended use. Complete fields can still describe the wrong goods.
Product data quality describes how suitable product information is for a particular use. It includes correct values and sufficiently complete details, as well as consistency between descriptions, attributes and assignments.
In a hypothetical example, a bottle's description says 750 ml while its contents field says 500 ml. Both fields are filled in. The contradiction still exists and can affect selection or ordering. A reliable product reference is needed to establish which value is correct.
A completeness score alone therefore does not prove business-level accuracy. Required information also depends on the product and intended channel. For important fields, record where the confirmed value comes from and who may correct it. A new shop interface cannot make this decision by itself.
Sources
Related terms
- Product variantA product variant is a particular version of a product. Its attributes must remain consistent across selection, pricing, stock and ordering.
- Master dataMaster data describes core business entities such as customers or products. It is reused across processes and can still change over time.
- Delivery capabilityDelivery capability describes whether a specific request can be fulfilled. A stock value alone does not fully answer questions of quantity, destination and time.
- Order historyOrder history shows previous orders within an agreed account scope. Old prices, current availability and current processing remain separate information.
- Dealer portalA dealer portal gives affiliated dealers digital access to agreed information and workflows. Its scope and company assignment need to be clear.
- Billing addressThe billing address is a separate address in an order or invoicing process. It must not be accidentally swapped with the delivery address.
Articles on this topic
E-Commerce with ASES
Online shops, marketplaces and B2B portals