# Identity + Quantity + Context = Truth

> Three inputs, and a test you can apply to any inventory process in about ten minutes.

- **Page** - https://iotready.com/insights/identity-quantity-context
- **Author** - Tej Pochiraju
- **Published** - 2026-05-02
- **Topics** - Fundamentals

Walk any inventory process and ask three questions at every step where something
moves. Which item is this, and how do we know? How much of it is there, and what
measured that? Who did this, where, and when?

You don't need a consultant for this. Take a clipboard, stand at the receiving
dock, and ask them out loud. Each answer is either "the system knows" or "someone
told it". Count the second kind.

## Identity

Read off the item. A QR mark, an RFID tag, a barcode someone printed at the
source. Not recalled, not inferred from position, not read from an accompanying
piece of paper.

Position is the sneaky one. "It's the blue crate on shelf C3" feels like
identity because it's been right every day for a year. Then someone moves the
crate, and every record that depended on the shelf is wrong at once.

A paper slip is worse, because it looks official. It tells you what someone
meant to send. The item in your hand is whatever it actually is.

So the test is simple. Cover the paperwork. Can the device still tell you what
this is?

## Quantity

Measured by an instrument. Weight, dimensions, temperature, humidity. A count
performed by a person is an estimate wearing a number's clothing.

That's not a complaint about people. Count 400 small items by hand at the end of
a long shift and you'll be off by a few. Everyone is. The number you type will
still be exact-looking, and nothing downstream will know it was a guess.

A scale doesn't get tired. It also doesn't round to the nearest ten because the
truck is waiting.

Some quantities have no instrument yet, and that's fine. Say so. A field that's
honestly marked "counted by hand" is more useful than one that pretends.

## Context

Supplied by the device, not the operator. Location, identity of the person, time,
and the state of the ERP transaction the reading belongs to.

This is the one people skip, because it feels like metadata. It's the one that
makes the other two usable.

A weight of 12.4 kg means nothing alone. Twelve point four of what, on which
scale, at what time, for which purchase order, by whom? Without those, you have a
number. With them, you have an event, and an event can be checked, audited and
argued about by people who weren't there.

When the operator has to supply context, they supply it late. Typing the time at
the end of the shift isn't the same as the time it happened, and everyone knows
it.

## Why it's an equation

Drop any one of the three and the record goes soft.

Identity and quantity without context gives you a right number you can't place.
Identity and context without quantity gives you a confident record of
"some". Quantity and context without identity is a precise measurement of
something unknown.

Add them up and the record can stand on its own. That's what I mean by truth: a
record that doesn't need the person who made it to vouch for it.

## The ten-minute test

Pick one process. Receiving is a good one. At each step where something moves,
write down the three answers and mark where each came from.

- From the item or an instrument: good.
- From a person, typed in the moment: weak, but traceable.
- From a person, typed later or copied from paper: that's your gap.

You'll find the gaps cluster. Usually it's one step, a handover between two
people or two systems, where all three go soft at once. Fix that step first.

Most of what an ERP gets wrong, it was told wrong. We've written about that in
[ERPs repeat the lies we tell them](https://iotready.com/insights/erps-repeat-the-lies.md). The test
above is how you find where the lying starts.

> **The point**
>
> If the system can't tell you how it knows, it doesn't know.