Marketplace Connect Bug: Are Your Shopify Variant SKUs Disappearing on eBay?

Hey everyone, your Shopify migration expert here, diving into a critical discussion from the community forums. We've all been there – relying on apps to keep our multi-channel sales flowing smoothly, only to hit a snag that throws everything into chaos. Recently, a very detailed thread caught my eye, highlighting a persistent and concerning bug with Shopify's own Marketplace Connect app, specifically impacting how variant SKUs are transmitted to eBay.

Imagine this: you've got a fantastic product with multiple variants – different colors, sizes, whatever it might be – each with its own unique SKU. You're expecting Marketplace Connect to faithfully send those unique identifiers to eBay for accurate inventory tracking. But what if it suddenly starts sending only the parent SKU, the main product identifier, instead of the specific variant SKU? That's exactly what one diligent merchant, Manfred Kraus (lonewolf in the forums), has been battling since May 10, 2026, and it's created a massive headache and a significant overselling risk.

The Core Problem: Variant SKUs Going Missing

Manfred's detailed account laid out the issue clearly: for multi-variant products, Marketplace Connect began transmitting only the 5-digit parent SKU (e.g., 12600) instead of the correct 9-digit variant SKU (e.g., 126002101) to eBay. This isn't just a minor glitch; it completely breaks inventory management for these products. If you sell a 'blue' variant, but eBay only sees the generic parent SKU, how does it know which specific variant's stock to reduce in Shopify? The answer is, it doesn't, leading to potential oversells and unhappy customers.

Manfred provided a stark comparison:

What's particularly troubling is that this isn't an isolated incident. Another merchant (home24 Outlet) reported the exact same issue in an App Store review, confirming it's a systemic problem, not just an account-specific quirk.

Digging Deeper: Manfred's Technical Hypotheses

After weeks of fruitless back-and-forth with support, Manfred, clearly a very technically savvy merchant, started doing some serious detective work. He proposed a few compelling theories as to the bug's root cause:

The "Wrong Variable" or "Changed Variable Name" Theory

His primary hypothesis is that Marketplace Connect might be trying to read a variable for variant SKUs that either no longer exists or had its name changed in Shopify's API or in the app's code around May 10, 2026. If the app tries to read an empty or null variable, it likely falls back to transmitting the parent SKU. This would look something like this in simplified pseudocode:

IF variant.SKU exists AND is not empty:
  transmit variant.SKU → eBay
ELSE:
  transmit parent.SKU → eBay  ← fallback triggered after May 10, 2026

This makes a lot of sense, especially since single product SKUs transmit correctly, suggesting the issue is specific to how variant data is handled in the loop.

The "Masked Bug" and Truncated SKU Length

Manfred also suggested that Marketplace Connect might be internally masking the bug. When it tries to transmit the same parent SKU for multiple variants, it likely detects duplicates and automatically adds an index (e.g., 12600(1), 12600(2)). The app might then think it successfully transmitted unique SKUs, even though these indexed SKUs are generated by MC, not by Shopify, and don't correspond to the actual variant SKUs.

Furthermore, the obvious truncation of SKUs (9 digits expected vs. 5 digits transmitted) should have been an immediate red flag for any validation check. This point, Manfred noted, was consistently overlooked by support.

The Frustrating Support Experience and What We Can Learn

Manfred's journey through support is a powerful lesson for all of us. Despite providing exhaustive documentation, screenshots, timelines, and technical analysis, he faced:

• Generic, unhelpful advice (like "unlink/relink" or "relist," which he'd already tried).
• Statements that were "demonstrably false" regarding SKU transmission.
• Long periods of silence (17 days at one point).
• Deflection of responsibility (e.g., for EANs).

He repeatedly asked for a simple code comparison before and after May 10, 2026, or a rollback, which he believed would quickly identify or fix the issue. These requests, however, seemed to go unaddressed for weeks.

What You Can Do If You're Affected

If you're using Shopify Marketplace Connect to sell multi-variant products on eBay, here's what you should take away from Manfred's experience:

1. Actively Monitor Your Listings: Regularly check your eBay listings for multi-variant products. Verify that the SKUs displayed on eBay for each variant match the specific variant SKUs in your Shopify admin. Don't assume everything is syncing correctly.
2. Document Everything: If you find discrepancies, start a detailed log. Note dates, specific SKUs (parent and variant), order numbers, and screenshots. This level of detail, as Manfred showed, is crucial when engaging with support.
3. Be Specific in Support Tickets: Clearly articulate the problem, provide your documentation, and if you have a technical hypothesis, share it. Emphasize the impact (e.g., overselling risk).
4. Push for Escalation: If initial support isn't getting you anywhere, don't hesitate to request escalation to a specialist or the engineering team. Referencing community discussions or app reviews where others report the same issue can strengthen your case.
5. Consider Workarounds (Temporarily): While not ideal, Manfred had to manually adjust inventory after every eBay sale. If you're facing this bug, you might need to implement similar temporary measures to prevent overselling until a fix is deployed.
6. Demand Transparency: It's fair to ask for an explanation of what has been investigated and a timeline for a fix, especially when a critical bug impacts your business for an extended period.

This whole situation underscores the importance of reliable integrations when running an e-commerce business. While Shopify provides an incredible platform for merchants to start and grow their stores, issues like this remind us to stay vigilant. If you're considering starting your own online journey, remember that choosing the right platform and understanding its integrations is key. You can explore options and get started with Shopify here: Start Your Shopify Store.

Manfred's persistence in the face of this critical bug is truly commendable. It's a stark reminder that even with robust platforms and apps, sometimes things go wrong, and it's up to us, the merchant community, to highlight these issues and push for solutions. I'll be keeping an eye on this thread and similar discussions, and I encourage anyone else experiencing this variant SKU bug to speak up in the community. The more voices, the better the chance of a swift resolution!