Solving the 'Sold Out' Mystery: Why Your Shopify Collaborator Account Sees No Stock

Ever been in that frustrating spot where you're diligently working on a Shopify store, maybe tweaking a theme in the preview, and suddenly you hit a snag? You try to add an item to the cart, and BAM! – "Sold out." But here's the kicker: the product is definitely in stock, the live site works perfectly, and other users (like the store owner) have no issues. It's just you, the collaborator, staring at that pesky "sold out" message.

This exact scenario recently popped up in the Shopify Community, with a user named jacob991 describing this very head-scratcher. He was making some custom cart changes and couldn't get past the "sold out" error in the development theme preview or editor. If this sounds familiar, you're not alone, and the good news is our community experts jumped in with some fantastic insights.

Why is This Happening to Just Me?

When an issue like this is specific to one account and not the entire store, it almost always points to something related to your individual session, account permissions, or how your context interacts with the store's settings. It's less likely to be a bug in the theme code itself if others aren't seeing it.

Check Your Collaborator Account Permissions and Context

VikashJ from Apploy hit the nail on the head, suggesting we first look at the collaborator account itself. This is often the culprit for specific user issues:

1. Location Access Limits: "Under Settings > Users and permissions, open your account and look for any location access limits." If your account is restricted to certain locations, and the primary stock for the product you're testing sits at a location you don't have permission to see, the store might display "sold out" specifically for your session.

2. Linked Customer Account: "It's worth checking whether you're also linked as a customer account on this store, separate from your collaborator access." This is especially relevant for B2B or wholesale stores. If your email is tied to a customer profile with specific location assignments or price lists, the storefront might be checking availability against that, rather than the general inventory.

Dig Into Market and Location Settings

While ahsandoesntcare pointed out that preview themes generally pull the same product data as the live storefront, they emphasized that "the difference is usually market or location context." This is a critical area to investigate:

1. Market Fulfillment Locations: "In Settings → Markets, open the active market and check which locations are set to fulfill it." Then, go to the product variant itself and look at its inventory per location. If your product's stock is only in locations not assigned to that particular market, shoppers (or your session acting as one) in that market will see "sold out."

2. "Continue Selling When Out of Stock" Setting: Confirm that the variant isn't set to "Continue selling when out of stock: off" with inventory tracking on. While less likely to be account-specific, it's a quick check to rule out a general inventory misconfiguration.

3. Preview URL Domain: "Also check the preview URL's domain." Sometimes a market-specific domain can route you to a context where the location isn't available.

4. Dropshipping App Interference: Laza_Binaery threw out a good "just guessing" idea: "is it maybe some dropshipping store with some of the popular apps? They all might have some setting to limit products by location." If the store uses third-party inventory apps, they could introduce their own location-based rules.

Bust That Browser Cache!

Sometimes, the simplest solution is the best. VikashJ wisely suggested ruling out a stale session entirely:

1. Log Out and Clear: "Log out of everything, clear cookies for the store's domain."

2. Fresh Start: Try the preview link in "a fresh incognito window on a device you haven't used with this store before." Cart and location context can get cached to a session, and once set, can persist across reloads.

3. Test Without Login: "Try duplicating the development theme and testing the same add-to-cart action from a plain browser session with no login at all, just the theme preview link with no other tabs or cookies." If it works here, you know the issue is tied to your specific browser session or account, not the theme code itself.

Jacob991 also tried using a VPN to match the store's location (a suggestion from Laza_Binaery), but it didn't solve his particular issue. Still, for others, location-based routing can sometimes be a factor, so it's not a bad initial thought.

When All Else Fails: Deep Dive with Developer Tools

If you've systematically gone through the above, and you're still hitting that "sold out" wall, it's time to get a bit more technical. Cuong, founder of Trooix, offered an excellent debugging strategy:

1. Inspect the Add-to-Cart Response: "In your browser’s Network tab, trigger the error and inspect the request to /cart/add.js, or its locale-prefixed equivalent."

2. Gather Key Data: Note "the submitted variant ID and quantity, the HTTP status, and the error description in the response."

3. Compare and Contrast: "Then have the owner test that same variant and quantity in the same draft theme, not just on the live site." By comparing your failed request with the owner's successful one, you can pinpoint differences. A 422 response with a sold-out description is very different from the theme merely displaying "sold out" after some other request error.

4. Check Cart Quantity: "Also check how many units of that variant are already in your cart, since that can affect whether more can be added." This is a simple but often overlooked detail.

This systematic approach, combining permission checks, market configurations, session troubleshooting, and technical debugging, covers all the bases. The "sold out" error, especially when it's unique to your collaborator account, can be tricky, but by following these steps, you should be able to uncover the root cause and get back to making those custom cart changes without a hitch!