{"section":"known-issues","requestedLocale":"en","requestedSlug":"addressid-mismatch-causes-invalid-address-for-an-item-error","locale":"en","slug":"addressid-mismatch-causes-invalid-address-for-an-item-error","path":"docs/en/known-issues/Checkout/addressid-mismatch-causes-invalid-address-for-an-item-error.md","branch":"main","content":"## Summary\n\n\nThe `shippingData` cart attachment supports the `addressId` field within a few different objects: `logisticsInfo`, `address`, and `selectedAddresses`.\nThe `addressId` field is also persisted in the user's saved addresses, kept within Master Data's AD entity.\n\nWhen placing an order, the Checkout API compares the selected shipping address in the orderForm with the ones available within the user's profile.\nIf a match occurs, the `addressId` within `address` and `selectedAddresses` from the orderForm is replaced with the existing value from their profile.\n\nHowever, at a later point in the API's validations, it will also compare this `addressId` with the one in the `logisticsInfo` object.\nAs the one in `logisticsInfo` is not replaced by the aforementioned process, they may not match, and this later validation will fail.\nThis triggers an \"**invalid address for an item**\" / \"endereço inválido para um item\", preventing the purchase from being completed.\n\n\n\n##\n\n## Simulation\n\n\n\n- Save two different addresses within a user's profile, and take note of their `addressId` values.\n- Assemble a Place Order request. Use one of your addresses created in the previous step, but use the `addressId` of the other one.\n- Send the request. The response will contain the error message \"invalid address for an item\".\n\n\n##\n\n## Workaround\n\n\nWhen sending the Place Order request with a previously saved address, ensure the value used for `addressId` matches the actual address data.\nAlternatively, you may also omit the `addressId` from the request."}