Block Gemini

Explore the connected ecosystem.

Can you trace this lot across a missing handover?

Follow a parts lot from a supplier through a carrier to a depot. Inspect each custody event and the evidence behind it.

Scope my lot traceability

Interactive example · fictional records

Inspect a custody event

Lot L-84 · Replacement parts

Last confirmed holder
Receiving depot
Evidence received
Carrier acknowledgement and depot scan
Custody status
12 cartons reconciled
Depot receipt
Review decision

Link the recovered event to the received lot

The carrier supplies the collection receipt and the depot confirms its count. Each event keeps its own recording time so the later correction remains visible.

Scope my lot traceability
Play the custody handover filmIllustrative freight handover. A physical transfer and a signed receipt are separate steps in the custody record.

What we can build with you

A lot timeline linking physical evidence, participant acknowledgements and a queue for missing custody events.

Bring to discovery
Bring lot identifiers, the physical scanning points and two trading partners’ handover records.
How to test the pilot
Trace a lot backwards through a late receipt and a missing scan. Check that every custody claim can be traced to its owner.
Implementation details and questions

Supply-chain and operations teams following products, batches and custody across organisations.

Connect product, batch and custody events across organisations. We design identifiers, capture workflows, evidence links and partner access so teams can investigate a journey from source to destination. Blockchain is an option when shared governance requires it.

  • Batch and product journey investigation
  • Partner handovers and custody records
  • Evidence links for provenance and quality review
  1. Identify the item and event

    Define identifiers for products, batches and participants. Agree which events matter and what evidence accompanies each record.

    An identifier and event schema
  2. Capture the handover

    Connect capture tools, enterprise records and partner submissions. Validate permissions and record missing, disputed or corrected information.

    A linked custody and evidence trail
  3. Investigate and act

    Let operators inspect the journey, trace related batches and route exceptions. Connect the investigation to the approved operating process.

    An investigation view and follow-up workflow

Capture and partner systems → validated event model → shared or central record → evidence and investigation interfaces. Sensor readings require their own reliable measurement and calibration process.

  • Identifiers and event data model
  • Capture, handover and evidence workflows
  • Partner and enterprise integrations
  • Investigation and exception interfaces

Make the event record useful first: identity, time, evidence, handover and exception ownership. Select the storage and trust model around the participants.

  • A recorded statement does not establish physical authenticity or eliminate fraudulent input. Source controls remain essential.
  • Regulated traceability obligations and supplier participation require a specific operational assessment.

Bring to discovery

  • Product/batch identifiers and event definitions
  • Partner roles and source-system access
  • Evidence, retention and correction rules
Can this cover different supply-chain industries?

The pattern can be scoped for different products and partner networks. Event definitions, evidence and regulatory requirements must be adapted to the actual industry.

Will we need every partner to change systems?

Not necessarily. Interfaces, capture tools and staged onboarding can connect different systems, subject to each partner’s access and data quality.

Trace one product batch through a disputed handover

For manufacturers, suppliers and buyers who need to verify the history of a particular batch across organisations.

How the work moves

The supplier registers a batch with its certificate. The carrier acknowledges collection and the receiver checks quantity and condition. If a seal is damaged, the receiver records the exception. A buyer can verify the chain of events and see who attested to each one.

What we connect and deliver

Connect batch identifiers from ERP, warehouse scans and supplier submissions. For monitored shipments, map a carrier milestone or a sensor reading to the correct lot and identify who verifies it. Define which events partners may validate and which documents stay under their owner’s control. A shared ledger is useful when independent partners need the same verifiable history.

Where to start

Choose one product line and two handover points. The pilot brief specifies the event schema, corrections process, verifier view and examples the buyer must be able to trace.

Scope a batch traceability pilot