Capture Critical Tracking Events

For FTL items, most Critical Tracking Events (CTEs) are recorded automatically. Keep using GRNs, warehouse transfers, and sale invoices as usual — Biznsbook fills in the Key Data Elements behind the scenes.

Receiving (automatic)

1. Create a GRN for an FTL item as normal.
2. Enter the batch number (required) and the supplier TLC on the line if the supplier provided one.
3. Post the GRN. A Receiving CTE is recorded. If no supplier TLC was given, an internal TLC is allocated automatically.

Transfers (automatic)

1. Transfer an FTL batch between warehouses as normal.
2. The system records paired Shipping + Receiving CTEs and propagates the TLC to the destination batch.

Shipping / sales (automatic)

1. Sell an FTL batch on a sale invoice.
2. A Shipping CTE is recorded against the lot.

:::info Delivery notes and Toast Delivery notes do not currently write Shipping CTEs. Toast POS sales imports can appear on the outbound Trace Report for visibility, but they do not create Shipping CTEs or FDA ESS rows. :::

Farm-side events (manual)

Use Manual CTE Entry for steps that are not part of a GRN, transfer, or sale:

1. Open Manual CTE Entry under Traceability.
2. Choose Harvesting, Cooling, or Initial Packing.
3. Select the FTL item, batch, and warehouse/location.
4. Enter quantity and unit, location description, and event date/time.
5. Save. The CTE joins the lot's event chain.

The CTE timeline can walk batch genealogy so parent lots appear in the chain. Transformation and Creation event types exist in the product but are not written automatically today.

What gets stored on each event

Typical Key Data Elements include TLC, product description, quantity/UoM, location, event date/time, reference document, and trading-partner GLN — enough to support a later Trace Report or ESS export.

Next step

Run a Trace Report

Search by batch, TLC, or GRN and review inbound and outbound chains.

Capture SFCR events

The same day-to-day pattern for SFCR-covered items.