Decide where the work belongs
Separate block from friction
Give highest urgency to a valid-looking address that cannot reach shipping or payment. Treat a recoverable formatting prompt as lower risk when it preserves input and explains the correction. Raise urgency when a correction clears apartment, postal, or region data.
Describe supported scope
List the tested countries, regions, locales, and address shapes rather than asserting global reach. Use support reports and reproducible fixtures to show scope. Mark untested regions unknown, especially when the validation rule comes from an unavailable boundary.
Choose a safe fallback
Decide whether checkout can let a shopper review or edit the normalized address, save the entered value, or proceed only after an explicit confirmation. Do not bypass a necessary delivery check silently. Assign the owner for any temporary manual path.
What to carry forward
Prioritize a validation failure as checkout-blocking when a reproducible address cannot reach a truthful shipping and tax state. Otherwise queue it as input-preservation or wording work with tested scope, fallback behavior, and an explicit unknowns list.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow