Why Are My Product Variants Not Syncing Correctly to Faire?
Why variants may not sync correctly to Faire
Variants usually go wrong because the product record is not as clean as it looks. A shirt with Small, Medium, and Large in your OpoShop store can turn into a partial Faire listing if one size is missing required data, if the option structure changed after sync, or if Faire already has an older manual version of that product.
Another common issue is selective sync. A merchant wants only part of the retail catalog available to wholesale buyers, sets product rules carefully, then later forgets that one color or style was excluded on purpose. At that point, the missing variant looks like a sync bug even though it is really a sync setting.
Pricing and stock can also make a variant look broken when the actual problem is different. If wholesale pricing is not set up the way you expect, or if inventory is shared differently across retail and wholesale, the listing can appear incomplete even though the variant exists.
If some products already exist on Faire, review how manually created listings affect sync before you keep chasing the wrong issue.
What does product variant syncing to Faire mean?
Product variant syncing to Faire means keeping each version of a product aligned between your OpoShop catalog and your Faire wholesale listing. If you sell one candle in 8 oz and 16 oz sizes, or one tote in black, olive, and sand, each option needs to carry over with the right title, option values, price, and stock.
That sounds simple. It is simple. But only if one system is clearly in charge.
In a clean setup, your OpoShop product acts as the source record. Faire Sync reads the product, sends the matching variants to Faire, and keeps wholesale-facing information in line with the retail catalog where that makes sense. Wholesale buyers then see the correct versions instead of a half-built listing.
A lot of confusion starts because merchants use the word "variant" to describe different problems. Sometimes the variant is truly missing. Sometimes the variant is there, but the wholesale price is wrong. Sometimes the stock count is off. Those are related problems, but they are not the same problem.
Here is a simple before-and-after way to think about it:
Weak: "My blue mug variant is not syncing." Stronger: "My 12 oz blue mug exists in OpoShop, but Faire only shows the 16 oz blue mug and the 12 oz white mug. The missing variant has a different option structure and no wholesale price."
That second version gives you something you can actually troubleshoot.
Why correct variant syncing matters for OpoShop merchants selling wholesale
Correct variant syncing matters because wholesale errors cost more time and trust than retail errors. If a retail shopper sees the wrong color, that is one bad product page. If a wholesale buyer places a case order for the wrong variant, you now have a catalog issue, a stock issue, and a fulfillment problem tied together.
The money side gets messy fast. Picture a product with four variants priced at $24 retail, with a $12 wholesale price for approved items. If Faire shows only three variants, or shows one variant at the wrong wholesale price, a buyer can order against a catalog that does not match your actual offer.
The work side gets worse too. A lot of merchants add Faire to save time, not create a second catalog job. If you are fixing titles, prices, and stock counts manually on Faire every week, the whole point starts to disappear.
For OpoShop merchants, this matters even more when retail and wholesale move at different speeds. A fast retail weekend can change stock on Monday morning. If Faire is still showing stale inventory for the same size or color, you can end up selling units you no longer have or hiding units you do have.
How to troubleshoot product variants that are not syncing correctly to Faire
The fastest way to troubleshoot product variants not syncing correctly to Faire is to check product structure first, then listing history, then sync rules, then pricing and inventory behavior. Most merchants start at the wrong end and lose an hour chasing stock counts before noticing that one option value changed from "Small" to "S".
1. Check the product record in OpoShop
The first check is the product itself. If one variant is missing on Faire, open the product in OpoShop and compare every option value line by line.
Look for small changes that create big headaches:
- Option names changed: "Size" became "Sizes" or "Color" became "Colour."
- Option values changed: "Small" became "S" after the first sync.
- One variant is inactive: the product looks complete, but one variant is not available the same way as the others.
- SKU gaps: one variant has blank or inconsistent identifying data.
A merchant selling a tee in 5 sizes and 3 colors has 15 variants. If 14 are built one way and 1 is built another way, that lone variant is usually the problem.
2. Check whether the product was created manually on Faire
Manual Faire listings often explain inconsistent variant behavior. If you built a product on Faire first, then later connected Faire Sync, Faire may already have a listing structure that does not match the current product in OpoShop.
That is where merchants get tripped up. They assume the app is creating a fresh listing, but Faire is often dealing with an existing record. If the manual listing has two color options and the synced product has three, the result can look random even when the real issue is duplicate catalog history.
If some products already exist on Faire, it helps to sort that out before you keep editing titles and prices.
3. Check title and option changes after the first sync
Title and option changes after the first sync can affect existing Faire variants because the listing relationship has already been established. A simple title edit is usually easier to manage than a structural option change, but both deserve a quick review.
A title change from "Classic Tee" to "Classic Pocket Tee" is one thing. Changing a product from one option set to two option sets is different. If you started with Size only, then later added Color plus Size, Faire may need a closer review because the variant map is no longer the same shape.
4. Check whether the issue is really pricing or inventory
A lot of "missing variant" reports are really pricing or inventory mismatches. The variant exists, but the wholesale price is blank, the stock count is not what you expected, or the listing is behaving differently across channels.
Use a concrete test. If your retail catalog shows 20 units of the black medium hoodie and Faire shows 0, ask a narrow question: is the black medium hoodie absent, or is the inventory behavior different? If retail is $48 and wholesale should be $24 but Faire shows another number, the catalog may be syncing while pricing rules need attention.
Best ways to manage variants on Faire: manual updates vs synced workflow
A synced workflow is usually cleaner than manual Faire updates because one catalog stays in charge. Manual updates can work for a tiny wholesale catalog, but they break down fast once products have multiple sizes, colors, or style combinations.
Here is the tradeoff in plain terms:
| Workflow area | Manual Faire updates | Mixed manual + sync | Synced OpoShop workflow |
|---|---|---|---|
| Product edits | Entered separately on Faire | Some edits in both places | Managed from one source |
| Variant accuracy | Easy to drift over time | Most likely to create conflicts | More consistent if catalog is clean |
| Pricing and inventory review | Manual checking every time | Hard to tell which system won | Easier to audit and repeat |
The middle option is usually the roughest. A merchant adds products manually on Faire, later syncs from OpoShop, then keeps making small edits in both places. That setup creates the exact kind of "why is one color missing?" problem this article is about.
Manual work also gets expensive in time. Ten products with four variants each is already 40 variant records to watch. At $18 wholesale on one item, $22 on another, and different stock counts after a retail sale, the room for mistakes grows fast.
Common mistakes that cause variant sync problems
Most variant sync problems come from a handful of repeat mistakes. The frustrating part is that each one looks technical at first, even when the real issue is catalog discipline.
Here are the ones we see most often:
- Editing listings in multiple places: a merchant updates a title on Faire, changes option values in OpoShop, and then wonders why the records no longer line up.
- Starting with incomplete product information: one size has a full setup, another size is missing part of the data, and only the complete variants appear as expected.
- Changing option structure after sync: renaming or rebuilding options after the first sync can leave the wholesale listing out of step with the retail catalog.
- Mixing retail-only and wholesale products without clear rules: some variants are meant to stay out of Faire, but nobody documents that decision, so later it looks like a sync failure.
- Confusing inventory behavior with catalog behavior: the product exists, but the stock count or wholesale price makes it look missing.
The honest answer is that most of these are process issues before they are app issues. If one candle scent is edited in one place and one jar size is edited somewhere else, no sync setup will feel predictable.
If you are still setting up your catalog, it is worth slowing down before the first sync. Clean product records save a lot of cleanup later.
What we recommend before and after syncing variants to Faire
The best setup is simple: use OpoShop as the source of truth, test with a small SKU set first, decide what belongs on wholesale, and review the first synced listings before you scale the whole catalog. That keeps the work manageable and makes it much easier to spot where a problem actually starts.
Start with 3 to 5 products, not 85. Pick products with clear size or color structures, such as a mug with 2 sizes, a shirt with 4 sizes, or a candle with 3 scents. If those sync cleanly, you have a pattern you can trust.
Before the first sync, make sure each product answers a few plain questions:
- Is the option structure final enough to sync? Constant option changes create avoidable cleanup.
- Does this belong on wholesale? Not every retail product should go to Faire.
- Do wholesale prices make sense? A $30 retail item with a $15 wholesale price needs to be intentional, not accidental.
- How should inventory behave? Shared stock needs to be understood before buyers start ordering.
After the first sync, review the actual listings on Faire instead of assuming everything carried over perfectly. Check one product title, one option set, one price, and one stock count by hand. That five-minute check catches a lot.
If you want a cleaner way to manage retail and wholesale without duplicate product work, this is exactly where Faire Sync helps. The point is not to create more systems. The point is to stop babysitting two catalogs.
Best answer: Treat your OpoShop catalog as the single source of truth, keep manual Faire edits to a minimum, and test a small group of variant-heavy products before syncing the rest. If one variant is missing on Faire, check product structure first, then existing manual listings, then sync rules, then pricing and inventory behavior. That order saves time because it finds the real cause faster.
FAQs
Why is one variant syncing to Faire but another is missing?
One variant is usually missing because the product data is not identical across all variants. Check option names, option values, SKU setup, product status, and whether that specific variant is included in your sync rules.
Do manually created Faire listings cause variant sync problems?
Yes. Manually created Faire listings can create conflicts if the existing Faire structure does not match the current product structure in your OpoShop catalog. That is one of the first things to review when synced and manual listings overlap.
Will changing product details in OpoShop affect existing Faire variants?
Yes. Changing product details in OpoShop, especially titles, option names, or option structure, can affect how existing Faire variants appear after sync. Small title edits are usually easier to manage than rebuilding the option structure after the product is already live.
Can I sync only selected products or variants to Faire?
Yes. You can choose which products belong on Faire and keep other products retail-only. If a product seems missing, double-check selective sync settings before assuming the variant failed to sync.
How do I troubleshoot variant pricing and inventory mismatches?
Start by confirming the variant actually exists on Faire, then compare the wholesale price and stock behavior against the product record in your OpoShop store. A pricing or inventory mismatch often looks like a missing variant even when the catalog record is present.
What should I check before my first catalog sync to Faire?
Check product titles, option names, option values, SKU consistency, wholesale pricing, and inventory expectations before the first sync. It is also smart to decide which products should stay retail-only so selective sync does not surprise you later.
Want a simpler way to manage retail and wholesale without duplicate catalog work?
