> ## Documentation Index
> Fetch the complete documentation index at: https://partner-integrations.voyado.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What's new?

Here you'll find  the changes and updates to the Voyado Engage app for Shopware.

There is an RSS feed for this page allowing you to subscribe to changes as they are published.

<Card title="Show me the RSS feed" icon="https://mintcdn.com/voyado-partners/0IxEIB2Y6a--gNYY/icons/partner-integrations-link.png?fit=max&auto=format&n=0IxEIB2Y6a--gNYY&q=85&s=f3f7d94d9be6a06ca87acc84e4d5c032" horizontal href="/docs/ecom/shopware/whats-new/rss.xml" width="128" height="128" data-path="icons/partner-integrations-link.png" />

<Update label="2026-07-08">
  ## Bug fixes

  * Fixed an issue where certain product data returned by Shopware in an unexpected format could cause sync errors. Product events now handle this format correctly.
  * Reduced additional cases where webhook events could fail with a "store configuration not found" error, by extending the fallback lookup introduced on 2026-07-02 to more integration endpoints.
</Update>

<Update label="2026-07-02">
  ## Bug fixes

  * Fixed a case where store configuration could intermittently fail to be found, causing sync errors even for correctly configured stores. The integration now falls back to an alternate lookup when the primary one returns no result.
</Update>

<Update label="2026-07-01">
  ## Bug fixes

  * Fixed cart tracking not firing for products added to the cart via the off-canvas modal. Tracking events are now sent correctly regardless of which add-to-cart flow the customer uses.

  <Info>
    Available in app-version **2.3.4 and higher**
  </Info>

  ## Improvements

  * Cart tracking now correctly fires when a customer empties their cart. Removing the last item from the cart now sends a tracking event to Voyado Engage, so abandoned-cart and re-engagement flows handle the cart-cleared state correctly.

  <Info>
    Available in app-version **2.3.4 and higher**
  </Info>

  * Requests to Voyado Engage that receive a temporary service-unavailable response are now automatically retried with a backoff, reducing the risk of data loss during brief outages.
  * Outbound API calls now enforce a 10-second timeout, preventing slow responses from blocking order and event processing.
</Update>

<Update label="2026-06-24">
  ## Bug fixes

  * Fixed an issue where saving a contact's consent and privacy policy settings could fail with a 422 error. Privacy policy acceptance is now persisted reliably when a contact is created or updated.
</Update>

<Update label="2026-06-22">
  ## Bug fixes

  * Fixed cart tracking events being rejected when no cart ID was available. This affected customers who reached checkout via custom themes or without going through the standard add-to-cart flow. Cart IDs are now sourced from Shopware's native session context token instead of being generated client-side, ensuring cart tracking works reliably for all customers.

  <Info>
    Available in app-version **2.3.3 and higher**
  </Info>

  ## Improvements

  * Orders with large numbers of line items are now processed more reliably. Order event payloads that exceed SQS message size limits are automatically offloaded to S3, preventing processing failures for complex orders.
</Update>

<Update label="2026-06-12">
  ## Bug fixes

  * Order line items that are not part of a bundle are no longer grouped together incorrectly. Standalone items previously shared a blank grouping value that Engage displayed as "\*", lumping unrelated items into one group. They now appear individually as expected.
  * Sales tax amounts on orders, receipts and returns are now always reported as positive values.
  * Orders containing discounted bundle/composition items now calculate tax using each item's own tax rate instead of the order's overall rate. Orders with mixed tax rates that were previously rejected by Engage now sync correctly.

  ## Improvements

  * More reliable retrieval of order data from Shopware, reducing transient failures when fetching order details.
  * Events are now processed more reliably in batches. If one event fails, the remaining events in the same batch continue to process independently rather than failing together.
</Update>