Skip to main content

​
Import, Export, And Upgrades

Liquid themes are source packages. Import and export move the editable package, not a compiled app bundle.

​
Export

Export downloads the current theme source package as a ZIP. It includes:
  • layout/
  • sections/
  • snippets/
  • assets/
  • schema.json
  • settings.json
  • theme-package.json
API: 
GET /dev/v1/themes/{id}/export
CLI: 
shoppex theme pull --theme "$THEME_ID" --out ./my-theme

​
Import Or Source Replacement

Import uploads a full source snapshot and validates it. API: 
POST /dev/v1/themes/{id}/source
CLI: 
shoppex theme push --dir ./my-theme
Push is a full source replacement. Deleted local files are deleted remotely.

​
Validation

Validation checks:
  • manifest shape
  • declared files
  • Liquid syntax
  • safe tags and filters
  • static partial references
  • unsafe markup
  • package limits
  • optional typecheck for surrounding generated/config files
If validation fails, the draft source may still be stored so you can inspect and fix the exact failing snapshot. Publish remains blocked.

​
Upgrades

An upgrade compares a merchant-customized Liquid package with a newer upstream package. The safe model is:
  1. export or pull current source
  2. apply upstream changes in a branch or local folder
  3. resolve conflicts intentionally
  4. push as draft
  5. validate
  6. preview
  7. publish
Backups may be available around upgrade and restore flows, but normal small edits should rely on preview before publish.

​
Not Included

Liquid source export is not:
  • a full private backend artifact path
  • a direct storage dump
  • a checkout or payment export

​
Next Steps

Package Format

Required Liquid source package shape.

Build & Publish

How source becomes a live server-Liquid artifact.