Master data: the shared language of the business

Two salespeople sell the same replacement filter. One calls it Filter A and the other calls it Blue Filter. Purchasing knows it by the supplier's reference, while the warehouse stores it under an internal code. All four descriptions might refer to one physical product, but a system cannot reliably combine them unless the business establishes a common identity.

Master data provides that identity. It describes the relatively stable things a business repeatedly works with: its customers, suppliers, items, warehouses, units, accounts, and commercial classifications. Transactions describe events involving those things. A customer record describes who the customer is; an invoice describes a particular amount billed to that customer.

Why consistency has an operational effect

A duplicate customer can split outstanding balances between two records. A duplicate item can make one record appear out of stock even when its duplicate holds the physical inventory. An incorrect unit conversion can turn a reasonable purchase quantity into an excessive commitment.

These are business problems, even when every individual document looks neatly completed. The information must be consistent across documents for totals, availability, and history to make sense.

In DNA, customer and supplier records provide reusable commercial information. Items are organised with categories and can use attributes and variants. Warehouses and bins describe location. Payment terms describe the agreed basis for billing or settlement. These records help transactions inherit a coherent starting point.

Identity, classification, and defaults

Identity answers which specific entity is involved. A customer code distinguishes a business from another business with a similar name. Classification answers what kind of entity it is. A customer group might distinguish wholesale from retail accounts, while an item category groups related products.

A default is a suggested starting value. A customer's usual payment terms can reduce repeated entry, but an individual contract may have a different agreement. A default therefore needs to be distinguished from evidence of what was agreed for a particular transaction.

These concepts solve different problems. Creating another customer record solely to represent a different payment arrangement can fragment the customer's history. Using an item category as a substitute for an individual item can lose the detail needed to fulfil an order.

A practical example

A distributor supplies safety gloves in medium and large sizes. Each carton contains 12 pairs. The product family is useful for reporting overall glove demand, but the size matters when fulfilling an order. A customer wanting 20 cartons of medium gloves cannot be satisfied with 20 cartons of large gloves merely because both belong to the same category.

DNA's category, attribute, variant, and unit concepts help express these distinctions. The category groups the family, the variant identifies the relevant combination, and the unit conversion explains that 20 cartons represent 240 pairs. Warehouse information then explains where those pairs are held.

The commercial price also needs a unit. USD 60 per carton and USD 60 per pair are radically different offers. Clear master data allows the document to communicate the intended arrangement.

An item also has a Track Inventory setting. This determines whether its quantity participates in stock control when the setting is available to the transaction. The item name or broad classification alone is not enough to determine its stock-check behavior. A product description and an operational setting serve different purposes.

Managing changes responsibly

Master data changes can influence future work. Changing a customer's usual terms does not mean an earlier signed agreement has changed. Renaming a product does not establish that old stock has become a different product. A responsible change distinguishes a correction to the description from a change in the underlying business identity.

Historical records matter when an entity stops being used. An inactive supplier may still have unpaid invoices. A discontinued item may still exist in the warehouse. Preventing new use and preserving past evidence are separate requirements.

The useful habit is to think about the downstream effect of a master record. Its quality influences quotations, purchasing, stock control, billing, and reporting long after it is first established.