Upgrading From 3.21 To 3.22

Deprecation of Saleor plugins

Following plugins are now marked as deprecated:

Plugin Name	Plugin ID	Possible replacements
Braintree	`mirumee.payments.braintree`	Juspay Hyperswitch App or Custom App
Razorpay	`mirumee.payments.razorpay`	Juspay Hyperswitch App or Custom App
Sendgrid	`mirumee.notifications.sendgrid_email`	Saleor SMTP App. On Saleor Cloud 3.23+, Customer Emails replaces it for new stores.
Dummy	`mirumee.payments.dummy`	Saleor Dummy Payment App
DummyCreditCard	`mirumee.payments.dummy_credit_card`	Saleor Dummy Payment App
Avalara	`mirumee.taxes.avalara`	Saleor Avalara AvaTax App

We plan to remove deprecated plugins in the future versions of Saleor.

Changes to orders with a zero total amount

The following changes were implemented to orders with a zero total amount:

No manual charge (Transaction or Payment) object will be created.
The OrderEvents.ORDER_MARKED_AS_PAID event will no longer be emitted.

Automatic checkout completion behavior change for checkouts with total being 0

Before version 3.22, the following scenario would result in automatic checkout completion. In version 3.22 and onwards, this behavior has changed.

Preconditions:

Channel has an automatic checkout completion feature enabled
Checkout has a total amount equal to zero
Checkout has lines

Upon processing a transaction, the checkout would have been completed because then, it was not considered fully paid. Transaction logic recognized the authorization status change, which triggered automatic checkout completion.

Now, upon processing a transaction, the checkout will not get completed because checkout is already considered fully paid; therefore, transaction logic does not recognize any authorization status change thus automatic checkout completion is not triggered.

Behavior change for creating a Payment (old API) for a Checkout object with an existing Transaction (new API)

Creating a Payment (old API) for a Checkout object with an existing Transaction (new API) is no longer permitted as it leads to inconsistent behavior.

Deprecation of the `attribute` and `attributes` fields in the `Page`, `Product`, and `ProductVariant` types

The attribute and attributes fields are deprecated, along with the SelectedAttribute type. They are replaced by the assignedAttribute and assignedAttributes fields on Page, Product, and ProductVariant, which use the AssignedAttribute interface. Each attribute type now has its own dedicated shape built on top of AttributeInterface, instead of the previous generic AttributeValue with unrelated fields.

The SelectedAttribute returns multiple optional and unrelated fields:

{
  product(slug: "apple-juice", channel: "default-channel") {
    attribute(slug: "multi-select") {
      attribute {
        id
      }
      values {
        id
        name
        slug
        value
        reference
        file {
          url
        }
        date
        dateTime
        boolean
        richText
        plainText
        translation(languageCode: FR) {
          name
          richText
          plainText
        }
      }
    }
  }
}

The newly introduced AssignedAttribute provides a strictly typed structure that only returns fields relevant to the specific attribute type.

{
  product(slug: "apple-juice", channel: "default-channel") {
    assignedAttribute(slug: "multi-select") {
      attribute {
        id
      }
      ... on AssignedMultiChoiceAttribute {
        value {
          name
          slug
          translation(languageCode: FR)
        }
      }
    }
  }
}

Previously, fetching a reference attribute required two steps: first retrieving the reference id, and then fetching the page using that ID.

{
  product(slug: "apple-juice", channel: "default-channel") {
    attribute(slug: "reference-to-page") {
      attribute {
        id
      }
      values {
        pageIdReference: reference
      }
    }
  }
}

{
  page(id: "<pageIdReference>") {
    title
  }
}

assignedAttribute(s) provides a specific type for each kind of reference, allowing the reference object to be fetched in a single query.

{
  product(slug: "apple-juice", channel: "default-channel") {
    assignedAttribute(slug: "reference-to-page") {
      attribute {
        id
      }
      ... on AssignedMultiPageReferenceAttribute {
        value {
          title
        }
      }
    }
  }
}

Changes to deactivated apps

Starting with version 3.22, webhooks are no longer triggered for deactivated apps. In earlier versions, events continued to be sent through active webhooks even when the app itself was deactivated.

Saleor Dashboard - Removed feature flags

The following feature flags have been permanently removed from Saleor Dashboard in the 3.22 release. These flags were enabled by default in previous releases and had to be manually disabled to revert to legacy behavior.

Version history

Version	Release Date	Key Changes
3.15.0	Aug 2023	Product filters added (disabled)
3.17.0	Oct 2023	Product filters enabled by default
3.19.0	Feb 2024	Discount rules added (disabled)
3.20.0	Jul 2024	Order filters added & enabled, Improved refunds added (disabled)
3.20.29	Mar 2025	App alerts added & enabled
3.21.0	May 2025	Extensions added & enabled, Discount rules enabled by default
3.22.2	Oct 2025	Feature flags removed (see below)

Here are full details about removed feature flags and what they changed:

Product Filters:

Added: v3.15.0
Enabled by default: v3.17.0

Order Filters:

Added & Enabled by default: v3.20.0