Shopify backup vs PIM and ERP resync: what each one puts back
Updated on
Short answer
A PIM or an ERP is not a backup of your Shopify store. A resync sends back the product fields it holds, in their current version, and nothing else.
A backup keeps a dated copy of the whole store, theme, pages and menus included, and puts back the item you choose as it was before the incident. Restore first, then let the sync resume.
What does a PIM or ERP resync put back?
A PIM is where product information is written: titles, descriptions, attributes, media. An ERP holds prices, stock and what accounting needs. Each one pushes its fields to Shopify through a connector.
When one of those fields is wrong in Shopify, the next sync overwrites it with the value the PIM or ERP holds. Some connectors also create again a product that was deleted in Shopify. For those fields, a resync does the job.
What does a resync leave out?
- The store at a given date. A connector sends the current value. None documents a dated copy of the Shopify store you could go back to.
- The theme, the pages, the blog and the menus. Neither a PIM nor an ERP holds them, so no sync can send them back.
- What was only ever entered in Shopify. A connector sends back what it holds. A field your team or an app filled in the Shopify admin is not in the PIM.
- A check before writing. No connector documents a comparison with the live store before it overwrites.
- A warning. No connector documents an alert when items disappear from Shopify.
PIM or ERP resync and Starship, side by side
| Comparison | PIM or ERP resync | Starship |
|---|---|---|
| Product fields held by the PIM or ERP | ||
| Automatic, dated copy of the Shopify store | ||
| Theme, pages, blog and menus | ||
| Comparison with the live store before anything is written | ||
| Alert when items disappear from Shopify | ||
| Ask Sidekick what was deleted |
According to the public documentation of the Shopify connectors of the market's PIMs and ERPs, November 2026.
When is the PIM's version the wrong one?
A resync writes what the PIM holds today. If the mistake was made in the PIM, or in a file imported into it, the sync carries it to Shopify again. Going back then means finding the earlier value somewhere else.
A backup covers that case, because each version is dated. You pick the product as it was on Monday, not as the PIM describes it now.
How do the two work together?
Back up before the change.
Run “Back up now” before an import, a connector update or a theme change.
Compare after the incident.
Starship shows the backup next to the live store, and what would change, before anything is written.
Restore what was hit.
One item, a category or the whole store. One item comes back in seconds, and Starship shows the estimated time for the rest.
Let the sync resume.
Starship writes to Shopify only. The PIM and the ERP are not modified, and the next sync runs as usual.
Starship does not replace the PIM or the ERP. It puts Shopify back in its state from before the incident, item by item, then the sync resumes. See also Shopify backup vs CSV export.
Sources
The statements about Shopify on this page come from Shopify's own documentation.
