Definition
In JSON, a property set to null is present with a null value; an omitted property is absent. Zero, false, and an empty string are different values again. A commerce data contract must define what each permitted state means rather than assuming null universally means unknown or clear this field.
Why It Matters
- A missing stock quantity must not automatically become zero stock. An unknown product measurement must not become a measured zero.
- A Commerce Intelligence OS needs trustworthy field meaning before an agent filters products, evaluates return reasons, or recommends an operational action.
How It Works
- Define each field independently: whether presence is required, whether null is allowed, and what null means for this operation.
- Specify snapshot and update semantics separately. For an update, omission might mean leave unchanged while null might mean clear, but only when the documented endpoint contract says so.
- Validate payloads before transformation. Avoid defaulting all falsy values to one replacement because legitimate zero and false values would be lost.
- Preserve provenance and uncertainty through analytics and agent inputs. Route incomplete required evidence to an explicit unresolved state with an accountable owner.
Ecommerce Example
Context: Illustrative example: a product update omits material composition, sets care guidance to null, and sets stock quantity to zero.
Recommended move: Under a contract where omission preserves values and null clears optional text, retain composition, clear care guidance, and record confirmed zero stock.
Why it matters: A different endpoint may reject that null instead. Validate the actual contract before applying the update; this is a design example rather than a claim about iKawn integrations.
iKawn Framework
Define
The iKawn ontology framework names each field and its permitted states.
Validate
Check presence and value rules before accepting data.
Preserve
Keep unknown evidence distinct from confirmed commercial facts.
Resolve
Request missing evidence before executing a dependent decision.
Concise Summary
Absent, null, zero, false, and empty text are distinct states. Give each permitted state an explicit contract and preserve that meaning throughout commerce workflows.