Shopify Marketplace Connect Bug: Variant SKUs Not Syncing to eBay – A Community Deep Dive

Hey everyone,

As a Shopify migration expert and someone who spends a lot of time sifting through community discussions, I often see recurring themes. One of the most frustrating is when a critical app integration, something you rely on daily, suddenly stops working as expected. It's not just an inconvenience; it can bring your operations to a grinding halt and, even worse, put your inventory at risk.

That's exactly what happened to Manfred Kraus, a store owner who recently shared a detailed, frankly exhaustive, account of a persistent bug with the Shopify Marketplace Connect app on the community forums. His experience, spanning over six weeks with no resolution, offers some incredibly valuable lessons for all of us dealing with app integrations and technical support.

The Variant SKU Nightmare: When Parent SKUs Take Over

Manfred's core issue, which started around May 10, 2026, was straightforward yet devastating: the Marketplace Connect app stopped transmitting the correct, unique variant SKUs from Shopify to eBay. Instead, it was sending only the 'parent SKU' for all variations of a product. Imagine having a t-shirt in S, M, L, XL, each with its own unique SKU in Shopify, but eBay only sees the generic 'T-shirt SKU' for all of them. Chaos, right?

Before May 10, Manfred confirmed that correct 9-digit variant SKUs were being transferred. But suddenly, orders like #2602334 and several others started showing only a 5-digit parent SKU, like 12600, on eBay. This isn't just a display error; it means inventory tracking is completely broken, leading to a massive overselling risk. Shopify would overwrite correct eBay stock levels after every sync, because it couldn't match the specific variant.

Manfred's Deep Dive: A Technical Analysis of the Bug

What struck me most about Manfred's posts was his incredible diligence in diagnosing the problem. He wasn't just reporting a bug; he was actively analyzing the likely technical cause. Here's a breakdown of his insights:

• The Missing Variable: Manfred hypothesized that the Marketplace Connect app was attempting to read a variable for variant SKUs that either no longer existed or had been renamed after a code change around May 10, 2026. When this variable returned an empty value, the app defaulted to the parent SKU. He even provided a clear table illustrating this:

  Shopify-Daten	Variable erkannt von MC	Ausgelesener Wert	Übertragen an eBay
  Einzelprodukt-SKU	JA	Shopify-SKU	Shopify-SKU
  Varianten-SKU 1	NEIN	(leer)	Eltern-SKU (Fallback)
  Varianten-SKU 2	NEIN	(leer)	Eltern-SKU (Fallback)
  Varianten-SKU 3	NEIN	(leer)	Eltern-SKU (Fallback)

• The Fallback Logic: He proposed the app's internal logic looked something like this:

  WENN Varianten-SKU vorhanden UND nicht leer:
      übertrage Varianten-SKU → eBay
  SONST:
      übertrage Eltern-SKU → eBay  ← Fallback aktiv seit 10. Mai 2026
  

• Automatic Index Generation: Manfred astutely noticed that Marketplace Connect might be internally masking the bug by adding an index (e.g., 12600(1), 12600(2)) when it detected duplicate parent SKUs. This made the app 'think' it was successfully sending unique SKUs, even though they weren't the correct Shopify variant SKUs.
• Ignored SKU Length Discrepancy: A crucial point Manfred raised was the difference in SKU length. His Shopify variant SKUs were 9 digits (e.g., 126002101), but eBay was receiving a 5-digit parent SKU (12600). He argued that a simple length check should have immediately flagged this as an error.
• Inconsistent Return Path: To add to the complexity, Manfred observed that while eBay consistently received the parent SKU, Shopify sometimes correctly received the variant SKU back for orders, and sometimes only the parent SKU. This suggested potentially two separate bugs: one for outgoing data, one for incoming.

He even explicitly asked the developers: "Welchen genauen Variablennamen verwendet Marketplace Connect um Varianten-SKUs auszulesen – und stimmt dieser noch mit dem Variablennamen überein den Shopify nach dem 10. Mai 2026 verwendet?" (Which exact variable name does Marketplace Connect use to read variant SKUs – and does it still match the variable name Shopify uses after May 10, 2026?) This is a brilliant, precise question that gets to the heart of the technical issue.

What This Means for Your Store & How to React

Manfred's experience highlights a few critical takeaways for any store owner using marketplace integrations:

1. Verify Your Syncs: Don't assume everything is working perfectly. Regularly spot-check your inventory and product data on connected marketplaces, especially for variant products.
2. Workarounds Are Limited: Manfred tried common workarounds like unlinking/relinking the product and even re-listing it entirely. Neither resolved the issue, as the underlying bug in the app's code persisted. This means manual inventory adjustments were necessary after every eBay sale, which is unsustainable for any growing business.
3. Document Everything: Like Manfred, keep meticulous records. Dates, order numbers, screenshots, detailed descriptions of expected vs. actual behavior – all of this is invaluable when dealing with support.
4. Escalate Smartly: If you're facing a similar, persistent bug, don't be afraid to escalate. Provide your own technical analysis if you can, referencing specific code behavior or data points. Emphasize the business impact (e.g., "overselling risk"). Mention if other merchants are affected, as this points to a systemic issue, not just an account-specific one. Manfred even suggested a dedicated test environment for the app developers and a code comparison before/after the bug started.

Manfred's journey, enduring 45+ days without a fix despite extensive documentation and multiple support contacts, underscores the frustration when critical integrations falter. He correctly pointed out that a rollback to the code version before May 10, 2026, could have immediately restored functionality while a proper solution was developed.

Ultimately, this case is a powerful reminder of the need for robust testing and responsive development for apps that are integral to a merchant's operations. If you're experiencing similar SKU synchronization issues with Marketplace Connect or any other app, take a page from Manfred's book: document, analyze, and push for a developer-level review. And definitely check your community forums – chances are, you're not alone!