How Long Does a Sync Take in Orion?

Orion is designed to keep your Wix Store and Epos Now account aligned in real-time, but that doesn’t always mean “instant”.

This guide explains what actually happens during a sync, how long each step takes, and why timings may vary.

How Orion Syncs Your Products (The Real Flow)

Every time something changes in Epos Now (price, stock, barcode, product details) Epos sends an event to Orion.
Orion then processes each affected product individually and performs a full pass:

Step 1 — Update the Product in Orion

Orion calls Epos Now for the latest data:

• Product Name

• Price

• Inventory

• Modifier options

• Active/Archived status

• Settings (real-time stock/price sync toggles)

This updates the product record instantly inside your Orion dashboard.

Step 2 — Check if the Product is Linked to Wix

Orion checks whether the product is already linked to a Wix item.

If not linked:

• Tries to match barcode

• If barcode fails → tries SKU

• If still not linked → sync completes, but no Wix updates happen

Nothing breaks if a link is missing — the product will simply wait until it is linked.

Step 3 — Sync Stock & Price to Wix (only if linked)

If the product is linked and the relevant real-time settings are enabled:

• Stock is updated on Wix

• Price is updated on Wix

• Any failures are logged (Wix rate limits, variant errors, etc.)

This means one single event causes all 3 operations automatically.

So How Long Does a Sync Actually Take?

Real-Time – Normal Operation

Most product events complete in:

⭐ 2–10 seconds per product

This includes:

• Fetching data from Epos

• Checking links

• Updating stock

• Updating prices

• Logging the sync history

• Sending notifications

Why Isn’t It Instant Every Time?

Real-time sync depends on two external systems:

1. Epos Now Response Time

Sometimes Epos APIs are instant. Other times they temporarily slow down.

Common delays:

• Busy merchant accounts

• Large product catalogues

• Burst updates inside Epos

• Global Epos maintenance windows

If Epos delays sending data, Orion must wait.

2. Wix API Rate Limits

Wix processes thousands of merchant updates globally.
If Wix is busy, they may briefly return:

• 429 Too Many Requests

• Slower response times

Orion automatically retries in these cases, but it adds a few seconds.

Sync All — Timing Expectations

The “Sync All” button sends one big batch event to re-sync every product you have.

Typical timing depends on catalogue size:

Why?

Because each product is processed individually, and Orion guarantees:

• No duplicates

• No double-processing

• No overload of Wix or Epos

• Automatic retries

• Stale jobs automatically cleaned up

Even huge stores sync safely without timeouts or failures.

Why Are Timings More Predictable in Orion?

Unlike the old “Legacy” system:

❌ Legacy (Old System)

• Batch updates

• Velo limitations

• Manual flags

• Long delays

• Often took 30–60 minutes

• High failure rate during busy periods

✅ Orion (New System)

• Real-time pub/sub events

• No batching

• No Velo limits

• Fault-tolerant

• Automatic retry logic

• Job tracking & cleanup

• Full product pass on every event

This results in much smoother, more reliable and faster syncs.

How Do I Know My Sync Worked?

Orion provides visibility:

• Dashboard → shows overall health

• Notifications → tells you exactly what synced (stock, price, product, link, deletion)

• Product Viewer → shows real-time product state

• Progress tracking (for Sync All)

• Full job history (internal)

If something can’t sync (e.g., missing link), nothing breaks — Orion safely logs the reason.

Key Takeaways

• Most updates complete within 2–10 seconds

• “Sync All” is much faster and more reliable than the old system

• Orion runs entirely event-driven — not batched

• Stock and price syncs happen automatically whenever possible

• Delays are almost always caused by Epos or Wix being temporarily slow

Need help?

If your sync seems unusually slow, feel free to raise a ticket — we can check your logs in real time.

Click here to log a ticket