BagCheck compares the three recorded measurements in the best physical orientation. It does not invent a missing axis label or assume that unknown protrusions are included.
Source
Where these details came from
Last checked
Unknown
Evidence
PATCHED (root review BOUND_PERSISTS_IN_IDENTITY): identity.capacityVariant cleared from '1L' to null. The product's own title names no '1L' size, and its capacity is published only as a sub-1L bound ('<1L' bound token at [1136075,1136077)), so no size-bucket name is supported. physical.capacityLitres was already null. STALE SENTENCE REMOVED: the note previously asserted that the bound was stored as a capacity value, which contradicted the null field. No capacity value is asserted now. ORIGINAL NOTE (minus the stale sentence): Retained first-party Shopify feed object (handle modular-pouch-sling). Exterior dimension line cited ('12" x 6" x 1"'). Carriage literal inside this product's own body: 'Comes in three pre-assembled configurations with our Quick Release Shoulder Strap.' Bare 'Weight: 6oz' line states no empty/unladen basis, so emptyWeightKg is null. Published capacity is a BOUND, not a fixed volume: the witness literal is "<1L" (less than 1 litre). The maintained parser derives 1 from it, but the field is held null rather than recording a bound as an exact capacity.