Back to library

Supplier price-list normalization

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.

by adlass TemplatesVersion 1Uses adlass toolsUniversal

Published Aug 21, 2026 · Updated Aug 26, 2026

Helpful · 0View raw SKILL.md

Requirements

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.

Skill document

The full SKILL.md your agent reads and follows.

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.

Related skills

  • Sync a spreadsheet into a record type

    Loads an uploaded spreadsheet into a record type of the workspace with the bulk sync tool, previewing the changes before writing. Use for master data imports, periodic refreshes of a table, or migrating a list from Excel into records.

  • Anomaly variance explanation

    Explains material changes in a business metric by decomposing period, volume, price, mix, and data-quality effects, then ranks evidence-backed causes in a cited analysis sheet and management memo. Use for KPI variance reviews, monthly business reviews, forecast misses, anomaly investigation, and driver analysis.

  • Data migration field mapping

    Maps source-system fields to a target data model for migration, documenting transformations, requiredness, value translations, identifiers, validation rules, and unresolved collisions. Use for CRM migrations, ERP imports, warehouse loads, application replacement, and controlled spreadsheet-to-system field mapping.

  • Dataset Quality Assessment

    Dataset Quality Assessment converts table schema, column types, null policy, primary and foreign keys into profiling report and defect register with field metrics, duplicate groups, invalid values, orphan keys, temporal gaps, and severity, with cited evidence, explicit rules, and unresolved exceptions. Use for dataset quality assessment, recurring review, and decision preparation.