In in initial design I was doing just that. Using the npub to fetch profile data and then filling in a profile card of the seller on the store and automatically adding the correct lightning address. I decided to remove it for two reasons reasons. The first was the increased impersonation risk. I could set my profile picture and description to look just like yours and a customer would likely never check and see a different npub. Relying only on the verification phrase and the npub I had hoped would make this risk smaller. The second reason was privacy. When you open a store with all relevant information in the URL there is no way for someone to tell what store you are on. If I add a profile or lightning address lookup then you are pinging relays requesting a store from a specific user. Since at this point I had already decided not to add profile name/picture/bio I felt the relay request was not needed for just the ln address. However this may have been the wrong approach and having the ability to swap ln addresses on an existing store may have been worth it as an option. Regarding updates you are correct. The catalogue of a store is fixed. Any change to any detail will alter the link. The mitigation I have for this is the optional Inventory management toggle. Without an inventory management event a store link is forever, can never be updated or changed in any way. Stores such as this should not be shared widely. With an inventory management event you can mark certain items as discontinued or out of stock, or you can close the store entirely and optionally provide a link to an updated store. It would have been possible to put all the items on relays but at that point you are just recreating the stores that nostr already has and are creating nnothing new. I am hesitant about stores as perhaps the UX is just too bad to make them ever useful. But they were the first site type and I have a soft spot for them. That being said I still wonder if it is best to remove them alltogether.