Not for this check, because it needs no costs, descriptions or customer data: SKU codes can be replaced with your own anonymous IDs. If your policy requires one anyway, a mutual NDA is signed before anything is sent.

Our WMS exports look different. Will it still work?

Almost certainly. The test needs five fields: SKU, case pack, cases received, units posted, and either a received-count or an adjustment log. Column names don't matter, and a CSV or Excel file straight from the report screen is fine.

Is this a sales trap?

It's a real diagnostic with a real output, and you keep it whether or not you buy anything. You'll be offered one follow-up call to walk through the result. There's no email sequence, and saying no ends it.

Why is it limited to five a month?

Every check is read by the same analyst who runs the paid audits. The limit keeps turnaround at three business days.

Free diagnostic · 3 business days

Free case-pack check:
find the pack fields your WMS has wrong

A wrong case pack creates the same variance on every receipt of that item, and counts correct it one adjustment at a time. This check finds those fields from your own receipt history and returns the list. It's free because it shows exactly how a WMSAudit engagement works.

Updated 19 September 2026
Written by WMSAudit
A Ravenspire LLC company
Free · one export · no call required

Short answer

Send two exports: your item master and about 90 days of receipts, plus the adjustment log if you can. The receipt-ratio test looks for SKUs whose variance per case is the same whole number receipt after receipt. That's the signature of a wrong pack field, not a counting error. Within three business days you get the flagged SKUs, the evidence for each, and the units involved.

What you send

Item master: SKU, case pack, and inner pack if you have one. Nothing else is needed: no descriptions and no costs.
Receipts, about 90 days: SKU, vendor, date, cases received and units posted. Include the received or counted quantity if your receiving process records one.
Adjustments (optional, strongly helps): SKU, date, quantity and reason code, same period. Many pack errors never show at receiving. They show as counts correcting the same item in the same direction.

Keeping it safe. Replace SKU codes with your own IDs if you prefer; the test only needs them to be consistent across files. Send the files as a password-protected zip and give the password by phone, or share a link from your own file system. Files are deleted when the result is delivered, unless you ask otherwise.

What you get back, within three business days

The flagged SKUs, each with the test that caught it and the evidence: for example, "6 receipts, −2 units per case on all 6".
The likely correct pack where the data implies one, to confirm against a physical case before changing anything.
The units involved over the period you sent, and an indicative value if you give an average unit cost.
Structural flags: case packs of 1 on items received in cases, inner pack equal to case pack, and inner packs that don't divide the case.

It comes as a short summary plus a CSV you can sort and hand straight to whoever owns the item master.

How the test works

A counting mistake is random: over one receipt, short another, a different amount each time. A wrong pack field isn't. If the item master says 14 and the vendor ships 12, every case posts two units that never arrived, so the variance divided by cases received comes out at the same whole number on every receipt. That constant is the fingerprint.

When receipts aren't counted, the same fingerprint appears later in the adjustment log: the item gets corrected in the same direction again and again, and the corrections add up to a whole number of units per case received. The method is explained in more depth in item master audit (test 7) and unit-of-measure errors.

What it is and isn't

It is one test from the full audit, run properly on your own data. It isn't the audit: it doesn't look at locations, putaway, replenishment, counting design, adjustments by user, or interfaces, and it doesn't price findings against your costs. If the check turns up a pattern worth chasing, the full WMS audit is the next step. If it turns up nothing, that's a useful answer too.

Limited to five checks a month so each one is read properly.

Request the check

Fill this in and you'll get a reply with where to send the files. Don't attach data to the form.

Questions

Do we need an NDA?: Not for this check, because it needs no costs, descriptions or customer data: SKU codes can be replaced with your own anonymous IDs. If your policy requires one anyway, a mutual NDA is signed before anything is sent.
Our WMS exports look different. Will it still work?: Almost certainly. The test needs five fields: SKU, case pack, cases received, units posted, and either a received-count or an adjustment log. Column names don't matter, and a CSV or Excel file straight from the report screen is fine.
Is this a sales trap?: It's a real diagnostic with a real output, and you keep it whether or not you buy anything. You'll be offered one follow-up call to walk through the result. There's no email sequence, and saying no ends it.
Why is it limited to five a month?: Every check is read by the same analyst who runs the paid audits. The limit keeps turnaround at three business days.