Skip to content
Help Center

What happens while your data imports ​

After you start your setup, Commander imports your store in the background. Some pages need data that has not arrived yet. This page explains what you see in the wizard and on those pages, and what to do about it.

How long the first import takes depends on how many orders, products and customers your store has.

The three phases ​

Commander groups the import into three phases. The progress strip at the bottom of the setup wizard shows them.

PhaseWhat it covers
Account setupCommander creates your workspace, sets up your account and starts the product sync.
ImportingCommander reads your store data. The phase stays in progress while older order history keeps loading.
Generating insightsCommander works out what your data means.

The strip is closed by default. The summary line names the current work, for example Reading your store…. When everything is done, it reads Your store is ready. Click the summary line to open the strip.

Once Importing starts, a Show import detail link opens a short list. It shows Categories, Products, Customers and Orders — last 30 days. Each row reads Pending, In progress, Done or Failed. A bar shows how many items Commander has read so far.

The import keeps running in the background if you close the window.

The 30-day pass of orders comes first. Commander then imports your last 90 days of orders, and after that the rest of your order history. While this runs, an indicator on every page reads Importing your last 90 days of orders, and later Deepening your order history.

After the first import, Commander syncs your order and customer data once a day. Settings > Store Status shows each job. See Store Status.

What you can do meanwhile ​

Keep answering the wizard questions. No question makes you wait for the import. Progress appears beside your questions, not instead of them. See The setup wizard.

Some wizard steps use imported data. If the data has not arrived, Commander tells you and shows a fallback, for example your Shopify best sellers instead of a product ranking.

Pages that are not ready ​

Some pages need data that is still loading. Instead of an empty page, Commander shows one card. Its first line starts with Importing, names the main source the page waits on and shows how far it has got:

  • When Commander knows the total, it reads, for example, 2,500 out of 9,000, with a bar.
  • When it only knows the count so far, it reads, for example, 4,500 so far, with a moving bar.
  • When it knows neither, it reads Syncing.
  • It shows when the import started, for example Started 10:35. Commander never guesses how long it will take.
  • If the count has not moved for a while, it says so, for example Products and variants: no new rows since 10:42.

When the page waits on more than one source, the line says how many, for example Importing 3 sources · Products and variants · 2 more. Click Show details to see a row for each of the others.

Below, What you'll see here says what the page gives you once the data is in, with the page's blocks outlined. On some pages it adds the first line of an example from a sample store, marked Example; click See the full example to read it with its next steps. The last line names the connected sources, links any you can still connect, and has the Explore with demo data button. You can leave the page; the import keeps running.

If something the page waits on failed, or has not started, the page shows a panel titled Still preparing this view instead. The panel names what it waits for, such as your last 90 days of orders or the rest of your order history, and gives each part a status.

Some pages show a notice above their content instead of the panel. It starts with "We're still finishing" and names what is not ready, for example "your last 90 days of orders" or "the rest of your order history". It ends with "This section will fill in as more data arrives."

In the Still preparing this view panel, each row carries a status.

StatusWhat it means
Working on itCommander is making this part now.
Waiting on earlier stepsThis part needs another part first. The row usually names it.
QueuedThe work is lined up.
ScheduledEverything is in. It runs on the next scheduled pass.
Needs youSomething waits on an action from you. The text above the list says part of the work waits on something in the list. The same text appears when a row shows Not started.
Not startedThis part has not run yet. The row links to a page where you can fix the cause, for example Review your integrations.
Needs an active planThis part does not run for your store yet. The row links to View plans, and the Billing page shows your current plan.
Needs attentionSomething failed.
DoneThis part is ready.

The ad breakdowns row counts every ad Commander has analysed, your own and your competitors'. It reads Done once Commander has analysed at least one of them. Commander analyses new ads in the background after each ad sync, so the count grows by itself. Pages that build on your ad breakdowns wait for this row.

If every part a page needs has failed, the title changes to This view can't load yet. For some parts, the panel says Commander retries on its own. You do nothing. For the others, the panel says it will not retry, and you contact support.

Explore with sample data ​

You do not have to wait. You can look around a sample store while your own import keeps running.

  1. In the wizard, press Explore the app with sample data instead. On a waiting page, press Explore app with demo data.
  2. Under Choose a sample store, pick a sample store.
  3. Browse the app. A bar at the top says you are exploring sample data.
  4. To return, press the button on that bar. It reads Go back to onboarding while you are mid-setup, or Back to my store after you finish the wizard.

Sample data is not your data. Your own import is not affected. For more, see Demo Mode and sample data.

If a step fails ​

If a phase fails, the strip opens by itself. Its summary line reads, for example, Importing needs a look. The strip then lists the steps under the three phase names.

  1. Read the error text.
  2. Press Retry, or press Restart from here on a phase.
  3. Press See details if you want the full detail.
  4. After repeated retries, Retry becomes Contact support. Press it.

If setup shows no sign of progress for a while, Commander says nothing already imported is lost and offers two choices.

  1. Press Resume setup first. Commander picks the work up from where it stopped and keeps everything already imported. The button reads Resuming… while it runs.
  2. Press Clear and start again only if resuming does not help. This drops the setup and returns you to the first form.

If either one does not work, a message appears in the strip and stays until you try again. After repeated resumes, Resume setup becomes Contact support.

Commander is built by Omniconvert.