Skip to main content
Import and export are Pro features. On the free build the routes are not registered at all — a request 404s like any unknown route.
Presets export as JSON and import somewhere else. The obvious use is carrying a staging store’s work to production without rebuilding it by hand.

​
Exporting

One preset — Export as JSON in the row menu. Several — tick the rows you want and use the bulk export. The file contains the presets, their items, and every setting on both. It does not contain your store settings, your wording overrides, or any order data.
The export is plain JSON, so it diffs readably. Committing it to a repository gives you a version history of your presets, which the plugin itself does not keep.

​
Importing

Upload the file on the destination store.

​
How products are matched

By SKU first, falling back to product ID. SKU first is the important half. Product IDs almost never line up between two stores — the same hoodie is #412 on staging and #1908 on production. A SKU is a name you chose, and it usually survives the move.
An ID-only match is a guess. If your two stores have unrelated product IDs, an import can silently attach the wrong product. Check imported presets before activating them — which is what the next section makes easy.

​
Every import arrives inactive

Whatever the status was on export, imported presets land inactive. No link goes live unasked. You get to open each one, check the items matched the products you expected, look at the health panel, and activate deliberately.

​
Slugs

An imported slug already taken on the destination store gets a numbered suffix, the same way a manually created one does. The import never overwrites an existing preset.
That means importing the same file twice gives you two copies rather than an update. Import is a copy operation, not a sync.

​
What does not travel

Import presets containing custom items after linking a carrier product on the destination store. Without one, those items cannot be added and the health panel will flag every affected preset.

​
For developers

The routes are cartpresets/v1/presets/export and cartpresets/v1/presets/import, registered by Pro on the shared cartpresets_register_rest_routes action. On free nothing listens, so neither route exists. See the REST API.