App Store August Update: Segment App and PayloadCMS
August brings a brand new Segment App, a new provider to the CMS App, and new features across the board.
Segment
The newly introduced Segment App sends Saleor-specific events to Segment - a data platform designed to supercharge your analytics and enhance customer experience.
Currently, the Segment App is configured to track the following events: ORDER_CANCELLED, ORDER_CREATED, ORDER_FULLY_PAID, ORDER_REFUNDED and ORDER_UPDATED.
CMS
In August, the list of available providers grew with another addition. We added support for PayloadCMS - an open-source CMS developers love.
To begin using Payload CMS, head to the integration documentation.
As a reminder, Saleor’s current line-up of supported CMS providers consists of PayloadCMS, Builder.io, DatoCMS, Contentful, Strapi.
Is your favorite CMS missing from the list? Feel free to propose it on GitHub!
Taxes
Transaction flow
We changed the provider transaction flow to rely on different events. Previously, we operated on ORDER_CREATED and ORDER_FULFILLED. On the first one, we would create a transaction on the provider’s side. On the latter, we would commit the created transaction.
The new flow unifies the process under one ORDER_CONFIRMED webhook event. The user can decide whether to commit the transaction in the provider configuration in the app.
Let’s break it down in the case of AvaTax. If you enable the "Autocommit" option in the AvaTax configuration form, the transaction created on the ORDER_CONFIRMED event will be committed. If disabled, the transaction will be created uncommitted.
OrderCancelled
The transaction flow has been enhanced to support a new webhook event: ORDER_CANCELLED. This event is currently supported in Saleor’s AvaTax app implementation.
New AvaTax field mappings
Taxes App allows you to associate custom values with transaction fields using privateMetadata. If a matching metadata key is located, that value will be incorporated when creating a new transaction.
For a comprehensive list of mappable fields, visit our documentation. This month, we've introduced the following fields:
avataxDocumentCode- maps to AvaTax’s document code.avataxTaxCalculationDate- maps to AvaTax’s date.
UI
We did a slight rearrangement in the AvaTax configuration form. It now consists of three sections:
- Credentials - fields related to authenticating the user.
- Settings - fields related to the user preferences.
- Address - address used for tax calculation.
The full changelog can be found here.
Product Feed
In version 1.11 of the app, we’ve integrated Handlebars into Product Feed to enhance your customization options. As a result, you can now design the title template like so:
The fields in the {{ }} brackets will be dynamically populated during feed generation.
The URL structure for products has also transitioned to the Handlebars format. While the application continues to support the older URL format, the recommended syntax is now:
Additionally, the Product Feed App now lets you select which product attributes (such as "brand," "color," or "size") are used in generating the feed. We've also aligned pricing attributes with Google's guidelines and introduced the use of the Product Group ID field.
Search
Improved attributes mapping
Integration with Algolia now sports improved attribute mapping. The new orderVariants field can be used to find alternatives to the selected product variant.
In the latest update, we've differentiated between metadata for parent products and individual variants. The metadata field now pertains to the parent product data, while the new variantMetadata field is designated for each variant.
Additionally, we've enhanced the data types for JSON-like fields. The fields: description, metadata, variantMetadata, and otherVariants, are now structured as actual JSON objects rather than stringified JSON. This improves both data integrity and ease of use.
Miscellaneous
The additional improvements include:
• A single-button click now allows you to update your Algolia index with a preset configuration optimized for seamless integration with Saleor.
• The full-text search has been refined for better results, courtesy of a new descriptionPlaintext field that incorporates unformatted product descriptions.
• We've addressed the issue of stale product variants lingering in Algolia after a product is deleted or its channel visibility is modified. This ensures data consistency across all platforms.