---
name: supplier-price-list-normalization
description: Converts supplier price lists into the wholesale company’s item and pricing schema, normalizing identifiers, units, packs, tiers, and changes while isolating exceptions. Use for supplier onboarding, annual price updates, catalog maintenance, and purchasing data review.
license: Apache-2.0
metadata:
  adlass.categories: "data-tables/cleanup-normalization, data-tables/data-quality"
  adlass.industries: "wholesale"
  adlass.tags: "price-list, normalization, wholesale, suppliers, purchasing"
  adlass.adaptation: "mapping"
  adlass.source: "n8n:W-01"
  adlass.version: "1"
---

# Supplier price-list normalization

## Purpose

Create a usable, auditable price table without losing supplier terms or masking unmapped products.

## Scope

Supplier price files, item masters, pack and unit definitions, tier prices, effective dates, and prior lists. **Excluded:** price negotiation, purchase-order creation, and automatic master-data publication.

## Data basis

- Current and prior supplier price lists, item master, supplier agreements, unit dictionary, mapping rules, and exception policy.
- The fixed records, tables, or folders in the skill scope that hold the relevant history or schema.

## Result

A normalized price sheet, change report, and exception sheet for unmapped, conflicting, or anomalous records.

## Quality criteria

- Every normalized row has a supplier identifier, internal identifier or explicit unmapped status, unit basis, and effective date.
- Pack and unit conversions are reproducible.
- Tier prices retain thresholds and conditions.
- Changes reconcile to the prior list or are marked new.
- Exceptions are not silently dropped or overwritten.

## Instructions

Map by supplier and item identifiers before using descriptions or UPC-like values. Preserve the source price and terms alongside normalized values. Normalize units only through the approved dictionary. Compare effective dates before labeling a price as changed. Flag negative, zero, outlier, duplicate, and conflicting values according to the exception policy.

## Adapt before use

Keep the source trail close to every conclusion and preserve the difference between a source fact, a calculated value, an assumption, and a recommendation. Use stable identifiers across the document and sheet so a reviewer can move from a summary statement to the underlying row and source. Prefer a complete, transparent partial result over a confident answer built on missing evidence.

- Add the item master, supplier mappings, unit dictionary, and price schema.
- Define effective-date and supersession rules.
- Set outlier thresholds and duplicate handling.
- Specify which exceptions block publication or require review.