Skip to main content

Why does the sync process take so long?

Big catalogs + long sales history = longer first sync. Forecasts show once data import finishes.

Paolo Caneparo avatar
Written by Paolo Caneparo
Updated over 2 weeks ago

What the sync actually does

When you connect channels and locations in onboarding, Rewize pulls: products (SKUs), on-hand stock, sales history, and other data needed for forecasts, health labels, and purchase planning. Forecasts only appear after sales data finishes importing.

Why it can take longer

  • Catalog size: More SKUs = more product + inventory records to import.

  • Sales history depth: Longer history (months/years) extends processing time.

How to check progress

  • Refresh the app after a few minutes; large imports can take minutes to hours depending on SKU count and history.

  • Review onboarding steps, ensure channels, locations, and suppliers are fully added so nothing is stuck waiting for required mappings.

  • Spot partial data? Some SKUs may load before all history is processed.

What you can do while waiting

  • Finish Supplier assignments, Ignore non-tracked SKUs, and set Lead times / MOQs so forecasting is ready the moment data lands.

  • Configure Health label logic and ABC rules in Settings.

When to contact us

If data still hasn’t appeared after a reasonable window (e.g., you expect many thousands of SKUs and it’s been hours), ping us in the in-app chat. We’ll check the sync queue.

Did this answer your question?