Validating Shopify selling_plan_id without rejecting normal null values
The new webhook field carries the selling plan for subscription items. Requiring it on ordinary purchases rejects valid data.
Not every null needs another lookup
Null has a valid meaning on an ordinary purchase item. A required-value check that ignores subscription status sends legitimate orders into unnecessary lookups. Filling an arbitrary plan ID or string to improve completeness may make a quality metric look better while destroying the evidence of the purchasing arrangement. [1, 2, 3]
The additional field can reduce API calls
Shopify's 2026-10 announcement adds selling_plan_id to line items in Orders webhooks. It identifies the plan applied to a subscription item and is null for a non-subscription item. The change delivers information that previously required an additional Admin API request; earlier API versions remain unaffected. A field's availability does not mean every item must contain a value. [1]
Do not derive subscription status from the null being tested
The order-support owner should preserve purchase type and API version. Accept null for an ordinary purchase and separate subscription references that require investigation. Deriving subscription status solely from whether selling_plan_id is empty would make the expected result depend on the same observation under test. First align an independent purchase-type record, such as the order ledger, by item key. [1, 3]
A conditional fixture for an ordinary purchase
Define an illustrative item as non-subscription according to an independent order record. Its expected plan-nullness is true. An actual true preserves an inapplicable reference without inventing one. A false result means a plan ID is attached to an ordinary purchase; inspect the source for a mapping mixed with another item. If subscription status is unknown, this rule cannot establish normality or omission, so retain an investigation state. [1, 3]
Use the specified condition instead of blanket NotNull
RowLevelValidator in Truthound Core 3.3.2 accepts a row_validator callback for the relation between purchase type and null state. The proposal narrows a required-value rule to its valid scope. First distinguish a field absent in an older version from an explicit null in the new version. Truthound does not retrieve subscription contracts or make payment decisions. Send only insufficiently supported items through an approved lookup procedure instead of repeatedly querying every normal null. [1, 2, 3]
Application conditions
Read item-level source data from Orders webhooks in 2026-10 or later. Establish subscription status from the order ledger, not by inferring it from the absence of the same field under test.
Alternatives
Send only items with uncertain subscription status through an approved ledger lookup; do not generate an additional call for every null.
Limitations
Truthound does not retrieve subscription contracts or decide payments. Distinguish a field absent in an older version from an explicit null in the new version.
Evidence
- Event checked
- Subject checked
- Modified
