If you’re managing inventory in spreadsheets and email, start here

Before you buy new software, stabilize the basics.

Start by standardizing part and vendor data. Then automate three flows:

1. Inventory transactions (receipts, issues, adjustments)
2. Reorder signals into purchasing
3. Daily/weekly reporting

The goal is a clean “system of record” plus automation that keeps quantities, costs, and reorder decisions accurate.

Who this is for

Ops leaders, plant managers, inventory controllers, and procurement teams who want fewer stockouts, fewer surprises, and less manual reporting.

The pattern we see across manufacturing

The teams we work with vary in size, but the problems look the same:

• Parts live in spreadsheets
• Purchasing lives in email
• Reorder decisions depend on tribal knowledge
• Reporting gets rebuilt every week

That leads to stockouts, expedite fees, and constant “Do we have it?” messages. This guide shows how to stabilize the workflow, then automate using tools you probably already have.

The pain points and what usually causes them

1) On-hand inventory you don’t trust

What it looks like:

• • On-hand numbers feel unreliable
  • “We have it somewhere” searches
  • Adjustments happen weeks later
  • Cycle counts don’t reconcile cleanly

What causes it:

• • Multiple files acting as “truth”
  • No consistent transaction log (receipt/issue/adjust)
  • Manual entry with no validation (wrong part, unit, location)

2) Reorder rules that don’t match demand

What it looks like:

• • Rush orders and expedite fees
  • Reorder rules in someone’s head
  • Reorder points don’t reflect lead time changes
  • Safety stock decisions vary by person

What causes it:

• • Lead times not tracked by part/vendor
  • No shared definition of min/max vs reorder point vs Kanban
  • No exception list (what needs review vs can auto-flow)

3) Supplier communication trapped in inboxes

What it looks like:

• • “Did we place that PO?” questions
  • Missing confirmations
  • Late shipments discovered too late
  • No consistent follow-up cadence

What causes it:

• • PO status not centralized
  • Confirmations not logged back to the system
  • No alerts when dates slip

4) Reporting that eats hours every week

What it looks like:

• • End-of-week copy/paste reporting
  • Manual matching of receipts, invoices, and usage
  • Inventory valuation questions take days to answer

What causes it:

• • Data pulled from multiple places with inconsistent part naming
  • No clear reporting level (by part, job, location, day)
  • No reconciliation workflow

A stack that usually works without a full rebuild

Excel

• • Best for: analysis, pivots, forecasting, variance exploration, scenario modeling
  • Not great for: being the system of record for live inventory transactions

Airtable (or another structured table layer)

• • Best for: parts/vendor master data, PO tracking, exceptions, approvals, role-based permissions

ERP / accounting system

• • Best for: financial truth, valuation rules, posting, formal purchasing/receiving (when already in place)

Automation tools (Make, Power Automate, Zapier)

• • Best for: connecting systems, alerts, approvals, sync jobs, audit logs

A practical build plan

Step 1: Standardize the parts master

Decide what fields are required and enforce them.

Minimum fields most teams need:

• • Part ID (unique)
  • Part name (consistent naming)
  • Unit of measure + conversions (if needed)
  • Preferred vendor + alternates
  • Lead time (by vendor if it varies)
  • MOQ / order multiples
  • Reorder rule (min/max or reorder point + safety stock)
  • Locations (stocking points)
  • Status (active/obsolete/restricted)

Deliverable: one controlled parts master (not five versions).

Step 2: Create a transaction log you can audit

This is the difference between a spreadsheet and a real inventory process.

Common transaction types:

• • Receipt
  • Issue to job / production
  • Transfer
  • Adjustment (with reason)
  • Scrap / write-off

Rules that prevent drift:

• • Every quantity change must be a transaction
  • Adjustments need a reason (and approval above a threshold)
  • Every transaction includes timestamp + user

Deliverable: one transaction table you can filter, summarize, and reconcile.

Step 3: Automate reorder signals into purchasing

Start with exceptions. Safer. Easier to adopt.

Typical flow:

• • If on-hand + on-order − allocated is below the reorder rule…
  • Create a “PO needed” record with suggested quantity
  • Route for approval if it breaks a rule (dollar limit, MOQ exception, etc.)
  • After approval, create the PO (ERP or tracker)
  • Send vendor email + request confirmation date
  • Log confirmation date back into the system

Deliverables:

• A consistent daily “Buy List”
• Less hunting, more exception review

Step 4: Automate reporting outputs

Start with the reports you build manually today.

Common set:

• • Stockout risk (next 7/14/30 days)
  • Shortage list by job/work order
  • Receipts vs expected (late shipments)
  • Adjustments by reason + approver
  • Usage variance (planned vs actual, if applicable)
  • Cycle count results + reconciliation status

Deliverables:

• • Scheduled reports to email/Teams/Slack
  • One leadership view + one ops working view

Governance that keeps it clean

Approvals

Use approvals where the risk is real: high-dollar POs, new vendors, large adjustments, obsolete parts.

Keep it lightweight: requester → approver is enough for most teams.

Reconciliation

Set a cadence and make it visible:

• Daily: receipts posted vs expected
• Weekly: top variances, negative inventory flags
• Monthly: cycle counts, valuation checks (as needed)

Audit trails

Track by default:

• Who changed reorder rules, and when
• Who approved adjustments, and why
• What numbers were used for each report run

Proof 

Case study example:

A manufacturer client tracked parts in multiple spreadsheets and emailed vendors manually. They standardized the parts master, added an auditable transaction log, and automated a daily reorder exception list into a purchasing approval workflow. Reporting moved from weekly manual assembly to scheduled outputs.

Results:

• 30–60% less time spent chasing inventory status
• 20–40% fewer stockouts by catching reorder risk earlier
• 2–6 hours/week saved on recurring inventory and purchasing reports

Templates you can copy into your process

Inventory exception queue (fields)

• Part
• Location
• On-hand
• On-order
• Allocated
• Reorder point / min
• Suggested qty
• Vendor
• Lead time
• Reason flag (stockout risk, demand spike, lead time change, negative inventory)
• Approval status + approver
• Notes

Adjustment control (fields)

• Part + location
• Qty before / qty after
• Adjustment qty
• Reason code
• Evidence link (count sheet, photo, ticket)
• Approval required? (Y/N)
• Approver + timestamp