Your Inventory Is Lying to You: Available, Committed, Damaged, and Work in Progress

The shelf holds eighty jars, so accepting a sixty-unit order feels safe. But twenty are already committed, eight are on quality hold, six are damaged, twelve belong to unfinished kits, and the count includes a delivery that has not arrived. The business does not have eighty available jars. It has a story created by collapsing different states into one number.

Inventory is not only a quantity; it is a quantity with status, location, identity, and time. When those dimensions disappear, purchasing arrives late, sales promise unavailable stock, and production consumes components reserved for another job.

The fix is not constant counting. It is a small state model that mirrors the decisions the business actually makes.

The real-world pattern

A soap studio's spreadsheet reports 240 finished bars. An event planner orders 180. Packing discovers that 60 are curing, 24 are wholesale allocations, and 18 have damaged cartons. The maker rush-produces, shortens normal recovery time, and pays expedited freight. After separating available, committed, work in progress, hold, damaged, and inbound states, the same shelf supports accurate promises without more total stock.

The practical playbook

Define available precisely

Available inventory is usable, released, uncommitted stock in the correct location. It excludes future receipts, unfinished goods, holds, and quantities already promised.

Put it to work: Write the formula and use it consistently in catalog, order, and production decisions.

Reserve commitments when promises are made

Paid orders, approved production, wholesale allocations, replacements, and samples may reduce what can be offered even before physical movement occurs.

Put it to work: Choose the commitment event and release rule so abandoned drafts do not hold stock forever.

Make work in progress visible

Materials issued to a batch have changed state but have not become sellable output. WIP needs batch identity, location, planned completion, and status.

Put it to work: Limit concurrent WIP and reconcile actual good output before increasing finished stock.

Separate hold from damage

Quality hold means disposition is undecided; damaged or rejected stock has a defined restriction. Combining them hides investigation and invites accidental release.

Put it to work: Use clear physical segregation and authorized release, rework, return, or disposal decisions.

Treat inbound as a date and confidence

A purchase order is not usable stock. Supplier confirmation, transit, receiving, inspection, and release all affect availability.

Put it to work: Set reorder triggers using current available stock and realistic lead time with the reorder-point calculator.

What to watch

State changes must come from real events. Avoid manual totals that can be edited without a movement record. Count critical items cyclically, investigate discrepancies, and preserve lot or expiry identity where safety, traceability, quality, or customer obligations require it.

The number that keeps this honest

Track inventory accuracy by state and the number of promises made against unavailable stock. A perfect total count with incorrect commitments is still operationally wrong.

Put the lesson to work without rebuilding everything

Choose one current product and one recent operating cycle. Gather the source evidence before changing the system: purchase records, actual material quantities, sellable yield, hands-on time, order history, refunds, defects, customer questions, and the cash that moved. Estimates are acceptable when clearly labeled, but replace the highest-impact estimate first. A small maker does not need perfect data; the business needs numbers reliable enough to support the next decision.

Write the decision in plain language. “Improve inventory” is a project with no finish line. “Set a reorder trigger for the vessel that can stop our bestseller before Friday” can be completed and tested. Name the product, owner, trigger, action, and review date. Use a checklist or spreadsheet if that is sufficient. Add software only when the same information must stay connected across orders, materials, formulas, production, purchasing, and more than one person.

Run a seven-day evidence sprint

On day one, document the current method without defending it. On day two, calculate the baseline result. On day three, identify the earliest point where information becomes uncertain or work begins to wait. On days four and five, make the smallest useful control: a specification, decision rule, capacity limit, cost field, status, template, or quality check. On day six, run it through a real order or representative batch. On day seven, compare the result and decide whether to keep, revise, or remove the control.

The sprint should answer one question, not digitize the company. Record unintended consequences. A faster packout that increases damage is not an improvement. A lower material price that demands too much cash or produces inconsistent batches is not automatically a saving. A popular offer that requires unpaid founder labor is not automatically a winner. Look at the entire promise from purchasing through customer acceptance.

Keep a decision-grade scorecard

Most topics in this guide can be monitored with a short weekly scorecard:

• demand: qualified inquiries, orders, units, conversion, and repeat behavior;
• economics: net revenue, sellable unit cost, contribution, and contribution per constrained hour;
• delivery: promised versus actual completion and the age of open work;
• quality: first-pass yield, defects, rework, replacements, and the reason for each exception;
• inventory: available, committed, held, incoming, and days of practical coverage;
• cash: money committed before delivery, expected receipts, and obligations that are not spendable profit.

Not every business needs every measure. Choose the few that can change an action this week. Define each measure so the number cannot quietly change meaning. Compare normal cycles rather than a launch-day peak with a quiet Tuesday. Trends become useful only when the underlying definitions remain stable.

Build a rule for the tired version of you

A useful operating rule still works when the founder is busy. Write it as an if-then statement: if available stock reaches the reorder point, create the purchase decision; if requested customization exceeds the included revision, pause and re-quote; if practical capacity exceeds the agreed threshold, offer a later window; if a critical quality check fails, hold the affected work and investigate before release.

Test the rule against a recent surprise. Would it have prevented the late order, weak margin, shortage, or confusing customer exchange? If not, make the trigger more specific. If it creates ceremony around low-risk work, make it lighter. Good systems are not collections of forms. They make the correct action easier to recognize at the moment it matters.

Know when the system is ready to grow

Expansion should be earned by evidence: repeated full-price demand, a complete cost that pays sustainable labor, stable quality, a funded replenishment cycle, and a process that does not require emergency intervention every time. Before adding products, channels, equipment, or staff, name the constraint the investment will relieve and the result that will prove it worked.

Also define a stop or revision rule. Decide the maximum cash, time, defect rate, or delivery risk you will accept before pausing. This does not make the business less ambitious. It protects the resources required for the next good experiment. A clear no is often the system that preserves a better yes.

Questions for the next operating review

Before closing the review, ask whether the current offer and the current process describe the same promise. Marketing may still show an old package, quantity, lead time, option, or result after production has changed. Purchasing may use a new component that has not reached the specification. A customer-service reply may create an exception the schedule never received. Walk one recent order from the page the customer saw through the materials, batch, inspection, packout, delivery, and payment. Correct the earliest mismatch rather than adding another downstream reminder.

Then test the decision under three conditions: normal demand, a credible peak, and a disruption. The peak is not an imaginary viral month; it is the largest scenario supported by an event, wholesale conversation, seasonal history, preorder count, or campaign plan. The disruption should reflect a real vulnerability such as a long-lead package, unavailable founder skill, lower yield, carrier delay, or rejected material. Decide in advance which quantity, date, substitute, allocation, or communication rule changes in each condition.

Finally, review the human load. Count the steps that require memory, private messages, repeated copying, after-hours rescue, or one person's approval. Decide which should be removed, standardized, delegated, or made visible. Do not automate an unsafe or unclear decision merely because it repeats. Establish the rule and evidence first, then use automation to carry reliable information between steps.

Before the next cycle begins, make the change observable. Save the old baseline, the new rule, the person responsible, and the date when the team will review the outcome. Tell affected customers or partners when the change alters a promise, lead time, quantity, specification, or price. During the cycle, capture exceptions without treating every exception as a reason to abandon the rule. At review time, separate normal variation from a recurring failure. Keep the change when it improves the intended result without moving unacceptable cost or risk somewhere else. Revise it when the direction is right but the trigger, threshold, or instruction is weak. Remove it when it adds work without improving a decision. This simple record creates a reusable operating memory and gives future teammates the reason behind the process, not only the latest version of a checklist.

The review is complete when it produces an owner, action, and date. Keep a short record of the decision and the result after the next cycle. That history prevents the business from reopening the same debate every month and turns ordinary operations into a durable body of knowledge. Share the rule with everyone affected, confirm that they can follow it with the information available, and revise any instruction that depends on unspoken founder knowledge.

The bottom line

The purpose of operations is not to make a small business feel corporate. It is to protect the product, the customer, the cash, and the people doing the work. Choose one action from this guide, assign it to a real product and date, and review the evidence after the next cycle. Consistent learning compounds faster than dramatic reinvention.

Explore the complete library of free tools for makers or see how Batch Scale connects the work.