Shopify Historical Backfill
Choose, launch, and verify the historical Shopify data window exported to a destination.
Last reviewed September 15, 2026
Historical backfill exports supported Shopify server-side records from a past window that you select. Vendo cannot recreate client-side browsing events from the Shopify 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 initial export window of the pipeline.
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
A backfill can include these records. The result depends on the enabled server events and on what the source makes available.
- 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
- In destination setup, enable the required server-side events.
- Choose the historical range.
- Review the event volume, retention, and cost implications for the destination.
- Click Complete Setup.
- Monitor the destination status.
- Before you assess normal incremental freshness, wait for the initial import to complete.
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.
- Compare orders, line items, refunds, and profiles separately, not as one total.
- Check the earliest and latest timestamps.
- Sample stable order and customer identifiers.
- Inspect skipped and failed records.
- Confirm that normal incremental jobs start after the initial window.
Re-running History
A request for an additional historical range can send records again. Before you run history again, confirm the deduplication key and retention behavior of the destination. If you need cleanup or an exact replay boundary, contact support.
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 |