Staged records
A staged record is one Shopify-shaped payload, ready to load.
There’s at most one per (migration, resource, source row).
Where to find it
From any run item, click Destination records. Filter by:
- Source ID of the originating row.
- Pending — only records with unpushed changes.
- Loaded — only records that have been pushed to Shopify at least once.
- Resource type.
What’s on a row
| Field | Meaning |
|---|---|
| Payload | The JSON that JSONata produced — the body of the Shopify call. |
| Shopify ID | Shopify’s identifier for this record, set on first successful load. Empty until then. |
| Pending | Marked pending if the payload hasn’t yet landed (or has changed since the last successful load). The next load picks it up. |
| Mapping version | The version that produced this payload. |
| Last loaded at | Wall-clock of the most recent successful push. |
| Last load error | If the last load failed, the Shopify error here. |
How to use it
- Pre-load review — after a transform, scan the payloads of a representative sample to confirm the mapping’s output is sane.
- Post-load audit — for any record, see the exact JSON that landed on Shopify, plus the version that produced it.
- Failure triage — filter by pending + last load error to see exactly what’s stuck and why.
Pending mechanics
A record becomes pending when:
- A transform produced new output for it.
- A previous load failed for it.
A record clears its pending flag when:
- A load successfully pushed it.
You can force a re-push of records that aren’t pending by toggling only-dirty off in the next load. See Only-dirty loads.
Last updated on