Why is the Walmart cart sharing link not working for me right now when I really need to get this order in? I am super stressed out because our delivery slot for the week is about to expire in like ninety minutes and my roommate needs to see the final total before we split the bill. Every time I send her the share link from my cart it just takes her to a page that says her cart is empty even though I have over $250 worth of stuff in mine.
I am debating between a few workarounds:
The screenshot thing is gonna be a nightmare because we have so many bulk items for the pantry and I dont want to miss anything. I really prefer the cart sharing so she can just hit add all or whatever but it just wont load for her. Is there some setting I have to toggle or is the Walmart app just glitching out? We are trying to stay under a strict budget this month and I dont want to accidentally double order something if she starts her own cart from scratch and we end up with two of everything...
> Giving her my actual login info which feels sketchy. Dont share logins, its a huge security risk. Use the list feature instead to prevent double-spending and keep your budget on track while the apps being buggy...
I've dealt with this exact headache before when I was trying to coordinate a huge supply run for a camping trip last summer. Honestly, the Walmart cart share feature is super finicky because it relies heavily on browser cookies and active sessions. If your roommate isnt logged into their own account on the same browser before clicking that link, it usually fails and shows an empty cart. I would suggest being very careful with your approach here.
Late to the party, but I have dealt with this several times during our monthly office supply runs. The Walmart share button is notoriously unreliable because it often generates a temporary URL that expires or fails if the recipient has a different home store selected in their app. If their local store doesnt carry one specific item in your cart, the whole link can sometimes fail to load the contents correctly. A few technical workarounds I have found that actually work: