What Should I Do if a Synced Product Is Wrong on Faire?
Start by checking where the wrong data originated
The fastest fix is to stop looking at the whole product and isolate the one field that is wrong.
A lot of sync problems feel bigger than they are. A merchant opens Faire, sees a bad listing, and assumes the entire product is broken. Usually it is not. Usually one piece is wrong: the wholesale price is off by $4, one variant says "Blue / Large" when it should say "Navy / Large," or inventory on Faire still shows 18 units after 6 retail sales happened in OpoShop.
Start with a simple check:
- Title: Is the product name wrong on Faire, or just different from your OpoShop product?
- Description: Is wholesale copy outdated even though retail copy is current?
- Variant mapping: Is one size, color, or SKU attached to the wrong option?
- Price: Is the wholesale price using the wrong value or the wrong rule?
- Inventory: Is stock wrong across the whole product, or only on one variant?
That first pass tells you where to look next. It also keeps you from making random edits in both places, which is how a small mismatch turns into a messy one.
If you want a cleaner sync setup before problems stack up, this is a good point to tighten the workflow.
What counts as a "wrong" synced product on Faire?
A wrong synced product on Faire is any listing where the wholesale version does not match the product data you intended to send.
That can show up in obvious ways, like the wrong title or the wrong photo. It can also show up in quieter ways that cause bigger trouble later, like a variant mapped to the wrong SKU or a wholesale price that looks fine at a glance but is actually pulling the wrong amount.
Common examples include:
- Wrong title: Faire shows "Cedar Candle 8 oz" while your OpoShop product now says "Cedar + Smoke Candle 8 oz."
- Wrong images: Faire still shows an old lifestyle image set after your retail product was updated.
- Wrong variant details: The retail product in OpoShop looks correct, but Faire shows the wrong scent, color, size, or case pack on one variant.
- Wrong wholesale pricing: Your retail item sells for $24, but the Faire listing shows a wholesale price that does not match the pricing setup you expected.
- Wrong inventory counts: OpoShop shows 12 units left, while Faire still shows 20.
- Wrong product match: A product created manually on Faire was later connected to a synced workflow, and now no one is fully sure which record should be edited.
That last one causes more confusion than people expect. If a listing began life as a manual Faire product and only later got tied into a sync process, the listing may carry old settings or edits that do not line up cleanly with your store record.
Here is the simple test: if a wholesale buyer sees details on Faire that you would not want them ordering from, the synced product is wrong.
Why this matters when you sell retail in OpoShop and wholesale on Faire
Wrong product data matters because one bad field can create buyer confusion, pricing mistakes, and extra manual work across both channels.
Retail and wholesale do not break in the same way. A retail customer in OpoShop might abandon a product page if the title or image feels off. A wholesale buyer on Faire might place a larger order based on wrong case quantities, wrong variant details, or the wrong wholesale price. The stakes are different, and the cleanup is usually slower.
A few real-world consequences show up fast:
- Buyer confusion: A retailer thinks they are ordering the matte black mug, but the variant on Faire is tied to gloss black.
- Pricing errors: A product priced at $18 retail should wholesale at $9, but Faire shows $12. That changes margin expectations for the buyer and can stall the order.
- Overselling risk: Inventory on Faire says 30 units are available, but OpoShop already sold 14 units at retail.
- Double entry work: You fix the title in Faire, then fix the description in your store, then forget which version should win next time.
That last part is the trap. Most merchants add Faire because they want wholesale without duplicate data entry. If every mismatch turns into two edits in two systems, the whole setup starts working against you.
If the issue feels inventory-related, read how to keep retail and wholesale stock aligned across both channels: how to keep inventory in sync across retail and wholesale
How to troubleshoot a wrong synced product on Faire step by step
The cleanest troubleshooting flow is to identify the exact mismatch, compare both records, check for manual overrides, and then resync from the right source.
1. Identify the exact field that is wrong
A vague note like "the product is wrong" slows everything down. A precise note speeds everything up.
Write the issue in one line. "Variant 'Small / Sage' shows the photo for 'Medium / Olive.'" Or: "Faire shows wholesale price as $14, but expected price is $11." Or: "Faire inventory shows 22 units, OpoShop shows 9."
Weak: "The listing looks off." Stronger: "Only the 'Amber 4 oz' variant is wrong on Faire. Title and description match, but the wholesale price shows $8 instead of $6."
That level of detail tells you where the sync likely broke.
2. Compare Faire against the source product
Open both records side by side and compare field by field. Do not trust memory here. Memory is how people swear the product was right yesterday and then lose 30 minutes chasing the wrong issue.
Check:
- Product title
- Description
- Images
- Variant names and option values
- SKUs
- Wholesale price
- Inventory count
If only one variant is wrong on Faire, spend most of your time on variant mapping and SKU setup. Single-variant issues are usually not a whole-product problem.
3. Check whether Faire was edited manually
Manual edits on Faire can explain why product information is different on Faire than in OpoShop.
This is the part many merchants skip because they assume sync means one-way control from the store. But if a title, description, or variant detail was edited directly in Faire after the listing was connected, you can end up with a mismatch that looks random but is not random at all. It is just two records fighting.
A good question to ask is: was this product originally created manually on Faire? If yes, be extra careful. Older manual setup choices can still shape what you are seeing now.
4. Confirm pricing logic and inventory behavior
Price and inventory often look like one problem even when they are two separate ones.
A title can sync one way, inventory another way, and wholesale pricing through its own rule set. So if the title and description look right but the wholesale price is wrong, do not assume the whole sync failed. Check the pricing setup by itself. The same goes for inventory after retail sales in OpoShop. A stock mismatch does not automatically mean the product mapping is wrong.
If you are troubleshooting repeated mismatches and want a simpler process, this is where a dedicated sync workflow helps.
What is the best way to fix the issue: update the source of truth or patch Faire manually?
The safer long-term fix is usually updating the source of truth, while manual patching in Faire only makes sense for a one-time exception.
Here is the decision in plain English. If the product should stay consistent across retail and wholesale, fix it in your OpoShop store and let the sync carry the right value over. If the issue is a one-off wholesale exception that should live only on Faire, a manual edit can be fine, but only if you know it will not be overwritten later.
| Fix approach | Best for | Watch out for |
|---|---|---|
| Update the product in OpoShop | Titles, descriptions, images, standard variants, and any product data that should match your main catalog | Future syncs can overwrite manual Faire edits, so the store record should be the clean version |
| Edit the listing directly in Faire | One-time wholesale-only exceptions, buyer-facing notes, or temporary adjustments you do not want in retail | Manual changes can create confusion later if someone assumes OpoShop still controls that field |
| Use a small test resync first | Products with messy history, manual Faire origins, or variant issues affecting only 1 SKU out of 12 | Resyncing without checking the source can repeat the same mismatch |
A quick example makes this easier. Say your ceramic planter sells for $36 retail in your store. You expected the wholesale price on Faire to show $18, but it shows $22. If your wholesale pricing is supposed to come from the store-side setup, fix the source record there. If you only patch Faire to $18 and leave the store record untouched, the next sync may put the wrong number back.
Manual patching feels faster. Sometimes it is. But if you keep doing it, you end up maintaining two catalogs instead of one.
What common mistakes cause synced product issues?
Most synced product issues come from editing both systems, missing variant details, or assuming every field syncs the same way.
The first mistake is trying to fix the same product in two places at once. You update the title in Faire, someone else updates the product in OpoShop, then the next sync leaves everyone wondering which version should win. That is not a product problem. That is a process problem.
Other common mistakes show up all the time:
- Overlooking variants: The parent product looks right, but one SKU has the wrong option value or image.
- Assuming price and inventory behave the same: They often follow different sync rules.
- Ignoring product history: A listing created manually on Faire may not behave like one that started in your store.
- Skipping a side-by-side check: People trust what they remember instead of comparing actual values.
- Fixing the symptom only: A merchant patches one bad Faire field but never corrects the source record.
You can see this in a simple scenario. A candle product has 8 variants. Seven are correct. One variant on Faire says "Sea Salt" but should say "Driftwood." If you only update the visible label and never check the SKU mapping, the same bad match can return later.
That is why the issue is not just "how do I fix this listing?" The better question is "how do I stop this exact mismatch from coming back?"
What do we recommend for OpoShop merchants using Faire Sync?
We recommend keeping OpoShop as the main product source, limiting manual overrides in Faire, and testing fixes on a small set of SKUs before touching the whole catalog.
That approach is boring in the best way. It gives you one place to maintain titles, descriptions, images, variants, and stock logic. It also makes troubleshooting much faster because your team knows where to look first.
A practical workflow looks like this:
- Keep one source of truth: If the product belongs in your retail catalog, maintain the clean record in your OpoShop store.
- Use manual Faire edits sparingly: Save them for true wholesale-only exceptions.
- Test with 3 to 5 SKUs first: If one mug, one candle, and one apparel item sync cleanly, broader sync work gets much easier.
- Use a repeatable checklist: Check field, compare records, review manual edits, confirm variants, confirm price, confirm inventory, then resync.
- Document odd cases: If a product started manually on Faire, mark that clearly so no one guesses later.
If you are still early in setup, review what to check before your first catalog sync to avoid product mismatches: what to check before your first catalog sync to Faire
Best answer: Keep your store record clean, treat your OpoShop catalog as the source of truth for standard product data, and use manual Faire edits only when you truly need a wholesale-only exception. That gives you a fix that holds up the next time products, prices, or inventory change.
If you want a cleaner wholesale workflow, this is the next step.
FAQs
Should I edit the wrong product in OpoShop or in Faire?
Edit the wrong product in OpoShop if that product data should stay consistent across retail and wholesale. Edit directly in Faire only for a true one-off wholesale exception that you do not want synced back from the store.
Why are my product variants not syncing correctly to Faire?
Variant sync problems usually come from mismatched option values, SKU issues, or an older Faire listing that was edited manually. If only one variant is wrong on Faire, compare that single variant's SKU, option name, and option value against the store record before changing anything else.
What happens if I change a product title in OpoShop after it is listed on Faire?
If the title field is part of your sync behavior, changing the product title in OpoShop should update the Faire listing on the next sync. If Faire was edited manually or the listing has older setup history, check the result after syncing instead of assuming the new title will win.
Can I sync price changes from OpoShop to Faire without republishing everything?
Yes, price changes can usually be handled without rebuilding the full catalog, as long as the product connection is already in place and pricing is set to sync from the store record. If the wholesale price on Faire still looks wrong, check the pricing rule before republishing the product.
Why is my Faire inventory not matching my OpoShop stock?
Faire inventory usually stops matching OpoShop stock when inventory sync rules, variant mapping, or timing of updates are off. Start by checking whether the mismatch affects the whole product or just one SKU, because a single-variant stock issue points to a different fix than a full-product inventory gap.
What happens if I already edited the product manually on Faire?
Manual Faire edits can stay in place, get overwritten, or create confusion, depending on which fields are controlled by the sync. If a product was already edited manually on Faire, compare every changed field against the store record before you resync so you do not erase the wrong thing.
A cleaner wholesale setup starts with a cleaner source of truth.
