address Validation

Retired Boards Appdev Custom Storefronts

Topic summary

  • Issue: Creating/updating customer addresses via APIs (customerAddressCreate, customerAddressUpdate) accepts entries without validation. Example payload with placeholder values (including country iso2 “be” and non-conforming ZIP) is saved without errors.

  • Conflict: At checkout, checkoutShippingAddressUpdateV2 enforces validation and rejects the same address with the message: “Please enter a valid zip for Belgium.”

  • Impact: Users can store invalid addresses in their profiles but cannot use them for shipping, causing a broken checkout experience.

  • Core concern: Inconsistent validation rules between customer address endpoints and checkout shipping address update. The poster seeks a way to prevent users from saving unusable addresses (e.g., by validating earlier or aligning validation across endpoints).

  • Status: No guidance or solution provided yet; question remains open with no decisions or action items reported.

Summarized with AI on February 8. AI used: gpt-5.
1

Hey everyone,

When i call customerAddressCreate and customerAddressUpdate, I do not think there is an address validation. This is the object that I sent :

{“address1”: “Aaaaa”, “address2”: “Aaa”, “city”: “Aaaa”, “country”: {“areaCodes”: null, “dialCode”: “32”, “iso2”: “be”, “name”: “Belgium”, “priority”: 0}, “firstName”: “Aaaa”, “province”: “Aaaa”, “zip”: “Aaaaa”}

Then there is no error. However, there is an address validation when I call checkoutShippingAddressUpdateV2.
When I want to use the address that I create there is an error and it says: “Please enter a valid zip for Belgium”.

In other words, A user not able to user an address that he/she create it.

How can I prevent users from encountering such a problem?

1 Like