Description:
Immaculate Trading Cards reported that updating the store address in Dashboard 2.0 shows an "Error saving profile" message and the address keeps reverting to the old value. Support confirmed the org should use 674 Kenhorst Plaza, Reading, PA 19607 and found that Django still had the old address 203 West Lancaster Avenue, Shillington, PA 19607, US saved while the legacy coordinates pointed to the new location.
Store name: Immaculate Trading Cards
Correct address: 674 Kenhorst Plaza, Reading, PA 19607
Previous address in Django: 203 West Lancaster Avenue, Shillington, PA 19607, US
Legacy coords noted by support: 40.300591486075426, -75.94848933143845
Steps to Reproduce:
- Open Dashboard 2.0 Organization Settings for the store.
- Attempt to update the Store Address to
674 Kenhorst Plaza, Reading, PA 19607. - Click save.
Current Result:
The UI returns "Error saving profile" and the store address reverts to the old address. Support had to update the address manually.
Workarounds:
Support manually updated the store address.
What or how many support tickets are blocked by this?
This conversation required support intervention to complete the address change.
(If internal tool): what core actions are you trying to take that aren't possible because of this?
A store cannot reliably update its own address in Dashboard 2.0.
Expected Result (Success Criteria):
- [ ] Saving a store address change persists the new address instead of reverting.
- [ ] Dashboard/admin address data and location data remain consistent.
