2 min read

Shirely Changelog: What’s New

This changelog summarizes public-facing changes in Shirely 1.3.0 and earlier releases. It is not a substitute for the release source.

1.3.0 — current release

  • Automation adds saved import and export slots, Run now, hourly, twice-daily and daily WP-Cron schedules, Run History, and WP-CLI commands.
  • Scheduled imports can read Google Sheets, a public remote CSV or a CSV in Shirely’s protected inbox directory.
  • Scheduled exports publish supported catalog data to Google Sheets.
  • WooCommerce coupons now use native import and export workflows.
  • Catalog provenance helps prevent a source store’s product ID from being treated as a local ID during transfers.
  • A manual customer import can optionally send an invite email to newly created customers; unattended Automation and WP-CLI runs do not send it.

WP-Cron depends on site activity and can start a due job later on a quiet site. For large imports or precise timing, use system cron with WP-CLI and verify completion in Run History.

1.2.1 — historical release

  • WooCommerce compatibility: requires WooCommerce 8.0+ and is tested through WooCommerce 10.7.
  • Store Data workflows cover dedicated CSV import/export surfaces for orders and customers, with additional store data surfaces handled separately from product import/export.
  • Order export/import uses WooCommerce order APIs and is HPOS-safe.
  • Customer import/export treats customers as WordPress users with the customer role.
  • At that release point, Google Sheets workflows were on demand. Scheduled Automation was added later in 1.3.0.
  • Smart Sync skip behavior applies only to posts, pages, and custom post types with a mapped Record ID; products, categories, and Matrix Mode rows are always processed.

Recent 1.1.x highlights

  • Google Sheets import/export using the customer’s own Service Account for private Sheets and exports.
  • Matrix Mode for WPML product, category, post, page, and custom post type workflows.
  • Improved category hierarchy handling across languages.
  • More reliable partial updates and product matching behavior.

For the current public feature set, use features and documentation.