CSM for WooCommerce Release Notes - 3.5.2026090228.310091

Released: September 3, 2026

Overview

Added

• WooCommerce Order Management and Listing Management now run on Suite Engine's metadata driven API Engine framework instead of the original legacy engine. The order and listing sync functionality customers already rely on is unchanged. This is a foundational change to how API calls, pagination, and data mapping are handled behind the scenes, and it sets up WooCommerce to receive new capabilities faster in future releases. Furthermore, this new API Engine framework is more supported than the predecessor, so stability is improved by migrating.
• A new required component, the Suite Engine API Engine Library, is installed alongside this app to support the change (see Updated below for version details).

• The WooCommerce Setup Wizard has been redesigned around two paths so that both new and existing customers get a setup experience suited to their situation.
  • The wizard opens with a Path Selection step offering Quick Setup (Recommended) or Custom Setup. First time users with no existing WooCommerce Sales Channel or API connection see Quick Setup selected by default. Returning users default to Custom Setup, and Quick Setup is automatically blocked with an inline warning if existing WooCommerce configuration is detected.
    • Quick Setup uses a single screen for WooCommerce Store URL, Consumer Key, Consumer Secret, and WordPress credentials, with a Test Connection action that shows live, inline connection status. The store URL accepts the address with or without the https:// prefix. All other choices, including the Sales Channel, API connection, and API Operations, use sensible defaults automatically.
    • Custom Setup walks through the same configuration step by step: creating the Sales Channel (with inline duplicate code checking that blocks the Next button until resolved), setting up the API connection (with the same duplicate checking, plus the option to reuse an existing WooCommerce API connection instead of creating a new one), entering store credentials, and choosing whether to load API Operation Executions, with a confirmation prompt before any existing operation records are overwritten.
  • Both paths end with a Review step summarizing what will be configured (Sales Channel, API connection, API Operations, and Automations), followed by a completion screen listing what was configured and recommended next steps.

Updated

• Requires CSM Core version 4.10 or later.
• Adds a new required dependency, the API Engine Library (version 1.22 or later), which powers the modernized WooCommerce integration described above.

• The "Load Shipping Carriers" and "Load Shipping Methods" actions on the WooCommerce Sales Channel page have been retired and are no longer visible. Use the Retrieve Shipping Methods action instead.

Fixed

• Stores with more than 100 product attribute options (terms) for an attribute were only getting the first page of results because the underlying API call was missing paging support.
  • A page size parameter and a follow up retrieval step have been added so all attribute options are now retrieved regardless of how many exist.

• Loading the WooCommerce API Operation Automations previously wrote a fixed, hardcoded Sales Channel value into the automation configuration instead of the Sales Channel actually being set up.
  • Automation properties now use the correct Sales Channel Code, fixing automation behavior for Sales Channels that do not use the default code.

• When a Sales Return Order linked to a WooCommerce order included lines manually added by a user (items not on the original order, which WooCommerce allows as long as the refund total does not exceed the order total), the validation that checks whether a return line's quantity exceeds the original order quantity could incorrectly include unrelated posted invoice and credit memo lines that had no connection to the order.
  • The check now only considers lines that are actually linked to the order, correcting the maximum allowed refund quantity calculation.

• API Operations loaded by this app previously defaulted their last execution timestamp to a fixed date in 2021.
  • This hardcoded default has been removed so newly loaded API Operations no longer inherit an outdated fixed timestamp.