Inventory & costs

Commercial Product Data Master

A pack changing from twelve to ten pieces can distort stock and cost. Control item identity, units, batches and translations before approving data changes.

What you will take away

Pack contents can change quantity and unit cost without a supplier price increase.

Separate item identity, specifications, packaging levels and batch data.

Review historical transaction effects rather than automatically overwriting past conversions.

The supplier's price has not increased, yet the cost per piece has risen. After a lengthy review, someone discovers that the new pack contains ten pieces rather than twelve, while the conversion factor in the system remains unchanged. The error did not begin with an accounting entry. It began with a small product-data change that nobody noticed.

A product master is more than a searchable list of names. It connects commercial descriptions with purchasing, stocking and selling units. When those languages differ without explicit links, receipts can carry incorrect quantities, displayed prices can mislead and reported margins can fail to describe what was actually sold.

The twelve-piece pack test

In a hypothetical example, a business buys 50 packs at SAR 120 per pack, excluding taxes and additional costs. With twelve pieces per pack, the purchase contains 600 pieces costing SAR 10 each. If the new pack contains ten pieces at the same pack price, the actual quantity is 500 pieces and the cost is SAR 12 each.

Keeping the old conversion factor creates 100 nonexistent pieces and understates the apparent unit cost by SAR 2. An employee may later try to resolve the discrepancy with a stock adjustment, but that alone will not prevent the next receipt from repeating it. Start by identifying the pack configuration applicable to each delivery, then review affected transactions through approved procedures. Do not overwrite historical conversions indiscriminately.

Four layers that do not belong in one name field

LayerExample informationWhy distinguish it?
Internal item identityStable tracking codeMarketing names can change without changing identity
Product specificationsSize, colour and capacityDifferences may require separate stock identities
Packaging levelPiece, pack and cartonEach level has quantities, conversions and potentially its own code
Batch informationLot reference and applicable datesThese may differ between deliveries of the same item

The objective is not to create dozens of unused fields. Begin with information that changes receiving, selling or traceability decisions. If a property cannot safely be inferred from the name, do not bury it in free text that varies between employees. Conversely, there is no need to create a new product for every lot where the system appropriately supports batch tracking within the same item.

A supplier spreadsheet is not an unquestionable authority

Importing a product file saves data-entry time, but it can also import the supplier's mistakes. Compare a sample with the packaging or product documentation, paying particular attention to price units, quantity units and similar-looking codes. A code identifying a carton should not sell a single piece without an explicit mapping.

Ministry of Commerce references emphasise the truthfulness of commercial product information, including applicable characteristics such as quantity, dimensions and origin. Its unit-pricing guidance also illustrates the value of comparison on a consistent basis. These principles explain why sound data matters; product-specific labelling requirements still need assessment against the relevant rules and competent authority's requirements. A well-designed internal record does not replace that assessment.

When translating between Arabic and English, check meaning rather than matching words alone. Volume must not become weight, and qualifications that alter the product's nature must not disappear. Where practical, keep units and numeric characteristics in shared structured fields, with a suitable description for each language. Editing a marketing translation should not unintentionally alter an operational specification.

Small edit, significant questions

Before changing information already used in transactions, ask whether the change corrects an error, represents a new product or applies only to later deliveries. Each calls for a different response. Clarifying a name may be straightforward; changing the base unit or merging two codes with existing balances requires a wider review of movements and open documents.

Define who requests changes and who approves attributes affecting cost and stock. Preserve the previous value and the reason for amendment. Do not allow a marketing campaign to redefine pack size on earlier orders. An item with unresolved information can be held from use until the uncertainty is resolved, instead of filling fields with guesses merely to complete entry.

Start improvements with products repeatedly associated with receipt discrepancies, returns and unexplained price adjustments. Reviewing a limited number of their records will often reveal a shared packaging or conversion problem. Better product data should reduce these exceptions; counting populated fields alone will not demonstrate that improvement.

Sources & further reading

Visit the original source to explore the concept and its wider context.

General educational content. Appropriate treatment depends on your business and accounting policies; consult your accounting professional when applying it to business records.