Shopify Historical Backfill
Choose, launch, and verify the historical Shopify data window exported to a destination.
Last reviewed July 13, 2026
Historical backfill exports supported Shopify server-side records from a selected past window. Client-side browsing events cannot be recreated from Shopify’s backend data.
Available Windows
The current setup offers no historical sync or a bounded range up to the maximum shown in the app. Vendo converts the selected preference into the pipeline’s initial export window.
Choose the smallest range that meets the analysis or migration requirement. A larger window increases volume, destination usage, processing time, and reconciliation work.
Included Data
Depending on enabled server events and source availability, a backfill can include:
- orders and eligible lifecycle events;
- refunds and fulfillments;
- per-product purchase events when enabled;
- customer profile updates;
- supported abandoned-checkout records.
It does not recreate historical page views, product views, searches, cart clicks, or browser-only checkout events.
Start a Backfill
- During destination setup, enable the required server-side events.
- Choose the historical range.
- Review the destination’s event volume, retention, and cost implications.
- Complete setup and monitor the destination status.
- Wait for the initial import to complete before assessing normal incremental freshness.
If no server-side event is enabled, the setup can force the historical preference to none because there is nothing eligible to export.
Verify
Reconcile by source date and event type:
- compare Shopify order counts with exported order events;
- separate orders, line items, refunds, and profiles rather than comparing one total;
- check earliest and latest timestamps;
- sample stable order and customer identifiers;
- inspect skipped and failed records;
- confirm normal incremental jobs begin after the initial window.
Re-running History
Requesting an additional historical range can resend records. Confirm the destination’s deduplication key and retention behavior before rerunning it. Contact support when cleanup or an exact replay boundary is required.
Troubleshooting
| Symptom | Check |
|---|---|
| Status remains pending | Server events, source readiness, destination credentials, and job history |
| Oldest date is later than expected | Selected window and what Shopify still exposes |
| Counts differ | Event definition, refunds, cancellations, timezone, line-item events, and destination rejection |
| Duplicates appear | Stable event ID, destination deduplication, and whether history was replayed |