Batch and serial trace review

Trace supplied batch relationships and movement ledgers, calculate unit-bound balances and identify recipients and missing evidence within an explicit scope.

Input

Result

A parent batch reaches a finished batch with a recorded shipment. The finished ledger balance is 15 kg, and the shipment recipient and reference remain attached to the movement. The trace is limited to the supplied records.

A trace review combines a batch register, transformation relationships and movement records. Deterministic traversal reveals reachable batches, while the ledger calculation keeps quantities tied to explicit units. AI reviews a bounded selection of exact batch notes for handling, identification or quality concerns.

Your texts, pages and images are processed on our own servers in the EU. Trust Center

Try it now Pricing

Who it is for

Operations, warehouse and quality teams reviewing a defined batch or serial number using internal records.

Typical uses

Trace forward to downstream batches or backward to inputs.
Identify recorded shipments and recipients.
Compare ledger balances with a threshold.
Surface unknown batches, mismatched units and missing references.

Example

Input

Batch register CSV: id,product,serial,unit,opening,notes B1,Base material,S1,kg,100,Keep dry B2,Finished product,S2,kg,20,Inspect packaging Batch relationships CSV: parent,child B1,B2 Movement ledger CSV: id,batch,kind,quantity,unit,party,reference,date M1,B2,ship,5,kg,Warehouse A,DEL-1,2026-11-01 Starting batch: B1 Trace direction: forward Maximum relationship depth: 10 Display zero stock: yes Movement details: all Stock warning threshold: 0 Detail order: batch

Result

A fixed example, shortened. Real results are AI-generated: please check them.

Price and limits

Price: usually 1–3 credits
Available with: Free, With package
Input limit: One page with up to 200,000 characters of HTML

Privacy

Processed on our own servers in the EU (Poland). Inputs and results are deleted after 7 days (Free) or 30 days (packages), or right after you see the result if you choose not to store them. Images are deleted right after processing.

In the API

Tool name: batch_traceability. Create a job with POST /api/v1/jobs and fetch the result with GET /api/v1/jobs/{id}. You find your API key in your account.

curl -X POST https://do4u.eu/api/v1/jobs \
  -H "Authorization: Bearer d4u_…" -H "Content-Type: application/json" \
  -d '{"tool": "batch_traceability", "url": "https://example.com/"}'

Full API documentation →

Questions and answers

Does this prove a complete recall scope?

No. The trace only covers supplied relationships and records within the selected direction and depth. Missing records and a depth boundary prevent a completeness claim. No recall, purchase or scheduling action is performed.

How are quantities calculated?

Opening balance plus receives and positive adjustments minus consumption, shipments and negative adjustments. Relationship edges never change balances. Units must match exactly; incompatible movements are reported and excluded.

Is the cutoff a historical inventory snapshot?

No. The cutoff filters dated movements only. The supplied opening balances and undated relationships remain the responsibility of the source dataset.

Is my text stored?

Only as long as needed: 7 days on Free, 30 days with a package – or not at all if you choose not to store it. Processing happens on our own servers in the EU (Poland).

Can I use the result right away?

Results are AI-generated. Please read them before you publish or send them.