Roadmap
Release Plan
| Extensions | Version | Release Date | BC 27.0 (2025 wave 2) | BC 26.0 (2025 wave 1) | BC 25.0 (2024 wave 2) | BC 24.0 (2024 wave 1) | BC 23.0 (2023 wave 2) |
|---|---|---|---|---|---|---|---|
| Pimics PIM | 13.1 | April 2026 | Yes | Yes | Yes | No | No |
| Pimics PIM | 14.0 | July 2026 | Yes | On Request | No | No | No |
We support both architectures so Pimics is available for cloud and also on-premise installations. We follow the Modern Lifecycle Policy and release cycle of Microsoft, so every year we release two main versions of Pimics for all Business Central versions in the current lifecycle. More details are available here: Product Roadmap, Releases and Supported Versions.
TODO
###Business Central 2026 release wave 1 Version 12.0.2 is the first version compatible with Business Central 2025 release wave 2 (version 27.0)
Next release
Pimics PIM 13.1
TODO
####Breaking changes | Breaking changes | Notes | | - | - | | Extension Pimics Base | The extension will be required for all other extensions. Some tables will be moved to this extension |
New features
| Identification | Title | Summary |
|---|---|---|
| #33328 | Publication Rule: Hide empty group | Adds a publication rule to automatically remove empty groups, chapters, and categories after reorganization, while always keeping the root structure. |
| #34338 | Improve Sana Commerce add-on | Improves the Sana Commerce add-on by aligning product APIs, setup flow, HTTP handling, and SharePoint image configuration for more stable integration. |
| #34868 | History - Create version when archived | Adds automatic version creation when items, categories, or documents are archived, controlled by new History options in setup. |
| #35392 | Description Text - Placeholders | Adds placeholders in description texts to dynamically insert master-data fields and filtered values, with support for preview generation. |
| #35760 | Resolver Group and checklists | Adds Resolver Groups and members so checklist and data-resolution responsibilities can be assigned to user groups instead of single users. |
| #36700 | Assisted Setup | Introduces a step-by-step Assisted Setup wizard guiding administrators through post-installation configuration of user licenses, permissions, retention policies, application areas, and job queues, with completion state tracked in Catalog Setup. |
| #37761 | Provide ModifiedDate of images to Sana | Extends the Sana Commerce image response to include a ModifiedDate field, enabling Sana to skip re-import of unchanged images and significantly reducing image synchronization time after large product updates or full index rebuilds. |
| #38692 | Publication Group configuration for cross-referenced categories | Extends publication group configuration to support cross-referenced categories in the same way as cross-referenced items. |
| #38713 | Entitlements for Pimics PIM | Defines BC-native entitlements for Full User, Read-Only, and No License user types, replacing the Catalog User table and aligning Pimics licensing with the AppSource entitlement model. |
| #38831 | InDesign - endpoint for flat JSON data structure | Adds an Azure Functions endpoint that exports publication data as flat JSON with selectable levels and fields, optimized for EasyCatalog and InDesign loading. |
| #38840 | Pipeline Actions | Introduces an extensible pipeline action framework with configurable actions such as Certify, Certify Channel, Run Checklist, and Webhook. |
| #38872 | ETIM 10 - Feature Groups | Adds ETIM 10 Feature Group support by preparing the data model, import logic, and upgrade handling for newer ETIM structures. |
| #39378 | Review Update By Publication Log | Reviews the Update By Publication Log feature by adding automated test coverage for key scenarios, documenting open issues, and proposing improvements to ensure reliable propagation of publication changes to items and categories. |
| #39423 | Publication Excel - Export / Import mapping including Source Record Type | Extends Publication Excel export/import mappings to preserve the Source Record Type field, ensuring mapping definitions correctly round-trip all record types instead of defaulting to Master. |
| #39905 | Bulk edit for Catalog items | Adds bulk editing support for Catalog Items, allowing simultaneous changes to Description, Manufacturer Code, Unit of Measure, Checklist Number, Picture ID, Item Template Code, and System Status across multiple records. |
| #40037 | IF conditions on fields for checklist relation lines | Extends the IF-condition framework to checklist relation lines, so that each relation is only applied during certification when its configured field conditions are satisfied. |
| #40440 | Checklist Relations - check Parent Allocation / Child Allocation | Adds two new check types to checklist relations: Parent Allocation (verifies items or categories are allocated under a required parent) and Child Allocation (verifies categories contain required child allocations), enabling stricter certification rules. |
| #31182 | Support all possible Sana Entity Field Types for Pimics Features | Extends Sana integration to support a broader range of Sana entity field types for Pimics features, improving typed data transfer beyond basic string/decimal handling. |
| #36818 | Sana publication update line interface: Channel-specific descriptions | Enables Sana publication update processing to use channel-specific master-data descriptions, aligning Sana output with channel-tailored content. |
| #37395 | Synchronize items in cross-referenced categories to Sana | Adds synchronization logic that resolves category cross-references into related item sets for Sana, including category-expansion scenarios. |
| #37762 | Sana publication line data: Prepare general image and attachment data separately from file retrieval data | Splits Sana publication data preparation into general metadata and file-retrieval payloads for images and attachments, reducing duplication and improving maintainability. |
| #38565 | Cross Reference for Catalog Item | Enables cross-reference management on Catalog Item records, including proper filtered navigation and lifecycle handling during activation and deletion. |
| #39652 | Publication API v2.1 | Introduces Publication API v2.1 as a new beta version with updated OData keys, versioned endpoints, and a deprecation path from v2.0. |
| #40458 | Pipeline - Certification & Non Certified Pipelines | Adds support for controlled use of non-certified pipelines with warnings, version-0 state handling, and checksum validation to prevent execution of changed pipeline definitions. |
Pimics - Vendor Catalog 12.2
This version will have a dependency on Pimics base.
| Identification | Title | Summary |
|---|---|---|
| #37146 | MCP server for importing data using AI Agents | Implements an API for Vendor Catalog to support data imports via AI agents and Copilot through the Model Context Protocol (MCP), introduces a new API import type for automated sessions, exposes master data definitions (features, values, keywords) with rich metadata for AI, and ensures compatibility with BC27 MCP server configuration for AI-driven Vendor Catalog workflows. |
In process
These features are partially done or we have a Proof of Concept.
TODO
Import from PDF (powered by AI)
In many cases vendors are able to deliver only product data sheets, without any easily importable data. These days AI is able to analyze the document, get the context of data, and create these products the same way as other imports from Excel, XML, or others.
Pimics Agent
The Pimics AI Agent will introduce advanced automation for product data management, transforming how users create, enrich, and maintain digital product materials. Leveraging natural language processing (NLP), the agent will convert unstructured text from sources like websites and brochures into structured product attributes, streamlining onboarding and updates. It will also generate marketing texts from structured data, enabling bulk content creation through intuitive chat-based commands. Context-aware data enrichment will help users identify and correct attribute inconsistencies, ensuring compatibility with distribution channels. Additionally, the agent will support sophisticated image management, allowing users to instruct the system to add or modify product images according to channel requirements. Finally, dynamic selection and modification of product groups via natural language will replace manual spreadsheet operations, making data handling faster and more user-friendly.
Printed Catalog Experience
Printed catalogs are often intensive in manual work, and details matter. Organizing products into manual groups or pages, selecting and moving images or text for multiple items at once, or copying the existing publication for the new season to make the update. These features could help users prepare content for publication easier and quicker, enhancing productivity.
Visual Tables
Tables are a simple way to compare products. You just need to define columns and rows with items, features, etc., and the table will show you the most important differences. We think they will be mostly useful with InDesign or e-commerce channels, where customers need to quickly review a range of similar products. In the past, we had this concept in Pimics for NAV, but we haven't migrated it into the Business Central version yet.
Planned
Here are features that will be in one of the next releases.
Suggest New Products (powered by AI)
This function covers the process of transformation of generic text into structured data in Pimics. It should help with creating new items and also updating existing items.
Custom XML Export
All XML exports from Pimics currently need to be defined by a developer or by a consultant. We'd like Pimics users to be able to define their own XML structure in an export mapping and decide which data should go to which element. This export will be available from publications.
Pipeline & Workflow
The proposed workflow and process pipeline functionality will significantly enhance operational efficiency and transparency by enabling structured, configurable process management within the system. By allowing users to define custom workflows, states, and associated actions, organizations can standardize procedures, ensure compliance, and automate repetitive tasks. Integrated logging and version control provide full traceability of changes and actions, reducing risk and improving accountability. This flexibility empowers businesses to adapt processes to evolving requirements without sacrificing control, ultimately accelerating product lifecycle management and improving collaboration across departments.
Ideas
Here are ideas for new features that we're discussing with our customers.
Working with Dynamic ETIM
ETIM recently introduced the concept of dynamic classification. As such, it will be updated on a regular basis and not released as official versions like 6, 7, 8, etc. In Pimics we need to be able to read the new structures (using API) and to define the processes to update existing data in Pimics instances using the dynamic ETIM classification.
Product texts
We'd like Pimics users to be able to insert dynamic macros into the product texts. A macro can be for example a value of a feature, or maybe another text. Combined with inheritance, this should speed up text preparation significantly, and also add to product data consistency. For this, we would need to make some pretty extensive changes to several data structures and background functionality. We need to also find a balance between macros in product texts and the current functionality for defining content, where users will always have more flexibility to prepare layouts for web or exporting to PDF.
Channel Overview & Categories
We would like to add the option of visualizing and managing product trees according to channels, each with their own category structures and item allocations.
Price management
We would like to extend the current Pimics functionality for handling purchase prices, with additional functionality to be able to insert additional costs to your standard vendor cost, set minimum profit margins, take market prices into consideration, handle currency conversions, etc. That will make it easier for you to have meaningful retail prices, that Business Central can further use in the process of selling.