Bulk order import

Use Order settings → Bulk import to sync historical Shopify orders into e-conomic. The app reuses the same order sync rules as ongoing order sync.

When to use it

  • You connected e-conomic after orders already existed in Shopify.
  • You need a one-time catch-up for a date range.
  • Ongoing sync only covers new events going forward.

What it does

  1. Finds Shopify orders in your selected date range and filters.
  2. Creates e-conomic sales orders or invoices according to your import options.
  3. Skips orders that were already synced when Skip if already synced is active (default).

What it does not do

  • Refunds, voids after sync, or order edits on Shopify are not pushed to e-conomic.
  • Cancelled/refunded/voided orders can be excluded with the default safety checkboxes.
  • Very large orders may need support review if not all lines are available from Shopify.

Why fewer orders may appear than expected

If you don't see all expected orders, check the following:

Cause What happens Fix
Default status filter Cancelled orders are excluded unless you uncheck "Exclude refunded, voided, and cancelled". Uncheck the safety filter, or explicitly pick Cancelled in Shopify order status.
Max orders The form caps each run (default 250, max 5000). If you set a low number, the import stops at that count. Raise Max orders in the form.
Older orders permission Shopify may limit access to older orders unless the app has permission for older order history. Ask the app/admin team to enable older order access and reinstall if needed.
Date range Store timezone differences can make edge-of-day orders appear outside the selected range. Extend the date range by one day on each side.
Background processing If background processing is not running, the run stays pending and no orders are scanned. Ask your app/admin team to restart background processing.

You can always open Bulk import logs to see the saved import choices and per-order skip reasons.

Recommended workflow

  1. Set Order → Rule sync (document type, VAT, shipping) the way you want ongoing sync.
  2. Open Bulk import, choose a date range, and click Preview.
  3. Review eligible vs skipped sample rows.
  4. Run a Dry run first if you want a full test run with logs, without creating e-conomic documents.
  5. Click Start import and wait for the run to complete. The status panel polls automatically and shows a loading indicator while the run is pending or running.

Document type for import

Bulk import has its own document choice (sales order, invoice draft, or booked invoice). It does not change your ongoing order sync settings. Booked invoices are created in the required e-conomic sequence automatically.

Import history (logs)

Every import run is saved with:

  • Saved choices for the run (date range, statuses, document type, enabled flags)
  • Per-order rows: order name, Shopify ID, financial/fulfillment status, result, skip reason or error message, and e-conomic ID when created

Open Order settings → Bulk import → Import history, or Bulk import logs in the header. Click a run for the full detail table. Dry runs are logged too.

Older order access

For orders older than Shopify's standard recent history window, the app may need extra permission for older order access. Ask your app/admin team to confirm this before large historical imports.

Large imports run in the background. If a run remains pending, contact your app/admin team.

Troubleshooting checklist

  1. Open Order settings → Bulk import → Import history and pick the latest run.
  2. Look at per-order rows filtered by Skipped / Failed to see reasons:
    • Test order — exclude test orders is on and the order is flagged as test.
    • Cancelled/refunded/voided — caught by the safety filter.
    • Shopify order status mismatch — your status filter excludes this order.
    • Financial/fulfillment mismatch — your optional filter does not match.
    • Already synced — the order was synced in a previous run or by ongoing sync.
    • Order status rules mismatch — "Apply order status rules from settings" excluded the order.
    • Dry run would sync — eligible, but you used Dry run.
  3. If the reason is unclear, send the latest run ID and a screenshot to support.