Hi everyone,
I’m running into an issue with Checkout Validation Functions and wanted to see if others have experienced something similar or if I’m missing something.
Context:
-
Using Cart & Checkout Validation Function
-
Validation target is address-related fields (e.g. deliveryAddress)
-
Logged-in customers with a saved/default address
-
One-page checkout (Checkout Extensibility)
Issue:
When the validation fails:
-
The checkout is correctly blocked

-
The function returns errors as expected

-
But no error message is displayed in the UI

This seems to happen specifically when:
-
The address is auto-filled from a saved customer address
-
The user does not manually interact with the address fields
Observations:
-
For guest users (manual input), error messages seem more reliable
-
The validation function itself is definitely running and returning errors
Questions:
-
Is this expected behavior with saved/autofilled addresses?
-
Are there known limitations around validation message rendering for address fields?
-
Is the
targetfield only a “best effort” for UI placement rather than guaranteed display? -
Has anyone found a reliable way to ensure users always see validation errors (besides using a Checkout UI Extension)?
Example (simplified):
{
"errors": [
{
"message": "Invalid address",
"target": "$.cart.deliveryGroups[0].deliveryAddress.address1"
}
]
}
Would really appreciate any insights, confirmation, or workarounds.
Thanks in advance!
