Businesses need to exchange data using the scalable, high-volume technologies already in their ecosystem. With 2024.2, the first iteration of a new streaming component is introduced to onboard more data faster. This Kafka-based solution differs from the existing asynchronous architecture of background processes and file-based integration by using true data streaming, consuming individual messages in real time. The delivery follows a proof of concept that achieved significant performance and volume handling improvements over background process-based imports, and general availability is expected with 2024.4.
Overall update summary
2024.2 focuses on getting data in faster and handling it more automatically. A new Kafka-based inbound message streaming component consumes individual messages in real time, moving beyond background, file-based integration, and the asset importer can now manage assets that live in external DAM systems end to end. Administrators can analyse the impact of a configuration change package before installing it. Matching advances on two fronts — a new Person Name matcher version and more robust machine learning match recommendations — and the Loqate address verification connector moves to Loqate's latest cloud API. The Instrument UI improves reference and link handling, adds translation status monitoring across products, extends data containers and introduces a product packaging experience. In PDX, the platform migrates to MongoDB, user journeys are refined, and Enhanced Content gains review flags, filters and dynamic record top-off.
Applicable links
- Update notes: Read
Inbound message streaming
Applicable to all domains | Included in Base | Admin | 24.2 highlight
What changed
- Consumes more data faster than background process-based imports.
- Real-time, message-level ingestion rather than batch file handling.
- Uses Kafka, a technology already common in customer ecosystems.
Configuration management — impact analysis improvements
Applicable to all domains | Included in Base | Admin | 24.2 highlight
What changed
Managing continuous development and configuration across multiple environments is complicated and error prone. The first phase of this work was delivered in 2023.3, and 2023.4 added integration with an external version control system in Git. With 2024.2, before installing a change package, administrators get an overview of all changes in the package, an anticipated installation outcome for each item, and identification of which items will require manual installation.
- Administrators can predict the impact of a configuration update before applying it.
- Reduces the risk of a change package causing problems.
- Manual installation work is identified up front.
Automated digital asset handling
Applicable to all domains | Included in Base | Admin, Business User | 24.2 highlight
What changed
PIM customers whose digital assets are managed in external DAM systems need flexible integration to handle product-to-asset references. With 2024.2, import configurations in the asset importer are optimized to handle assets stored in external DAM systems automatically: assets are created and updated, linked to products through naming conventions or metadata, and kept current with updates from the DAM via REST APIs. A pre-processor is also introduced for data adaptability.
- Reduces manual effort in managing externally held assets.
- Near real-time updates from the DAM speed up the business process.
- The pre-processor adds flexibility for adapting incoming data.
Instrument UI — general updates
Applicable to PMDM | Please refer to your Account Manager | Admin, Business User | 24.2 highlight | deck slide 1 of 3 in the Instrument UI series
What changed
Customers need a modern, intuitive interface that guides users efficiently through their tasks. With 2024.2, two features improve the Instrument UI: the single product details view handles references and links better, and a new view lets users monitor the translation status of multiple products at a glance.
- Clearer handling of references and links in the product details view.
- A comprehensive overview of translation status across products.
- Streamlines day-to-day product management.
Instrument UI — product data containers
Applicable to PMDM | Please refer to your Account Manager | Business User | 24.2 highlight | deck slide 2 of 3 in the Instrument UI series
What changed
Product data containers matter in complex data landscapes where composite and complex structures must stay trustworthy and accurate, so the focus is on extending what can be maintained within them. With 2024.2, a reference handling function is introduced to view, add and remove references easily, and table filters are added to narrow the view to only the information being sought.
- References inside data containers can be managed directly.
- Table filters make the relevant information easier to find.
- Improves the outcome of data enrichment in complex structures.
Instrument UI — product packaging experience
Applicable to PMDM | Please refer to your Account Manager | Business User | 24.2 highlight | deck slide 3 of 3 in the Instrument UI series
What changed
A structured packaging hierarchy is central to optimizing physical distribution and supply chain efficiency, and product combinations, exclusive retail partnerships, bundles and seasonal offerings complicate it further. With 2024.2, a tailored Product Packaging Experience is introduced, showing where, what and how a product is included in the hierarchy, and allowing pallet set-up and configurations to be viewed and maintained.
- Gives an overview of the product's place in the packaging hierarchy.
- Pallet set-up and configurations can be maintained directly.
- Supports optimization of distribution and product combinations.
Using AI and machine learning to enhance the matching experience
Applicable to Customer, Supplier and Location MDM | Available with the Customer Domain and Supplier Domain license | Admin, Business User | 24.2 highlight
What changed
Building performant matching algorithms is complex, data volumes keep growing, and a conservative approach to merge automation limits an organization's ability to create and govern a trusted single version of the truth. The matching vision is to minimize the burden of defining match rules, put match tuning in the hands of data owners, and use AI and machine learning to enhance and automate the process. 2024.2 advances two initiatives: a new version of the Person Name matcher, part of the pre-trained machine learning matchers that capture industry standard and complex matching edge cases; and improved robustness and scalability of match recommendations through machine learning, where MDM learns from manual duplicate review decisions and provides intelligent recommendations from continuous learning.
- Reduces the skills and effort needed to establish a matching algorithm, supporting faster ROI and easier maintainability.
- Improves matching outcomes and reduces matching setup time.
- Match recommendations improve operational efficiency and productivity through continuous learning.
Loqate cloud address verification update
Applicable to Customer, Supplier and Location MDM | Optional add-on for Customer, Supplier or Location domains | Business User | 24.2 highlight
What changed
A customer MDM solution depends on accurate, verified and current contact data, and Stibo Systems supports address verification and cleansing out of the box through a pre-built connector to Loqate. With 2024.2, the connector is updated to use Loqate's latest cloud API. Any Loqate Cloud API calls are made through the new API automatically once you update to 2024.2.
- Removes the risks associated with staying on legacy APIs.
- Uses Loqate's new AI address parser, lifting verification rates and performance.
- No change to how calls are made — routing switches automatically on update.
PDX user journey enhancements
Applicable to PDX | Business User | 24.2 highlight
What changed
Vendors and retailers syndicating and onboarding product data need a toolkit that lets them act quickly, minimizing repetitive work. The 2024.2 update delivers four improvements: filtering by last updated date range, unlimited product export from channels to spreadsheets, search by any attribute in direct and onboarding channels, and the flexibility to apply conditions on complex-to-flat attribute mappings.
- Less time spent on repetitive actions.
- Faster to locate and export the products that need attention.
- More flexible attribute mapping for channel requirements.
Migration to MongoDB
Applicable to PDX | Admin | 24.2 highlight
What changed
As expectations for speed and volume accelerate, businesses need their enterprise tools to support mission critical operations and scale with them. In the 2024.2 update, PDX migrates to a new database technology, MongoDB, so it can continue to scale as customers grow.
- Supports continued scaling of PDX as customer volumes grow.
- Underpins speed and volume expectations across onboarding and syndication.
- A platform change rather than a change in user-facing behavior.
Working at scale — flags and filters
Applicable to PDX Enhanced Content | Available with the PDX Enhanced Content license | Business User | 24.2 highlight
What changed
Managing enhanced content for a large product assortment requires several steps before it reaches product detail pages, including content top-off and final approval, and existing tools were not scalable enough for large assortments. In the 2024.2 update, reviewed content can be flagged, and a variety of new filtering options let users quickly identify the content records that need action.
- Provides the transparency needed to ensure only high-quality content is sent to retailers.
- Makes it faster to find the content records that need action.
- Supports working across large product assortments.
Dynamic record top-off
Applicable to PDX Enhanced Content | Available with the PDX Enhanced Content license | Business User | 24.2 highlight
What changed
Templates can create publication-ready content for a given channel, but many brands discover new data requirements when they start publishing enhanced content, so templates alone are not the end of the automation journey. In the 2024.2 update, users can flag parts of a template as manually maintained, allowing content to be specified for each dynamic record where upstream data is missing.
- Lets brands maximize automation of content creation despite gaps in upstream data.
- Increases individual productivity as new master data becomes available.
- Further reduces operational cost and time to market.
Enhancement requests delivered with 2024.2
ER 1 applicable to all domains, ER 2 applicable to PMDM | ER 1 included in base, ER 2 available with the Print license | Developer, Business User | 24.2 highlight
What changed
Enhancement requests let the platform adapt continuously to market and customer needs. Two are delivered with 2024.2: the System Setup selector is now available in Mapping when exporting classifications, which is needed to export attribute metadata for attributes linked to classifications; and Automated Datasheet Creation is brought to market, monitoring product data changes and automatically creating or updating standardized datasheet PDF files from a pre-configured, template-based approach, with the resulting file auto-classified and linked to the appropriate product.
- Attribute metadata for classification-linked attributes can be exported.
- Datasheet PDFs stay current automatically as product data changes.
- Removes manual effort from maintaining large numbers of product datasheets.
FAQ
2024.2 introduces the first iteration of Kafka-based inbound message streaming, automates handling of assets stored in external DAM systems, and adds impact analysis to configuration change packages. Matching gains a new Person Name matcher version and more robust machine learning match recommendations, and the Loqate connector moves to Loqate's latest cloud API. The Instrument UI improves reference and link handling, adds translation status monitoring, extends product data containers and introduces a product packaging experience. In PDX, the platform migrates to MongoDB, user journeys are refined, and Enhanced Content gains review flags, filters and dynamic record top-off. Two enhancement requests are also delivered.
Administrators are the main audience for message streaming, configuration impact analysis, asset handling and the PDX MongoDB migration. Business users are targeted by the Instrument UI updates, Loqate address verification, PDX user journeys and both Enhanced Content updates. Developers are addressed by one of the enhancement requests.
The 2024.2 deck does not map initiatives to the Acquire, Manage and Share data journey steps used in later releases. It groups them by applicability instead — all domains, PMDM, Customer/Supplier/Location MDM, PDX and PDX Enhanced Content. Journey step mapping should be confirmed from the release notes before publishing. [Insert / confirm]
Message streaming, configuration impact analysis and automated digital asset handling are included in base, as is the first enhancement request. The AI and machine learning matching updates require the Customer Domain and Supplier Domain license, and Loqate address verification is an optional add-on for the Customer, Supplier or Location domains. Both Enhanced Content updates require the PDX Enhanced Content license, and the Automated Datasheet Creation enhancement request requires the Print license. For the three Instrument UI updates the deck directs customers to their Account Manager. The deck does not state license terms for the PDX user journey enhancements or the MongoDB migration. [Insert / confirm]
Inbound message streaming is delivered as a first iteration in 2024.2, with general availability expected in 2024.4. The deck invites interested customers to try it and share feedback.