Manufacturing tracking: the number that says what is actually made

A factory's truth is not the order, the plan or the invoice; it is the quantity produced, the quantity consumed, and the difference between them. Everything else — the schedule, the supplier agreement, the cost — derives from those three numbers, and when any of them is missing the rest of the year follows the gap.

What are the three tracking points?

Start, finish, and inspection. Start records when the batch actually begins: the date, the lot number of the raw material, the operator's name, the planned quantity. Finish records when the batch is done: the actual quantity made, the time, and any deviation from the plan. Inspection records what was accepted and what was rejected: the quantity that passes, the quantity that fails, the reason for the failure, and who signed the decision.

Only two of these are strictly needed in a small factory. Start and finish give you the production number. Inspection is the quality record, and a small factory can combine it with finish — one form, one signature — as long as the fields stay separate. What you must not do is collapse finish and inspection into a single checkbox: a batch that is "done" but not "passed" is a different event from one that is both, and the difference is where the supplier argument lives.

Why is the batch a property of the production, not the ingredient?

A batch number that belongs to the ingredient ties the production record to the supplier's delivery, not to what the factory actually made. That works until the supplier changes a lot number mid-delivery, or the same ingredient arrives from two suppliers in one week. The batch that matters is the production batch: it starts when work begins, it carries the ingredient lots that entered it, and it ends when inspection is signed.

The ingredient lots are properties of the production batch, listed on the start record: supplier, supplier lot, date received, quantity received. When an argument comes — a rejected batch, a claim that a particular ingredient was bad — the record that survives is the one that links the supplier lot to the production batch to the inspection result. A supplier who sees only the ingredient invoice has no reason to accept responsibility for the finished product; a supplier who sees the production batch with the rejected quantity and the reason has a reason to talk.

That record is also the audit trail for the accountant: what was received, what was accepted, what was rejected, and when. Cost follows the accountant's rules, not the software's; this text describes the count, not the cost.

What does a weekly review compare?

Two pairs of numbers. The first is planned versus made: the production schedule for the week against the finished batches, with the deviation stated as a quantity and a reason — machine stop, material shortage, operator absence, quality hold. A deviation without a reason is a number that will repeat.

The second is consumed versus purchased: the ingredient lots that entered production that week against the supplier deliveries received, with the difference explained by what is still in stock and what was rejected at receipt. A supplier who delivers on time but delivers short, repeatedly, is a different problem from a supplier who delivers late; the weekly review makes the pattern visible before the factory stops for lack of material.

The review should take fifteen minutes: open the finished batch list, open the inspection records, open the supplier delivery record, count the differences, and write the reasons. A review that requires a meeting is a review that will not happen.

|| Dimension | Small factory practice | What the record must show | || --- | --- | --- | || Batch identity | Production batch number, not supplier lot | Start date, ingredient lots, quantity planned | || Quality decision | Signed at finish, not in a separate step | Accepted quantity, rejected quantity, reason, signatory | || Weekly review | Planned vs made, consumed vs purchased | Deviation with reason, supplier delivery difference |

What does a supplier argument need?

Not a complaint, but a record: the production batch number, the supplier lot number that entered it, the quantity accepted, the quantity rejected, the reason for the rejection, the date of the inspection, and the name of the person who signed. That is enough for a supplier to respond; without it the conversation is opinion against opinion, and opinion does not resolve a claim.

The form does not need to be digital to work. A paper form with the same fields, kept in chronological order, survives a dispute better than a message thread. The software's role is to make the form easy to find, not to replace the signature.

Where does tracking stop being tracking?

At the point where the factory starts computing cost. Cost accounting has its own rules — allocation of overhead, treatment of waste, valuation of work in progress — and those rules belong to the accountant, not to the tracking system. A tracking system that claims to calculate cost is a system that has stepped outside its evidence and is now making an accounting claim it cannot defend.

The same limit applies to legal claims: what a supplier owes, what a contract requires, and what a regulator demands are the authority of the contract, the lawyer, and the regulator — not this text. This article is about the count that makes the argument possible; the argument itself is settled elsewhere.

Where this goes wrong

• The batch is identified by the supplier lot, so the production record collapses when the supplier changes a delivery.
• Inspection is a separate process that never happens; rejected batches enter the finished number and the next customer receives them.
• The weekly review compares plans to plans; the actual finished quantity is not counted against anything.
• A supplier argument is made without a signed inspection record; the supplier responds with the same absence of evidence.
• The system calculates cost and presents it as a production number; the accountant disagrees, and neither can defend the figure.

What this does not cover

This is about counting production: the batch, the inspection, the supplier link, the weekly comparison. It does not cover cost accounting, which follows rules the accountant owns; contract law, which a lawyer owns; or regulatory inspection requirements, which the factory's regulator sets. It quotes no prices, no salaries, no production rates, and no statistics about factory efficiency. A factory in Algeria may have different supplier, inspection and record-keeping obligations; verify them with the regulator, not with this article.

We build production tracking systems that count the batch, link the supplier, sign the inspection, and compare the week — the numbers that make a factory administratively sound.