Skip to content

STOCK DATA AUDIT · INCLUDED WITH BOTH PRODUCTS

Find the duplicate SKUs and broken pack sizes hiding in your ERP.

Weeva reads your catalogue the way it reads orders, and shows you where the data will trip an order: duplicates, mis-calibrated units of measure, inconsistent pack sizes, missing prices. Each finding becomes a task with an owner.

Book a 30-minute demoSee a sample audit
Illustrative example: a stock data audit of fictional master data, listing duplicate SKUs, mis-calibrated units of measure and inconsistent pack sizes as fix tasks.

Included with

Related features

What is a stock data audit?

A stock data audit examines the catalogue in your ERP (the item master, in most ERPs) for defects that cause wrong orders and wrong stock: duplicate SKUs for the same product, units of measure that do not match how the product is sold, pack sizes recorded differently in different places, missing or zero prices, and codes that are never used. Weeva runs the audit continuously and turns each finding into an assignable task.

Why does clean stock data matter for order automation?

Every order matches against your catalogue. So does every mistake.

  • Duplicate SKUs

    A duplicate SKU splits your stock and your sales history in two. Half the orders land on one code, half on the other.

  • Wrong units of measure

    A wrong unit of measure ships twelve when one was ordered, or one when twelve were.

  • Inconsistent pack sizes

    An inconsistent pack size breaks pricing in one direction and stock in the other.

See how it works

Every finding, counted, typed and owned.

Illustrative example: a stock data audit of fictional master data, listing duplicate SKUs, mis-calibrated units of measure and inconsistent pack sizes as fix tasks.

The figures shown are sample data from a fictional distributor.

What does a stock data audit look for?

Eight kinds of defect, each with a fix.

Stock data findings, how Weeva detects them and the suggested fix

  • Duplicate SKU

    How Weeva detects it
    Same product under two codes, by description, barcode and ordering pattern
    Suggested fix
    Merge, redirect the retired code

  • Near-duplicate description

    How Weeva detects it
    Descriptions that differ only by spacing, case or abbreviation
    Suggested fix
    Standardise the description

  • Unit of measure mismatch

    How Weeva detects it
    Catalogue says Each, customers consistently order Case
    Suggested fix
    Set the selling unit, add the pack

  • Pack size inconsistency

    How Weeva detects it
    12 in the catalogue, 24 on recent deliveries or orders
    Suggested fix
    Confirm the pack, update the catalogue

  • Missing or zero price

    How Weeva detects it
    No price on an active SKU or on a customer's list
    Suggested fix
    Add the price or retire the SKU

  • Price list gaps

    How Weeva detects it
    A customer's list lacks products they order
    Suggested fix
    Extend the list

  • Orphaned code

    How Weeva detects it
    Never ordered, never received, never stocked
    Suggested fix
    Retire

  • Inactive but sellable

    How Weeva detects it
    Discontinued items still available to order
    Suggested fix
    Deactivate

Findings become tasks, not a spreadsheet nobody opens.

  • Assign each finding to a person
  • Mark fixed in Weeva or in the ERP
  • Verified against the ERP on the next sync
  • History kept for audit
Illustrative example:

Task F-1042: Unit of measure mismatch on WTR-1L-STL-6, Still water 1L, pack of 6. Catalogue Each, ordered as Pack on 14 orders. Owner Naledi Khumalo, Finance. Status In review. Suggested fix: Set the selling unit to Pack of 6 and keep Each as the stock unit.

  1. 22 Sep 06:00, Weeva: Found on the Sage 200 catalogue sync
  2. 22 Sep 08:14, Dev Naidoo: Assigned to Naledi Khumalo
  3. 22 Sep 10:37, Naledi Khumalo: Selling unit changed in Sage 200: Each to Pack (6)
  4. Next sync, Weeva: Check the change against the ERP

Cleaner data, fewer reviews.

Most order review reasons trace back to the catalogue. Fix the data and the review queue shrinks. The learning loop on orders and the audit on stock data feed each other.

See the learning loop

Reads the system you already run.

The audit reads your catalogue, units of measure, pack sizes and price lists from your ERP by API. It proposes fixes; it does not write to your catalogue unless a person on your team applies one.

See all integrations

Plus any other cloud ERP or accounting package, through an adapter on the same connector framework.

Or from a CSV or Excel export of your catalogue, before any connector is live.

What people ask about the audit.

Which ERPs can it audit?

Any system Weeva can read a catalogue from, which includes every integration listed on the integrations page and any CSV or Excel export. The audit reads the same catalogue your orders are matched against, so what it finds is what trips your order desk: duplicates, units, packs and prices.

Does it change data in my ERP?

No. It finds and proposes. Fixes are made by your team, in Weeva where the connector supports it or directly in the ERP, and verified on the next sync. Nothing in your catalogue changes without a person on your team deciding it should, and every decision is recorded.

How often does it run?

Continuously, on every catalogue sync, with a summary per week. A defect introduced on Tuesday shows up on the next sync rather than at the next year-end stock take, and a fix your team makes is checked against the ERP on the sync after that.

Can we start with an export instead of a connection?

Yes. Upload a CSV or Excel export of your catalogue and the audit runs on that. It is a practical way to see the findings before any integration work starts. When the connector is live, the audit moves to running on every catalogue sync.

What counts as a duplicate?

Two codes that describe the same product, judged by description, barcode, pack and how customers order them. Weeva shows its reasoning so you can disagree. Each suggested pair is a proposal: a person on your team confirms the merge or dismisses it, and nothing changes in the ERP until they do.

Is Stock Data Audit included with both products?

Yes. Stock Data Audit is a feature included with Sales Order Automation and Goods Receiving Automation. The catalogue that orders and delivery notes are matched against is the same catalogue being audited, so every fix you make shows up as fewer order and receiving reviews.

See Weeva on your own orders.

Pick a time that suits you. Bring three sample orders, including one your team finds awkward, and we'll run them through extraction and catalogue matching live. No obligation.

Book a 30-minute demoEmail us