One email about one jar. You have the answer before lunch.

A customer writes about a jar from March. Which batch? Which chili delivery? Which other jars? On binders and a text thread, that is an afternoon of archaeology with a deadline on it, and everyone in the workshop knows it.

In BatchDash the answer already exists: every batch records the lots that went in and books its output under a lot code, as a side effect of just running production. Tracing is typing one code and reading.

Request access Sign in

01Traceability

One code, and the trail opens both ways

Type the lot off a label, a delivery note or a batch record. The screen names what the lot is, then opens in both directions at once: what it came from, and where it went. Every row is a real record you can open rather than a report line: the delivery, the purchase order, the batch, the movement, the sale. Push either side a step deeper when the question needs it.

A lot trace in BatchDash: what the lot is, the deliveries and batches it came from, and the batches, stock movements and sales it went to.

02Traceability

Who has it, and what you can still stop

This is the half a spreadsheet never has. The lot reached one customer, who took 28 jars on an order you can open from the row. Twelve more were sold without an order, and the screen says plainly that there is nobody to contact for those. Twenty-two are still on your own shelf. And thirty are sitting on a confirmed order that has not shipped yet, which you can still stop from the order page. Six went into a gift box, and the set knows it.

A recall summary in BatchDash: the customer who received the lot with their order, what was sold without one, what is still on hand, what sits on an unshipped order and can still be stopped, and what went into gift sets.

03Traceability

When it is the vendor calling

The other direction starts with a phone call about a delivery. Type the chili lot and the screen gives you the vendor and the purchase order behind it, then every batch it reached and how much each one took. From there, one click is the finished lot and one more is the recall summary above. The perimeter stops being a guess, and getting to it takes about a minute.

An ingredient lot traced in BatchDash: the vendor and purchase order it came from, and the batches it went into with the quantity each one drew.

04Traceability

As deep as you ask, and honest where it cannot be sure

Both walks open one level at a time, up to five, so the screen answers the question you actually asked instead of burying it:

A made component traces straight through: the jar knows its mash batch, and the mash knows its chilis.
Ingredient stock is pooled at average cost, so a lot cannot always be pinned to one batch. A row it could have reached is marked possible instead of claimed.
That marking is the point. A trace that overclaims is worse than no trace at all when somebody is deciding what to withdraw.

05Traceability

The code they quote is the code you search

The customer’s email quotes something printed on the jar. That something is the batch’s own lot, put on the label by the editor reading it off the record, which is why pasting it into the search finds the batch on the first try. No parallel numbering scheme, no lookup sheet taped inside a cupboard door.

06Traceability

And a file for whoever is asking

The whole walk exports as a file, with the order and the customer on every sale it names. An auditor, a customer’s QA department or your own insurer gets a document, and your afternoon stays yours.

Works with

Batch recordsSealed batches, revertible trials StockA ledger every figure walks back to LabelsDesigned once, filled by every batch Batch manufacturing softwareThe whole system on one page, with its screens

Tracing a lotIn the help center