Store export and restore

List the parts of the store a bundle can carry (settings, customers, catalog, pictures, digital files, promotions, reviews, orders, store credit, and each add-on's own), grouped as the Export screen shows them, with how many rows each holds, the sets each depends on, the permission each needs, and whether this caller holds it. Also says whether this server can write a zip and seal secrets with a passphrase.

Queue an export of the store into one bundle (a zip) on the server. It runs in the background job queue a step at a time; read its progress with get_store_export. Give everything: true for every set the caller may export, or sets to name them. Hashed customer passwords go only with passwords: true. Credentials, tokens, webhook secrets and saved payment methods go only with secrets: true and a passphrase of at least eight characters, sealed in one encrypted file; without them the bundle holds none and the restore report lists what to enter again.

Read one export's progress, and once it has finished, its size, its sets with their row and file counts, whether secrets were sealed in it, what was not included, and when the bundle will be deleted from the server.

Delete an export's bundle from the server. The export's line in the history stays, saying who exported what and when.

List the bundles in user/data/kahunacart/exports, newest first: this store's exports, uploaded bundles, and bundles copied into the folder by hand. Any of them can be inspected and restored by name.

Read what a bundle on the server holds before restoring it: where it came from, the KahunaCart and add-on versions that wrote it, each set with its counts and whether it can be restored here (and which add-on to install when not), whether it carries sealed secrets, and whether a full restore is allowed into this store and why not.

Delete a bundle from user/data/kahunacart/exports by its file name.

Queue a rehearsal of restoring a bundle: the whole restore inside a transaction that is always rolled back, so it writes nothing. Read the report with get_store_restore. mode is merge (add to this store, never deleting anything) or full (only into a store with no orders and no customers). Give the passphrase to rehearse the secrets too.

Queue the restore of a bundle into this store. It runs in the background job queue a set at a time and sends nothing: no email, notification, webhook or payment provider call. Read its progress and report with get_store_restore. Run dry_run_store_restore first.

Read one restore or dry run: its progress, and once finished its report. The report has created, updated, skipped and failed per set, the sets that could not run and why, what to enter again, and when the store moved to a new address, a checklist for the old site with a redirects block for its site.yaml and each payment provider's new webhook address.

The history of store exports and restores, newest first: who ran each, when, which sets, the mode, the bundle's size and how it went.

Store an uploaded bundle (multipart, field file) on the server and answer with what it holds, the same summary inspect_store_bundle gives. No tool, because it takes multipart.

The bundle itself, streamed. This is the only way a bundle leaves the server. No tool, because it serves a file.

The catalog file, the same one bin/plugin kahunacart export writes. This is Export… → Catalog file on Products. No tool, because it serves a file.

Every product with its default variant, in the CSV importer's own column names, so it imports back with nothing to map. No tool, because it serves a file.