Subscribe free
Alloconomy 19 Oct 2026 5 min read

Sent, Received, Accepted: Three Different Claims

Order lines, shipment assertions, receipt evidence and message status.

Part 4: books & evidence. 60 declared = 56 accepted + 2 held + 2 not counted Fictional teaching model.

Part 4 of 16 · Behind the Buy Button

Maya says sixty; the receiving team says fifty-eight

eComm Inc has ordered 100 books at $20 each. Maya's first shipment notice reports 60 books. The receiving team counts 58. Of those, 56 pass the assumed inspection; two have damaged-looking covers and await a decision.

It is tempting to choose one number and call it “the quantity.” That would remove most of what we need to learn.

Part 4: books & evidence. 60 declared = 56 accepted + 2 held + 2 not counted Fictional teaching model.
Four quantities. Four meanings. ORDERED — 100 — Whole order; DECLARED SHIPPED — 60 — First shipment; COUNTED — 58 — Receiving observation; ACCEPTED — 56 — Inspection so far. Forty books have not yet been declared shipped. Counts are illustrative. Fictional example; see the nearby table and prose for an accessible explanation.
View the full-size diagram →

The evidence cheat sheet

Observation Quantity Who or what supports it?
Ordered 100 Approved commercial order
Declared shipped 60 Maya's shipment assertion
Counted at receipt 58 Receiving team's observation
Accepted so far 56 Inspection decision in this example
Still awaiting inspection 2 Open quality record
Not yet declared shipped 40 Remaining order quantity

The two missing books and the two held books are different problems. The remaining 40 books are not automatically part of the first shipment's shortage. Every quantity needs a scope: which order line, which shipment, which receipt and which date?

A shipment notice makes a claim about departure

An advance shipment notice, or ASN, tells the recipient what the supplier says is on the way. Amazon's Vendor Shipments documentation explicitly names shipment confirmation as an ASN.

In our example, Maya's notice and eComm Inc's count are independent statements only if someone actually counted the books. A “receipt” copied automatically from the shipment notice cannot independently confirm that 60 arrived. Two agreeing screens can be repeating one assertion.

Before the Shelf examines the physical handling and counting process. Here we need its commercial consequence: preserve what was declared and what was observed so the discrepancy can be investigated.

A unit needs a meaning

Now suppose Maya ships ten cartons, while the receiver records 120 individual books. These quantities agree if each carton contains twelve copies.

Normalized copies = cartons × copies per carton = 10 × 12 = 120.

The conversion needs an effective date. If Maya later switches to ten-copy cartons, rewriting the master record must not turn the old receipt into 100 copies. Keep the submitted quantity, unit, conversion and normalized quantity together.

The same discipline applies to an edition identifier. A hundred copies of the wrong edition do not satisfy an order merely because the count matches. A monetary quantity used in a software integration is different again; Part 12 examines that trap.

The message arrived; did the business event happen?

Maya's system submits an invoice and receives a technical processing status. That tells her something about the message. It does not, by itself, tell her whether the invoice was approved or the bank payment settled.

Amazon's transaction-status documentation is particularly instructive: the available result depends on the operation, and the documented Success state is not supported for submitted invoices or acknowledgements. Reading all interface statuses as one universal business outcome would be a mistake.

For eComm Inc, I would keep separate observations for message receipt, commercial validation, accounting recognition and payment. That is a proposed model for this series. It is not a description of Amazon's internal implementation.

Acceptance applies a requirement to evidence

The inspector might release the two held books after examining their covers. Accepted quantity would rise from 56 to 58; physically received quantity would stay 58. No new books arrived. A decision changed.

If the two missing books are subsequently located, the receipt history should record the correction or additional event. It should not silently replace the original count. Maya and eComm Inc need to understand both the best current view and why yesterday's view differed.

For Maya, this supports a specific claim rather than a vague complaint that “the system is wrong.” For eComm Inc, it assigns the next task to the right person: count, quality, item identity or data interpretation. For me, it explains why a fulfillment status and the condition of the book in my hand can answer different questions.

Our next step is to put prices beside these quantities. That will turn the disagreement into dollars without making it disappear.

Continue the series

Previous: The Purchase Order Begins Before the Purchase Order. Next: The $140 Disagreement Inside One Invoice. Return to the introduction and cheat sheet.

Evidence and method: public references were checked on October 18, 2026. The fictional scenarios, proposed controls and design conclusions are learning models, not claims about a real employer. Reported financial figures retain their stated measurement dates.