Can I Pause Syncing During a Big Launch or Inventory Count?
Yes, but only with a clear plan
Yes, pausing syncing is a reasonable move during a launch or inventory count if you know what you are freezing, for how long, and what needs to be checked before you resume.
That part matters more than people expect. A pause can protect launch-day inventory from bouncing around while retail orders come in fast. A pause can also give you a clean window to count shelf stock without wholesale availability changing underneath you.
But the pause is not free. If inventory syncing is paused, stock levels on Faire stop reflecting live changes from your OpoShop store. If product or price syncing is also paused, those updates will wait too.
If your main concern is keeping retail and wholesale stock aligned during busy periods, this is where a cleaner workflow helps.
What does pausing syncing mean for an OpoShop and Faire workflow?
Pausing syncing means temporarily stopping updates between your OpoShop store and Faire so you can make controlled changes without live data moving back and forth.
In plain terms, that can mean stopping inventory updates, product updates, pricing updates, or all three, depending on how your setup works. During the pause, Faire keeps showing the last synced version until you resume and send fresh data again.
That sounds small, but it changes how you need to think for the next few hours. If a candle set has 42 units in OpoShop when you pause, Faire may keep showing 42 even if retail sales bring the real count down to 19 before lunch.
A lot of merchants hear "pause syncing" and think "nothing changes anywhere." That is not the situation. Orders can still happen. Stock can still move. The sync is what stops, not the business.
- Inventory pause: Stock changes in your store do not flow to Faire.
- Product pause: Title, images, variants, or descriptions changed in your store do not update on Faire.
- Pricing pause: Retail-side edits tied to wholesale pricing rules do not refresh on Faire until syncing resumes.
- Full pause: You freeze all synced changes for a short window while you manage a launch or count manually.
Why can pausing sync matter during a launch or inventory count?
Pausing sync matters because launches and physical counts are the two moments when inventory is most likely to change fast and least likely to be perfectly clean.
A retail launch is the obvious example. Say you drop a new ceramic mug at 10:00 a.m. with 120 units available in your OpoShop store. By 10:18 a.m., retail shoppers buy 37 units, your team adjusts 6 damaged pieces out of stock, and one bundle offer changes demand again. That is not a great moment to let wholesale buyers act on unstable numbers if the item is also listed on Faire.
Inventory counts create a different kind of risk. During a full-store recount, you are checking what is actually on the shelf, what is reserved, what is damaged, and what was mis-picked last week. If Faire is still receiving live stock while your team is halfway through counting SKU A-104, the number on screen can stop matching the number in the bin.
Wholesale timing makes this trickier. A Faire order that lands during a manual recount can pull from the same pool as your retail store. If the count is not finished, you are making decisions with half-clean data.
- Launch-day volatility: Stock can move in minutes, not hours.
- Manual recounts: Physical counts often uncover missing, damaged, or misplaced units.
- Shared inventory: Retail and wholesale may be pulling from the same SKU pool.
- Update lag risk: Faire can keep showing stale numbers during a pause if you leave the window open too long.
How do you handle a pause without creating inventory problems?
You handle a pause safely by narrowing the scope, finishing the work fast, and reconciling stock in OpoShop before you let Faire catch up.
Most problems do not come from the pause itself. They come from vague pauses. The whole catalog gets frozen, nobody writes down which SKUs were affected, a price gets changed mid-count, and then syncing comes back on with no final check. That is where the mess starts.
The cleaner approach is boring, and that is why it works.
1. Decide what actually needs to stop
Most merchants do not need a full-store freeze. Usually, only a small group of SKUs is risky: launch exclusives, low-stock products, or items being counted by hand in the back room.
A weak plan is "pause everything just to be safe." A stronger plan is "pause inventory syncing for 14 launch SKUs from 9:45 a.m. to 1:00 p.m., keep the rest of the catalog live, and hold product edits until after reconciliation."
Weak: "We'll just pause sync during the sale." Stronger: "We'll pause inventory updates for SKUs L-201 to L-214 during the noon drop, finish the count by 2:00 p.m., verify stock in OpoShop, then resume and confirm Faire matches."
2. Decide who is watching wholesale during the pause
Wholesale does not disappear because your team is focused on retail. Someone still needs to know whether Faire orders are coming in, whether a buyer has questions, and whether any product should be hidden from wholesale for the day.
This is the part people skip when the warehouse is busy. Then a wholesale order lands at 11:07 a.m., the count is still in progress, and nobody knows if the stock number is real.
3. Reconcile before you resume
The safest time to resume syncing is after final stock is confirmed in OpoShop, not when the team is "basically done." Close enough is where overselling starts.
If counted stock says 86, your reserved stock says 8, and 3 units are damaged, the number you want flowing to Faire is the corrected number after all three are accounted for. Do not restart first and clean up later.
If you want a simpler setup for these handoff moments, there is a reason merchants look for fewer manual touchpoints between retail and wholesale.
Is it better to pause syncing, keep syncing, or sync only selected products?
The best option depends on how many SKUs are unstable and how much risk you can tolerate during the event.
If one new collection is launching and the rest of your catalog is steady, selective syncing is usually the cleanest answer. If you are counting the entire warehouse and confidence in stock numbers is low across the board, a short full pause can make more sense. If inventory is stable and your count is limited to a few shelves after hours, keeping sync live is often fine.
Here is the practical tradeoff:
| Option | Best for | Main upside | Main risk |
|---|---|---|---|
| Full pause | Full-store count or major stock uncertainty | Gives your team one clean control window | Faire shows stale inventory across the catalog until sync resumes |
| Keep syncing | Stable stock and low-risk updates | Faire stays current with live changes | Fast-moving launch items can oversell if counts are wrong |
| Sync only selected products | Launch items, low-stock SKUs, or hand-counted products | Limits risk without freezing the whole catalog | Takes a little more planning up front |
Selective control usually wins because it matches the real problem. Most stores do not have 800 unstable SKUs. They have 12 launch items, 6 low-stock bestsellers, and 20 products sitting on a counting table.
That is why the question is often not "Should I pause inventory syncing before a product launch?" The better question is "Which products need protection, and which products can keep moving normally?"
What mistakes should you avoid when pausing sync during busy sales periods?
The biggest mistakes are broad pauses, rushed restarts, and forgetting that wholesale buyers are still part of the day.
The first mistake is pausing the whole catalog when only a few SKUs are sensitive. That creates more stale data than you need and gives you more to verify later. If 9 products are launching, do not freeze 900.
The second mistake is resuming before counts are final. "We are almost done" is not a stock number. If one staff member still has a tote of returns to sort or a shelf of damaged goods to mark out, inventory is not ready to sync.
The third mistake is changing prices during the pause without a written plan. If retail pricing changes in your OpoShop store while wholesale pricing rules are also in motion, it gets very easy to forget what should appear on Faire once updates resume.
A few more to watch:
- Ignoring wholesale visibility: Faire buyers can still act on what they see unless you intentionally limit affected products.
- Skipping SKU notes: If nobody records which items were paused, post-count cleanup takes longer than it should.
- Leaving the pause too long: A two-hour pause is one thing. A two-day pause creates stale inventory and stale pricing.
- Restarting blind: Turning sync back on without checking OpoShop stock first can push the wrong numbers straight into wholesale.
What do we recommend for most Faire Sync merchants?
For most merchants, the safest answer is selective control, short pause windows, and a final stock check in OpoShop before syncing resumes.
That recommendation is not glamorous. It is just the one that creates the fewest ugly surprises. If only launch items are unstable, keep the rest of the catalog syncing. If only counted SKUs are uncertain, limit your pause to those products. Save full-store pauses for short windows when the whole inventory picture is in flux.
This also answers a common concern: can you keep some products syncing while holding back launch items? In many cases, yes, and that is usually the cleaner move. You do not need to shut down healthy parts of the catalog just because one corner of inventory is moving fast.
The same logic applies to wholesale orders during a recount. If a product is under review, treat it like a product under review. Hold it back, finish the count, confirm the real number, then let Faire reflect the corrected inventory.
Best answer: Use the smallest pause that solves the actual problem. For most OpoShop merchants selling on Faire, that means limiting sync only for launch items, low-stock bestsellers, or hand-counted SKUs, then reconciling stock in OpoShop before turning updates back on. A short, deliberate pause protects control. A vague, long pause creates stale data.
If you want a cleaner way to manage retail and wholesale without so much manual checking during launches and counts, Faire Sync is built for exactly that handoff.
FAQs
What happens if I pause syncing and a product sells on OpoShop?
If syncing is paused and a product sells on OpoShop, Faire will not receive that stock change until syncing resumes. Faire keeps showing the last synced quantity, which is why pause windows should stay short and controlled.
Should I pause syncing for a full-store inventory count or just for certain SKUs?
Most of the time, pausing only certain SKUs is safer because it limits stale data to the products that are actually being counted or are at risk. A full-store pause makes sense when the whole inventory picture is uncertain and you need one clean counting window.
How do I know when it is safe to turn syncing back on?
It is safe to turn syncing back on after final stock is confirmed in OpoShop, damaged or missing units are accounted for, and any launch-day adjustments are finished. If the team is still correcting counts, it is too early to resume.
Can I prevent overselling without pausing syncing completely?
Yes. A selective pause, limited product visibility, or tighter handling for only the affected SKUs can reduce overselling risk without freezing the whole catalog. That is usually the better move when most products still have stable stock.
Will price changes made during the pause update later on Faire?
Price changes made during the pause will only appear on Faire after syncing resumes and those updates are allowed to flow again. That is why price edits during a pause need a clear plan, especially if retail and wholesale pricing are being adjusted on the same day.
How do I handle wholesale orders during a manual inventory recount?
Handle wholesale orders during a manual recount by checking whether the ordered SKUs are part of the count and whether their stock is confirmed. If the numbers are still in motion, hold those products back from wholesale activity until the recount is complete and OpoShop reflects the corrected stock.
If you want a simpler way to manage OpoShop and Faire during launches, counts, and all the messy in-between moments, start here.
