SKU Cleanup and Item Master Setup Checklist
ITEM MASTER WORKING CHECKLIST
Record every cleanup decision before changing a live code
This checklist turns item-master cleanup into a controlled work pack. It does not replace the detailed guide; it provides the fields, status, evidence and acceptance steps needed to execute a reviewed batch.
01 – PROFILE
Inventory the records
Extract identity, status, units, quantity, value, supplier, channel, barcode and transaction use for every candidate.
02 – DECIDE
Approve the target record
Keep, merge, split, rename, inactivate or map only after checking units, variants, history and open documents.
03 – TEST
Prove the migration
Validate labels, search, imports, receiving, selling, transfers, returns and finance reconciliation before release.
Complete the checklist for one reviewed batch
Choose twenty to fifty difficult items, assign owners and evidence, approve the cross-reference and test every connected transaction before wider rollout.
This SKU cleanup checklist is an execution tool for a controlled item-master batch. Use the separate Item Master Data Cleanup Guide for detailed principles. Here, the objective is to capture the source record, defect, decision, mapping, evidence, test and approval so changes can be reproduced and reversed where necessary.
The SKU cleanup service supports implementation, while the SKU naming guide helps define future codes. Do not change live SKUs directly in a spreadsheet without checking transactions and integrations.
Worksheet 1: record profile
| Field | Record | Required evidence |
|---|---|---|
| Internal ID | Immutable system key | Source export |
| SKU and aliases | Current and legacy codes | Labels, channels and history |
| Product and variant | Family plus differentiating attributes | Approved product source |
| Units | Base, purchase, sales and packs | Verified conversions |
| Status | Active, hold, discontinued or replacement | Owner decision |
| Quantity and value | By location and cut-off | Stock and valuation reports |
| Usage | Open orders, receipts, transfers and production | Transaction search |
Worksheet 2: defect classification
- Duplicate records for the same purchasable item
- One code reused for unlike products
- Missing or invalid unit conversion
- Variant attribute embedded only in description
- Supplier or channel code not mapped
- Inactive item with stock or open transactions
- Barcode, tax or account inconsistency
- Unverified compatibility or replacement relationship
Worksheet 3: target decision
| Decision | Minimum check |
|---|---|
| Keep | Identity and fields are correct |
| Merge | Same item, variant and unit; history and stock can be reconciled |
| Split | One record incorrectly represents multiple variants or packs |
| Rename | Label improves without breaking identity or mappings |
| Inactivate | No stock, open dependency or required service obligation |
| Replace | Approved successor and effective relationship exist |
Never merge solely because names look similar. Check physical item, unit, pack, tax, costing, tracking, compatibility and transaction use. Preserve a cross-reference from every retired code to the approved target.
Worksheet 4: field standard
Define code format, product name, variant attributes, base unit, purchase and sales units, barcode type, supplier mapping, category, tax, accounts, status, replacement and required evidence. GS1 General Specifications provide identification rules where GS1 keys and barcodes apply; do not invent or reuse identifiers outside the relevant rules.
Worksheet 5: migration sequence
- Back up source records, balances, mappings and open documents.
- Freeze or control new item creation for the batch.
- Load reference data and target items in dependency order.
- Map suppliers, ecommerce, POS, warehouse and accounting together.
- Reconcile opening quantity and value at the cut-off.
- Retain rejected rows with a reason; never drop them silently.
Microsoft Business Central documents configuration packages and item units of measure. Destination templates and required columns must remain intact. Each system has its own import behaviour; validate rather than assuming a successful upload means the records are usable.
Worksheet 6: transaction test
| Scenario | Acceptance |
|---|---|
| Search and scan | New and legacy identifiers find the intended item |
| Purchase and receive | Supplier item, unit, cost and quantity are correct |
| Transfer | Same identity and unit persist across locations |
| Sell and return | Channel mapping, tax, quantity and refund link correctly |
| Count | Physical item and system record reconcile |
| Finance | Inventory value and control accounts reconcile |
Approval pack
The batch pack contains source extract, defect register, approved targets, transformation rules, cross-reference, import result, rejected rows, quantity and value reconciliation, transaction tests, owner approvals and rollback steps. Record release date and users informed. Monitor duplicate creation, failed scans, unmapped orders and stock variance after release.
Worksheet 7: post-release monitoring
| Signal | Owner action |
|---|---|
| New duplicate | Stop creation path and map the source |
| Legacy code not found | Repair alias, label or channel mapping |
| Unit variance | Quarantine affected transactions and verify conversion |
| Import rejection | Correct the source rule and re-run only failed rows |
| Stock or value difference | Reconcile to cut-off evidence before adjustment |
| User workaround | Review whether training or target design is wrong |
Define a monitoring period and a named close decision. The batch is complete when normal and exception transactions work, quantities and values reconcile, rejected rows have owners, users can find the correct item and no critical downstream mapping remains open. A successful import message alone is not acceptance.
Worksheet 8: sign-off ownership
Name the owner who approves identity, units, valuation mapping, channel aliases and opening quantities. Record each approval against the reviewed file version and cut-off. If any owner cannot verify their area, keep the affected items quarantined rather than treating silence as acceptance. This makes the final release decision traceable and prevents unresolved data questions from becoming live stock errors.
Worked checklist row
Two active SKUs appear to describe the same twelve-pack. The profile shows one record uses eaches and the other cases, both have open purchase orders and one is mapped to the online store. The team does not merge them immediately. It verifies the pack conversion, chooses an each-based target, maps the case as a purchase unit, updates the channel and supplier aliases, tests open orders and reconciles stock value. Both old codes remain in the cross-reference, and the duplicate creation rule is fixed.
Sources checked
- GS1: General Specifications
- Microsoft Learn: Set up item units of measure
- Microsoft Learn: Import business data
Reviewed by
Mitrend Digital editorial team
2026-07-17
Evidence used for this page
Reviewed against GS1 General Specifications and current Microsoft Business Central item-unit and import documentation. Provides an original in-page cleanup workbook and acceptance checklist distinct from the item-master guide.
Turn the guide into a practical next step
This resource provides general implementation guidance. Verify platform settings, tax, legal, payment and operational requirements against the current business context before making a live change.