Shopify Marketplace Connect & eBay: Decoding the Variant SKU Sync Disaster

Hey everyone,

As a Shopify migration expert and someone who keeps a close eye on our community discussions, I often see incredibly detailed problem-solving happening right there in the forums. Recently, a thread caught my attention that really highlights the frustrations and critical impact of integration bugs, especially when it comes to something as fundamental as inventory management. We're talking about a serious issue with Shopify's own Marketplace Connect app and how it handles variant SKUs when syncing with eBay.

A store owner, Manfred Kraus (lonewolf in the forums), brought to light a persistent and critical bug that's been causing a major headache for his multi-variant products on eBay since May 10, 2026. And he's not alone; another merchant confirmed the exact same problem. If you're using Marketplace Connect to list products with variants on eBay, you absolutely need to pay attention to this.

The Core Problem: Parent SKU vs. Variant SKU

Manfred's detailed account laid it all out: for multi-variant products, Marketplace Connect started transmitting only the parent SKU (e.g., 12600) to eBay instead of the unique, 9-digit variant SKU (e.g., 126002101). This might sound like a small detail, but it completely breaks inventory management. Imagine selling a "blue large" shirt, but your system only registers a sale against the generic "shirt" SKU. Chaos, right?

This bug leads directly to a massive overselling risk because eBay's inventory isn't being updated correctly for individual variants. Manfred documented seven affected orders within days of the bug appearing, and despite weeks of back-and-forth with support, the issue remained unresolved for over 45 days.

Manfred's Technical Deep Dive: What's Going On?

What's truly impressive is Manfred's persistence and his own technical analysis, which offers crucial insights into the potential root cause. He believes the app is reading the wrong variable for variant SKUs, likely receiving an empty value. When this happens, the app seems to fall back to the parent SKU.

Here's a simplified breakdown of his hypothesis:

Shopify Data Variable recognized by MC Value read Transmitted to eBay
Single product SKU :white_check_mark: YES Shopify SKU Shopify SKU
Variant SKU 1 :cross_mark: NO (empty) Parent SKU (fallback)
Variant SKU 2 :cross_mark: NO (empty) Parent SKU (fallback)
Variant SKU 3 :cross_mark: NO (empty) Parent SKU (fallback)

He even suggested a possible cause: a change in the variable name used to access variant SKUs in Shopify's API or Marketplace Connect's code around May 10, 2026. This would cause the app to look for a variable that no longer exists or is empty, triggering the fallback logic.

Adding to the mystery, Marketplace Connect seems to be internally masking the bug by adding an auto-incrementing index (e.g., 12600(1), 12600(2)) to the parent SKUs it transmits. This makes the system think it's sending unique SKUs, even though they're not the correct Shopify variant SKUs. Plus, the transmitted SKUs are often significantly shorter (5 digits) than the actual Shopify variant SKUs (9 digits), a clear red flag that should have been caught by basic validation.

Workarounds That Didn't Work

Manfred tried several suggestions from support, including unlinking and relinking products, and even relisting them entirely. Unfortunately, these workarounds proved ineffective, with eBay still showing the incorrect parent SKUs after each attempt. This confirms the bug is deeply rooted in the app's transmission logic.

The only current "solution" for affected merchants is manual inventory adjustment after every eBay sale with variants – a time-consuming and error-prone process that completely defeats the purpose of an automated integration.

Are You Affected? What to Do Now

If you're using Shopify Marketplace Connect to sell multi-variant products on eBay, here's what you should do:

  1. Check Your eBay Listings: Go to your eBay listings for products with multiple variants. Verify that the SKUs displayed for each variant match your specific Shopify variant SKUs, not just the parent product SKU. If you see truncated SKUs or parent SKUs with appended numbers (like 12600(1)), you're likely affected.
  2. Monitor Inventory Closely: Until a fix is deployed, you'll need to manually adjust inventory on eBay after each sale of a variant product. This is critical to prevent overselling.
  3. Document Everything: Take screenshots of your Shopify variant SKUs and the corresponding (incorrect) SKUs on eBay. Keep a clear timeline of when the issue started for you and any support interactions. The more detail you have, the better.
  4. Contact Shopify Support: When you reach out, reference this known issue. Explain that Marketplace Connect is transmitting parent SKUs instead of variant SKUs for multi-variant products, leading to inventory sync failures and overselling risk. Provide your detailed documentation.
  5. Advocate for a Code-Level Fix: Like Manfred, emphasize that this appears to be a bug in the app's transmission code. Request that the engineering team investigate a potential variable name change around May 10, 2026, and consider a rollback to a previous, working version of the app if possible.

Manfred also observed inconsistent behavior on the "return path" (how sales data is sent back to Shopify), suggesting there might be two separate bugs at play – one for outgoing transmission and one for incoming data. This further complicates things and underscores the need for a thorough investigation by the development team.

It's frustrating when critical tools don't work as expected, especially when it impacts your bottom line and reputation. The community's detailed feedback, like Manfred's, is invaluable in pushing for these fixes. Let's hope Shopify's engineering team can quickly pinpoint the exact variable causing the issue and implement a robust solution. Accurate SKU syncing is the backbone of multi-channel selling, and we need our tools to be reliable.

Share:

Use cases

Explore use cases

Agencies, store owners, enterprise — find the migration path that fits.

Explore use cases