Can I Use the Same SKU on eBay and My Online Store?
What a Shared SKU Actually Does
A shared SKU turns two independent listings into two views of one product. Without it, your website and your marketplace listings are strangers that happen to look alike.
Every automated process between channels depends on that link. Stock syncing needs to know which eBay listing to update when quantity changes on a given product. Order import needs to know which product record to decrement when a marketplace order arrives. Channel profit reporting needs to attribute a sale to the right cost of goods.
All three of those use the SKU as the join key. Get it consistent and the automation is trivial. Get it inconsistent and every one of those processes needs a manual mapping table that somebody has to maintain forever.
On eBay the field is labelled custom label in the listing form and SKU in the bulk tools and APIs. It accepts letters, numbers and common separators, and it is not shown to buyers. For merchants running an OpoShop store, the simplest approach is to push your existing variant SKU straight into that field and never invent a second code.
The Rules a SKU Has to Follow
A SKU is an identifier, not a description. Most SKU problems come from treating it as the latter.
Four rules cover almost everything:
- One SKU, one variant: A size and colour combination is its own SKU. A parent product with five variants needs five distinct SKUs, not one.
- Never reuse a retired code: If a product is discontinued, its SKU retires with it. Reusing it later corrupts every historical report that referenced it.
- Stable for life: Do not change a SKU because packaging changed or the product moved supplier. Changing it breaks the link to every past order.
- Machine friendly: Stick to uppercase letters, digits and hyphens. Spaces, slashes and accented characters cause problems in files and integrations.
Length matters too, in a practical way. Very long SKUs get truncated in labels and reports, and very short ones run out of room as the catalogue grows. Somewhere between eight and eighteen characters suits most small businesses.
A workable pattern is category, product, variant. Something like TEE-OAKLEAF-BLK-L reads clearly on a picking list, sorts sensibly, and stays unique. Compare that to 12 or black large tee, both of which cause trouble within a year.
Where Merchants Get the Mapping Wrong
The same SKU on both channels sounds simple until variants and bundles get involved. Three situations cause most of the trouble.
The first is variant flattening. Your OpoShop store has one product with five sizes. On eBay you create five separate single-variation listings because they rank better individually. That is a perfectly reasonable choice, but each of those five listings needs the matching variant SKU, not the parent product code. If all five carry the parent SKU, a sale of any size decrements the same record and your stock goes wrong immediately.
The second is bundles. You sell a three-pack on eBay that does not exist as a product on your own site. It needs its own SKU, and that SKU needs a rule saying it consumes three units of the single-item SKU. Without that rule, bundle sales never reduce your real stock and you oversell the singles.
The third is multi-quantity listings. eBay lets a buyer purchase four units in one order. Your import has to reduce stock by four, not by one order. This sounds obvious and is a genuinely common source of drift on consumables.
None of these are exotic. They are simply the cases where one listing does not equal one unit, and each needs an explicit mapping decision rather than a hopeful assumption.
How to Align SKUs Across Both Channels
If your catalogue is already messy, fix it before you connect anything. Syncing an inconsistent catalogue just spreads the inconsistency faster.
Two of those steps need a closer look.
1. Treat your store catalogue as the authority
Decide up front that your product records are the master and eBay reflects them. That single decision resolves nearly every conflict you find in the spreadsheet, because whenever the two disagree the store wins.
The alternative, reconciling case by case, takes far longer and produces a catalogue nobody fully trusts. Working from the master catalogue in your OpoShop admin also means the fix only has to happen once rather than every time you add a channel.
2. Verify with real orders, not assumptions
After connecting, place a genuine test order on each channel. Watch the quantity in your catalogue before and after. Then place a multi-quantity order and confirm it moves by the right amount.
This ten minute check catches the two failures that hurt most, which are variant listings pointing at a parent SKU and multi-quantity orders decrementing by one. Both look completely fine until a busy week exposes them.
Shared SKU vs Prefixed SKU vs Separate Codes
There are three ways merchants handle identifiers across channels, and only one of them scales comfortably.
| Approach | How it works | Why merchants choose it | Watch-out |
|---|---|---|---|
| Identical SKU on both | The same code appears in your store and in the eBay custom label | Simplest possible mapping, syncing works with no translation layer | Requires a clean, variant-level catalogue to begin with |
| Prefixed marketplace SKU | The store SKU with a channel prefix such as EB added to it | Makes channel origin obvious at a glance on picking lists | Every integration needs to strip the prefix, and one that forgets breaks silently |
| Separate marketplace codes | eBay listings carry their own unrelated identifiers | Often inherited from a period of listing by hand | Needs a permanent mapping table that somebody must maintain forever |
Identical SKUs on both channels is the right default. There is no translation step, no prefix to strip, and any tool that reads either system sees the same code. Order matching and reporting work without configuration.
Prefixed SKUs feel tidy and cause more problems than they solve. The prefix carries information that the order record already holds, and every piece of software touching the data has to agree on the prefix rule. One that does not agree creates orphaned orders.
Separate codes are almost always an accident rather than a decision, usually the residue of hand-listing products before any syncing existed. The mapping table works until the day it is out of date, and it is out of date the first time somebody adds a listing without updating it. Cleaning this up is one of the highest value hours an OpoShop merchant can spend before scaling a second channel.
What Shared SKUs Unlock Once They Are Right
A consistent SKU across channels is not just tidiness. It is the precondition for four things you probably want.
Accurate stock syncing is the obvious one. A sale on either channel finds the right record and reduces the right number, in both directions, without a lookup table.
Channel profit reporting is the underrated one. With one SKU across both channels you can ask which products sell better on the marketplace, which ones carry different margins by channel after fees, and which ones should be delisted. Those questions are unanswerable when the same physical product wears two different codes.
Purchasing gets better too. Demand from both channels rolls up to one product line, so your reorder quantities reflect total demand rather than OpoShop demand plus a guess about the marketplace.
Fulfilment gets faster and less error-prone. Pickers see the same code on every pick list regardless of where the order came from, and the barcode on the shelf matches it. That is a real reduction in mispicks for anyone packing marketplace and website orders in the same session from their OpoShop order queue.
What We Recommend
Use the exact same SKU on eBay as in your store catalogue, at the variant level, with no prefixes and no exceptions.
Three rules make that stick:
- Your product catalogue is the authority. eBay listings inherit their custom label from it.
- Every variant, bundle and multipack gets its own distinct SKU with an explicit component rule.
- Retired SKUs stay retired. New products always get new codes.
If your existing codes are inconsistent, do the cleanup before you connect any syncing. An afternoon in a spreadsheet now saves months of order-matching failures that surface as mysterious stock drift later.
If you are starting fresh with a new OpoShop catalogue, choose a readable pattern and write it down somewhere your team can see. The specific format matters far less than everyone following the same one for the next five years.
Best answer: Yes, use the same SKU on eBay and your online store, matched at the variant level and stored in eBay's custom label field. Keep the catalogue in your OpoShop store as the single authority, give bundles their own codes with component rules, and never reuse a retired SKU. That one consistency is what makes stock syncing, order matching and channel profit reporting possible.
If your codes are already out of alignment, straightening them out is the fastest way to make multichannel selling behave.
FAQs
Does eBay require a SKU on every listing?
Not for every listing type, but you should always add one. The field is called custom label, it is hidden from buyers, and leaving it blank makes automatic stock syncing and order matching impossible for that listing.
Can two different products share one SKU?
No. A SKU must identify exactly one variant. Sharing a code between products means a sale of either one adjusts the same stock record, which produces wrong quantities on both almost immediately.
What SKU should a bundle or multipack use?
Its own unique SKU, plus a rule recording how many units of each component product it consumes. Without that rule, bundle sales never reduce the stock of the individual items and you end up overselling the singles.
Should I add a channel prefix like EB to marketplace SKUs?
Better not to. The channel is already recorded on the order, and a prefix means every tool touching the data has to strip it correctly. Identical codes across channels remove that whole class of failure.
Can I change a SKU after products are already selling?
Avoid it. Changing a SKU breaks the link to past orders, historical reports and any listing already carrying the old code. If a change is unavoidable, retire the old code and update every channel in the same session.
Do variants need separate SKUs on eBay?
Yes. Each size, colour or configuration needs its own code, whether it sits inside a multi-variation listing or in its own single listing. Pointing several variants at one parent SKU is the most common cause of stock going wrong.
Ready to run one clean catalogue across every channel you sell on? Start where your products already live.
