

The import screen: a preview, what the pack adds, the requirements, and the two options.
A new store looks empty until it has products. Storefill fills it with the demo content your theme
was designed around, so you can see every section working and then swap the demo products for your
own.
Open Appearance Import demo, check the requirements, and click Import demo content.
For Vitrena, eBasket, Luma, Unishop and Gadgetix, Storefill first installs or updates and activates
WooCommerce when needed. Plugin setup runs on this screen, with activation redirects suppressed,
before any content is imported.
If setup fails, the import stops and offers Try again.
Storefill adds:
Tick This is a public demo site (or use --demo-site on the command line) to also set the site
title and store address, switch store visibility to Live, turn on pretty permalinks, unpublish
WordPress’s sample post and page, and add a demo checkout: a payment method that takes no money and
delivery methods, so visitors can place a test order. Never use this option on a real store.
wp storefill packs
wp storefill import unishop --demo-site
wp storefill status unishop
wp storefill remove unishop --yes
Demo packs are available for Twenty Twenty-Five (the default WordPress theme), Unishop, eBasket,
Luma, Vitrena, Gadgetix and Yantra. Packs for more themes are added to the demo library over time; Storefill
finds them without an update.
A demo pack is a few JSON files (content, dashboard settings, Customizer settings and widgets)
and a folder of photos in the public
demo-pack repository. Its README documents the format.
Nothing in a pack is executed: Storefill only reads data and imports images through the WordPress
media library. Pack text is treated as plain text (any HTML is stripped), and a pack can only change
a fixed list of store and site-identity settings, never accounts, roles, URLs or security settings.
A pack may declare required_plugins, with each entry specifying a WordPress.org slug, display
name, plugin entry file (for example, woocommerce/woocommerce.php) and minimum_version.
The admin importer prepares these plugins before importing content. Plugin downloads come only
from WordPress.org; a pack cannot supply a plugin download URL or executable code.
Storefill downloads demo packs from the public demo-pack repository on GitHub, published with
GitHub Pages at som3669.github.io.
index.json), the pack for your active themepack.json) and that pack’s photos.GitHub is operated by GitHub, Inc.:
Terms of Service,
Privacy Statement.
To use another host, define STOREFILL_SOURCE in wp-config.php with its base URL. To read packs
from a folder on the server without requesting pack files remotely, define STOREFILL_LOCAL_PACKS
with the folder path. Required plugins may still be downloaded from WordPress.org during import.
When you click Import demo content for a pack with required plugins, Storefill uses the
WordPress.org plugin API (api.wordpress.org) to check plugin information and downloads missing
or updated plugins from downloads.wordpress.org. These requests include the plugin slug and
locale, and WordPress’s default user agent includes the WordPress version and site URL. Your
server’s IP address is also visible to the service. Plugins are activated only with the current
administrator’s plugin-management permissions.
If a required plugin needs an update, Storefill requests WordPress’s standard plugin update
check from api.wordpress.org. WordPress sends installed plugin headers and versions, active
plugins, plugin translations and available site languages, plus its version and site URL in the
user agent. Only the selected demo’s required plugin is updated.
WordPress.org Privacy Policy.