PluginDistrict

<p><strong>SnapSettings for WooCommerce</strong> by Plugin District lets you back up your entire WooCommerce configuration and restore it on any other WooCommerce installation in seconds.</p>
<p>Whether you are migrating from staging to production, setting up a new store with identical settings, or just want a dated snapshot before making big changes — this plugin handles it with one export and one import.</p>
<h4>What gets exported</h4>
<ul>
<li>All WooCommerce options (currency, store address, payment gateways, email settings, inventory, and more) — any row in <code>wp_options</code> whose name begins with <code>woocommerce_</code>, excluding runtime/version-specific entries that should not be transferred between sites.</li>
</ul>
<h4>What does NOT get exported</h4>
<p>Products, orders, customers, coupons, media, or any other transactional data. This is a <em>settings</em> backup tool.</p>
<h4>Key features</h4>
<ul>
<li><strong>Drag-and-drop import</strong> — drop a CSV onto the upload zone or browse for the file.</li>
<li><strong>Dated export filename</strong> — files are named <code>woocommerce-settings-YYYY-MM-DD.csv</code> so backups are easy to identify.</li>
<li><strong>Atomic import</strong> — every import runs inside a database transaction. If anything fails the database is automatically rolled back; nothing is left partially imported.</li>
<li><strong>Import summary</strong> — stat pills, a per-table breakdown, and a collapsible full log so you can see exactly what changed.</li>
<li><strong>Safe option exclusions</strong> — runtime and version-specific options (<code>woocommerce_db_version</code>, <code>woocommerce_version</code>, etc.) are intentionally excluded from exports to avoid breaking the target site.</li>
<li><strong>Confirmation dialog</strong> — prevents accidental overwrites on import.</li>
<li><strong>Capability-gated</strong> — only users with the <code>manage_woocommerce</code> capability (Shop Manager / Administrator) can export or import.</li>
</ul>
<h4>Also available</h4>
<p>A separately-distributed Pro add-on extends SnapSettings with shipping zone and tax rate export/import. See <a href="https://plugindistrict.com/plugin/settings-backup-and-migration-wizard-for-woocommerce/" rel="nofollow ugc">plugindistrict.com</a> for details.</p>


SnapSettings for WooCommerce

Export, transfer, and restore your WooCommerce settings across different installations with a single CSV file.

Jon Christopher

<p>Build any number of options screens based on <a href="https://wordpress.org/plugins/custom-field-suite/" rel="ugc">Custom Field Suite</a>.</p>
<h4>For Example</h4>
<p>Begin by creating Field Group(s) you want to include on your options screen. <strong>Be sure to set NO Placement Rules.</strong> Once it’s created, note the post ID it uses. You can then register any number of options screens like so:</p>
<pre><code>function my_cfs_options_screens( $screens ) {
    $screens[] = array(
        'name'            => 'options',
        'menu_title'      => __( 'Site Options' ),
        'page_title'      => __( 'Customize Site Options' ),
        'menu_position'   => 100,
        'icon'            => 'dashicons-admin-generic', // optional, dashicons-admin-generic is the default
        'field_groups'    => array( 'My Field Group' ), // Field Group name(s) of CFS Field Group to use on this page (can also be post IDs)
    );

    return $screens;
}

add_filter( 'cfs_options_screens', 'my_cfs_options_screens' );
</code></pre>
<h4>Retrieve your options like so:</h4>
<pre><code>$value = cfs_get_option( 'options_screen_name', 'cfs_field_name_from_field_group' );
</code></pre>
<p>You can set up multiple top level and/or children options pages by adding a <code>parent</code> argument when registering your screen:</p>
<pre><code>function my_cfs_options_screens( $screens ) {

    // Parent
    $screens[] = array(
        'name'         => 'options',
        'field_groups' => array( 'My Parent Field Group Name' ),
    );

    // Child
    $screens[] = array(
        'name'         => 'options-nav',
        'parent'       => 'options', // name of the parent
        'field_groups' => array( 'My Child Field Group Name' ),
    );

    return $screens;
 }

 add_filter( 'cfs_options_screens', 'my_cfs_options_screens' );
</code></pre>
<p>You can also use CFS Options Screens to set up Field Group ‘defaults’, allowing a Field Group to appear both on a CFS Options Screen and a post edit screen. The CFS Options Screen will act as the default/fallback and the post edit screen will override those defaults.</p>
<pre><code>function my_cfs_options_screens( $screens ) {
    $screens[] = array(
        'name'            => 'options',
        'menu_title'      => __( 'Site Options' ),
        'page_title'      => __( 'Customize Site Options' ),
        'menu_position'   => 100,
        'icon'            => 'dashicons-admin-generic', // optional, dashicons-admin-generic is the default
        'field_groups'    => array(
            array(
                'title'         => 'My CFS Field Group Name',
                'has_overrides' => true,
            ),
        ),
    );

    return $screens;
}

add_filter( 'cfs_options_screens', 'my_cfs_options_screens' );
</code></pre>
<p>Check out the <code>cfs_options_screens_override_note_default</code> and <code>cfs_options_screens_override_note_override</code> filters to customize the messaging for CFS Options Screens overrides.</p>


CFS Options Screens

Create options screens that utilize Custom Field Suite

SnapSettings for WooCommerce vs CFS Options Screens