How to Clean Up the Item Master in NetSuite

The item master in NetSuite is supposed to be the single record of what you sell. In practice, after a few years and a few supplier onboardings, it’s often three records of what you sell, each slightly different, plus a fourth that someone created during a rush order and never reconciled. Inventory counts look wrong because the system is splitting one product’s stock across multiple item records. Reports double-count. A sales rep quotes from one item record while fulfillment ships against another.

This is the predictable result of an item master that grew by manual entry, supplier-by-supplier, without anything resolving identity before a new item record gets created.

How duplicates actually get into NetSuite

It’s rarely one dramatic mistake. It’s the accumulation of small, reasonable-seeming decisions:

• A new supplier’s price list gets imported, and nobody checks whether half the products are already in the system under the previous supplier’s part numbers.
• Someone creates an item manually for a rush order rather than searching properly first, because searching NetSuite’s item list for a fuzzy match is slow and unreliable.
• A unit-of-measure mismatch — one item entered in each, the conceptually same item entered in case-of-12 — looks like two different products to anyone scanning the list.
• An acquisition or a catalog merge brings in a second company’s item master, with its own internal SKUs, alongside yours.

Each of these is individually minor. Compounded over a few years across a few thousand SKUs, they produce an item master nobody fully trusts.

What actually needs to happen before cleanup sticks

A one-time deduplication pass — exporting the item list, sorting, manually merging obvious duplicates — buys temporary relief. It doesn’t last, because nothing changed about how new items get created. The next supplier onboarding reintroduces the same problem.

The durable fix has two parts:

1. 1
   Resolve existing duplicates with confidence, not guesswork

   Match items by exact identifiers — manufacturer part number, GTIN, or other authoritative keys — where available, and by normalized attributes such as description, specs, and unit of measure where they aren’t. Merge what’s confidently the same item, flag the ambiguous cases for a human to confirm, and preserve a record of what merged into what so nothing breaks downstream in open orders or historical reports.

2. 2
   Put identity resolution in front of new item creation, not after it

   When a new supplier feed arrives, it should be checked against the existing item master before anything new gets created — not cleaned up retroactively six months later. This is the difference between a deduplication project that needs repeating annually and one that actually holds.

What to check in your item master right now

Keeping it clean after the fix

Once the item master is resolved, the goal is to stop it from drifting again. That means every new supplier feed or manual entry gets checked against the existing item master before writing a new record into NetSuite — not as an annual cleanup project, but as a standing step in supplier onboarding. The same applies on the other side of NetSuite: keeping the item master in sync with what’s published on your ecommerce storefront, covered in the ERP-to-ecommerce data gap.

Related reading

FAQ