Inventory Audits

AvanSaber’s inventory practice runs operational audits: point-in-time engagements where we review your inventory operations, systems, and data, then deliver a written report with findings and a prioritized roadmap.

This is the right shape when you suspect your inventory operations are not what they should be but are not sure exactly where the problems live, or when you want an honest outside read before committing to a transformation project.

When this fits

Inventory audits are the right shape when:

If you already know what the problem is and need it built or rebuilt, implementation is the better shape. If the problem is ongoing strategic ambiguity, advisory fits better than a one-time audit.

What we cover

Every audit examines four layers. The depth varies by engagement scope.

Operational layer. How does inventory actually flow through the business? We trace 5 to 10 representative SKUs from receipt through storage through pick to ship to invoice. We document the steps, the handoffs, the controls (or absence of controls), and the failure modes. We map the gap between the documented process and what people actually do.

System layer. What systems hold inventory data, and how do they communicate? ERP, WMS, OMS, accounting, ecommerce platforms, payment processors, 3PLs. We identify the source of truth, the sync patterns, the failure points, and the reconciliation gaps.

Data integrity layer. Does the system tell the truth? We sample inventory counts against physical counts, audit the reconciliation between subledger and GL, and assess data quality (duplicate SKUs, missing cost layers, orphaned inventory, ghost inventory, negative stock without explanation).

Process maturity layer. How well-controlled are the processes that govern inventory changes? Approvals on inventory adjustments, segregation of duties, cycle count discipline, period-end procedures, audit trail completeness.

Deliverables

Three artifacts at the end of every audit:

Written findings report. Typically 25 to 60 pages. Plain-language documentation of what we found, organized by the four layers above. Includes evidence (sample transactions, system screenshots where appropriate, reconciliation tables) and severity assessment per finding.

Prioritized roadmap. Recommendations sorted by impact and effort, with realistic estimates. We do not produce vendor-shaped roadmaps that recommend buying a specific tool. We produce operational roadmaps: do A first because it unlocks B; defer C until you have done A and B; D is wrong and stops adding cost the day you stop doing it.

Executive briefing. A 90-minute readout for your leadership team, walking through the major findings and the proposed roadmap. We answer questions, refine priorities, and align stakeholders on the next steps.

Optional add-on: vendor-evaluation support. If the audit surfaces a recommendation to evaluate or replace a vendor, we can run the evaluation as a follow-on engagement (or as an advisory retainer).

Typical audit shapes

A few representative examples from recent work:

Pre-acquisition due diligence audit. A private-equity firm asked us to audit the inventory operations of an acquisition target. Two-week engagement. We documented operational maturity, system gaps, working capital risk, and produced an integration risk assessment that informed the deal valuation.

Post-implementation health check. A mid-market manufacturer had implemented a new WMS 9 months prior and inventory accuracy was getting worse, not better. Three-week audit. We traced the problem to a sync pattern between the WMS and ERP that worked correctly under normal load but failed silently during high-volume receipts. Roadmap included an immediate sync-pattern fix and a longer-term reconciliation tooling investment.

Year-end inventory accuracy audit. A multi-warehouse distributor’s external auditor flagged an inventory accuracy concern that the operations team disputed. Four-week audit. We physically counted samples across all warehouses, reconciled against the system, and produced a documented finding that allocated the discrepancy to specific operational gaps (3 fixable, 1 systemic). The systemic finding became a multi-month implementation project we later delivered.

Multichannel ecommerce inventory audit. A 6-channel ecommerce seller had persistent oversells they could not eliminate. Three-week audit. We traced the problem to a combination of sync delay during channel-specific velocity spikes plus a bundle-decomposition rule that was decrementing components inconsistently across channels. Roadmap was specific and operational.

Engagement model

Fixed-fee pricing. Most audits are quoted as fixed fees against a defined scope. The scope is set during a short pre-audit scoping call (typically 60 minutes, no charge); the quoted fee includes all deliverables.

Timeline. 3 to 6 weeks from scope agreement to executive briefing. Compressed timelines (2 weeks) available for due-diligence contexts; extended timelines for complex multi-entity audits.

Confidentiality. Audit work is covered by mutual NDA before any document review. We do not publish or reference audit findings in our writing without explicit written permission.

Team composition. Audits are led by a senior practitioner (the same engineers and operators who run our implementation engagements), supported by domain specialists where the scope requires (for example, a data engineer for data-integrity-heavy audits).

What we don’t do

Honesty about scope:

How to start

Audits start with a short pre-audit scoping call. You describe the situation; we ask clarifying questions and propose an audit scope, timeline, and fixed fee. If you agree, we schedule the audit; if not, we part with no obligation.

Book a scoping call or describe your situation at [email protected].