Overall update summary
2026.1 works on three fronts. On the platform, the Modular Service Platform gains a Control Service API for automated management, OneQueue gets fairness and throughput improvements, developers get a Visual Studio Code test plugin and extended APIs, and administrators get per-user sFTP access control and the return of basic e-Signature. In PDX, supplier onboarding gains retailer-defined content requirements and clerical review, notifications and system responsiveness improve, the Channel Developer Program opens channel building to partners, and Enhanced Content is visually overhauled. In the New UI, Collections arrive alongside searchable node pickers and unified tab-level issue indicators.
Modular Service API
Platform | Included in Base | Admin, Developer | 26.1 highlight
What changed
The Modular Service Platform introduced in 2025.3 lets plug-ins such as Receivers and Business Functions run independently of the Stibo Systems platform, improving stability and scalability — but managing large numbers of endpoints was manual, with no automated monitoring or control. With 2026.1, a new Control Service API enables REST-based management of Modular Service Platform services, including creating and updating services, starting and stopping them, checking status and retrieving filtered logs.
- Simplifies system management and reduces manual effort.
- Improves operational visibility across services.
- Supports automation in large-scale environments.
Additional resources
Test function in Visual Studio Code
Platform | Included in Base | Developer | 26.1 highlight
What changed
Workbench lets users test JavaScript business rules directly, but Visual Studio Code users had to switch back to Workbench to run tests, breaking development flow even for small changes. With 2026.1 a lightweight Visual Studio Code plugin executes rule tests against the Stibo Systems platform over REST without committing any changes, presenting errors and rule output in Visual Studio Code. The plugin has a minimal UI and is distributed as a manually installed VSIX package.
- Faster feedback loops with no context switching.
- Safer testing, because no permanent saves are required.
- Clearer debugging in a single environment and smoother development of complex rules.
Additional resources
OneQueue background process framework improvements
Platform | Included in Base | Admin, Developer | 26.1 highlight
What changed
The OneQueue background process framework is widely used, but limitations seen across customer solutions held back wider adoption — specific processing scenarios caused uneven capacity distribution and delays in key solution areas. 2026.1 introduces a streamlined execution overview including a Scheduler Status that explains why processing may be temporarily paused, a new fairness mechanism preventing any single user or process type from consuming disproportionate capacity, and overall throughput improvements that allow more processing to be handled at once.
- Better insight into why processing is paused or delayed.
- Reduced wait times through fairer capacity distribution.
- Optimized resource use without compromising stability.
Additional resources
Self-Service UI — sFTP access privileges
Platform | Included in Base | Admin | 26.1 highlight
What changed
The Self-Service UI lets customers manage sFTP user accounts but could not assign differentiated access permissions to individual users, so sFTP users could potentially reach locations beyond what their role or process required — a problem for the many integrations that need strict separation of access. In the 2026.1 Self-Service UI update, administrators can define directory access and access modes when configuring sFTP user accounts, giving precise per-user control.
- Granular, tightly controlled sFTP data access.
- Reduces risk by ensuring users only interact with authorized locations.
- Strengthens security and compliance for sFTP-based integrations.
Additional resources
Basic e-Signature
Platform | Included in Base | Admin, Business User | 26.1 highlight
What changed
Basic e-Signature was deprecated in 2024.4 because of limited usage and compatibility issues with external authentication methods, but some customers must meet regulatory requirements that demand verification of the authorized user performing key workflow steps. In 2026.1, basic e-Signature support is reintroduced, now with optional external authentication through a dedicated re-authentication flow.
- Restores important customer-requested functionality.
- Supports regulatory compliance and workflow continuity.
- Offers flexibility to enforce stronger re-authentication security.
Additional resources
API extension
Platform | Included in Base | Developer | 26.1 highlight
What changed
Microservices interact with the Stibo Systems platform through the existing REST and GraphQL API, which supported basic data operations but lacked broader system-setup capabilities and required developers to write low-level REST calls by hand. 2026.1 introduces Service API client stubs that enable REST calls directly from Java and Modular Service Platform code, removing the need for low-level network-handling code, together with REST API v2 enhancements including new and updated endpoints.
- Broader and safer API access for microservices.
- Easier development through typed client stubs.
- Consistent, non-breaking REST improvements that extend coverage and performance without affecting compatibility.
Additional resources
Onboarding — enhanced content validation and review
PXDC / Acquire | Available with the PDX Onboarding license | Admin, Business User | 26.1 highlight
What changed
Inconsistent formats, quality issues and limited validation tools have required major manual effort from retailers onboarding supplier content, driving significant operational cost in the pursuit of high-quality listings. With 2026.1 the onboarding flow is extended with three capabilities: retailer-defined content requirements for administrators, clerical review before publication for business users, and a feedback loop to Enhanced Content Syndication.
- Greater retailer control over what content is accepted.
- More consistent content and streamlined collaboration with suppliers.
- Higher-quality product detail pages, driving customer engagement.
Additional resources
Expanded product status notifications
PXDC / Acquire & Share | Available with the PDX Onboarding license and the PDX Syndication license | Business User | 26.1 highlight
What changed
Email notifications covered only a limited set of statuses, giving users minimal visibility into product progress and no confirmation when products were accepted or retrieved. With 2026.1, notifications expand to include an Accepted status when products move from submitted to accepted, and a Retrieved status when products are added to a channel from a retailer's PIM.
- Improves transparency and user confidence.
- Makes onboarding and maintenance flows easier to track.
- Enhances operational efficiency through actionable notifications.
Additional resources
System responsiveness for suppliers
PXDC / Acquire | Available with the PDX Onboarding license | Business User | 26.1 highlight
What changed
Brands working with a small set of products faced waiting times disproportionate to the size of the task, making the system feel unresponsive and reducing confidence in the application. With 2026.1, the way job queues are processed changes, significantly improving responsiveness when working with small sets of products.
- More efficient experience for smaller brands.
- Faster system feedback on small tasks.
- Greater confidence in the application.
Additional resources
- Youtube chapter: Watch
Auto Care schema changes
PXDC / Acquire, Manage, Share | Available with the Auto Care license | Admin, Developer | 26.1 highlight
What changed
Automotive data is increasingly complex, global and content-heavy, but current standards for reference data, ACES and PIES lack strong multilingual support, detailed packaging data and advanced asset management — leading to manual work, duplicated effort and delays. With 2026.1, support is introduced for the latest schema changes to Auto Care reference data (VCdb, Qdb, PCdb, PAdb and Brand tables), to be followed by full support for the latest ACES and PIES standards in subsequent releases.
- More accurate and consistent automotive data.
- Faster onboarding and product changes.
- Expanded global reach through multilingual support.
Additional resources
Match tuning by data owners
CXDC, BPDC, SDC / Manage | Early Adopter Release | Admin | 26.1 highlight
What changed
Super users maintained matching algorithms with limited visibility into rule accuracy and underlying data quality issues, making collaboration with data owners difficult and every adjustment dependent on technical expertise. With 2026.1, a shared overview of match accuracy and data quality issues lets super users and data owners review potential matches together and refine the algorithm more effectively. Future updates will let data owners create and manage match rules directly.
- Faster tuning with fewer errors and less manual effort.
- Improved collaboration between super users and data owners.
- A path toward business-driven matching without relying on technical specialists.
Additional resources
Self-service onboarding channel enhancements
PXDC / Manage | Available with the PDX Onboarding license | Admin | 26.1 highlight
What changed
Channel Portal offered basic Data Standard synchronization and channel viewing but lacked full self-service and clear visibility into Data Standard generation, leaving retailers and partners with limited automation, poor transparency and complex troubleshooting. 2026.1 adds self-service tools for channel refresh and scheduling, email notifications for Data Standard generation status covering success, warnings and failures, and an improved UI for monitoring and troubleshooting.
- Simplifies channel management and improves visibility.
- Reduces manual effort through self-service and proactive alerts.
- Enables onboarding to scale.
Additional resources
- Youtube chapter: Watch
Expanded conditional expressions
PXDC / Manage | Included in Base | Admin, Business User | 26.1 highlight
What changed
Users working with complex data lacked dynamic validation, leaving attribute requirements static and prone to error, and the expression language could not cover common comparison scenarios as business rules grew more complex. In 2026.1, additional comparison operators are introduced in conditional expressions, including less than, greater than, less than or equal to, and greater than or equal to.
- More real-world conditional scenarios can be solved without JavaScript.
- Reduces complexity and improves maintainability.
- Makes conditional logic more powerful while staying approachable to configure.
Additional resources
Partner-managed channels
PXDC / Share | Requires a Channel Revenue Sharing Agreement and the PDX SDK License Agreement | Admin, Business User | 26.1 highlight
What changed
PDX lets brands syndicate product data through Channels, where Direct Channels are API-based integration points defining the content, format and delivery mechanism for receivers such as retailers, marketplaces and data pools — and these have been developed and maintained by Stibo Systems. Syndication customers need channels with complex integrations that Configured Channels cannot always handle, and partners had no formal way to build and publish them. The PDX Channel Developer Program opens Direct Channel development to external developers and partners, with a Channel API, documentation and a Channel SDK.
- Partners can build advanced channels and publish them in the PDX Channel Marketplace.
- Creates new revenue streams for partners.
- Expands channel availability for all PDX users.
Additional resources
Enhanced Content display
PXDC / Share | Available with the Enhanced Content license | Business User | 26.1 highlight
What changed
An increasingly competitive marketplace requires brands to deliver more engaging, high-quality experiences across channels, and existing content formats limited their ability to do so. 2026.1 introduces three enhancements: a visual overhaul across all modules, 50% increased content width to accommodate larger imagery for storytelling, and responsive content design for high-fidelity presentation across all devices.
- Stronger visual appeal, helping products stand out on the digital shelf.
- Improved storytelling capabilities.
- Consistent brand experiences across all devices.
Additional resources
- Youtube chapter: Watch
Improved column and field selection in node pickers
PXDC / Manage | Please refer to your Account Manager | Admin | 26.1 highlight
What changed
Content managers and administrators struggled to find the right columns, fields and attribute groups because node pickers offered no effective search — browsing hierarchies was slow and identical names in typeahead made selection unreliable. With 2026.1, a search tab is added to Customize View and all configuration node pickers, allowing search by name and ID with clear icons. Typeahead shows both name and ID, results respect “Show in Workbench” rules, and searches cover all relevant column and field types.
- Users locate the right items without navigating deep hierarchies.
- Configuration becomes faster and more accurate.
- More consistent setups, especially where many names are similar.
Additional resources
Unified tab-level issue indicators
PXDC / Manage | Please refer to your Account Manager | Business User | 26.1 highlight
What changed
Users lacked a clear overview of an object's data quality, with validation signals scattered and complexity making problems hard to find without deep manual inspection. With 2026.1, a unified indicator presents all stored validation issues in a single counter per tab, reflecting the highest severity and updating automatically as issues are resolved. A tooltip summarizes issue types, and the indicator covers tables, reference structures and invalid or orphaned data while excluding temporary input feedback.
- Users quickly see where issues are and how severe they are.
- Less time spent searching for problems, and improved data quality.
- A smoother, more confident workflow for complex objects.
Additional resources
Collections in the New UI
PXDC / Manage | Please refer to your Account Manager | Admin, Business User | 26.1 highlight
What changed
Users often work with massive datasets but need only a small relevant subset, and the New UI offered no efficient way to create, monitor and manage collections — increasing operational overhead and slowing decisions. With 2026.1, Collections support arrives in the New UI: users can browse and work with search-based collections, refresh them, and manage non-search-based collections by adding or removing items directly.
- Improves focus and collaboration by letting users work with the most relevant data sets.
- Reduces manual effort and distraction.
- Accelerates decision-making across teams.
Additional resources
FAQ
2026.1 adds a Control Service API for managing Modular Service Platform services, improves OneQueue fairness and throughput, and gives developers a Visual Studio Code test plugin and extended APIs. Administrators gain per-user sFTP access control and the reintroduction of basic e-Signature. In PDX, onboarding adds retailer-defined content requirements and clerical review, notifications and responsiveness improve, the Channel Developer Program opens channel building to partners, and Enhanced Content is visually overhauled. The New UI adds Collections, searchable node pickers and unified tab-level issue indicators.
Administrators are the main audience for the platform and onboarding-configuration updates. Developers are targeted by the Modular Service API, the Visual Studio Code plugin, the API extension and Auto Care schema changes. Business users are targeted by onboarding review, notifications, supplier responsiveness, Enhanced Content display, issue indicators and Collections.
Acquire covers onboarding content validation, system responsiveness for suppliers and expanded status notifications. Manage covers match tuning, onboarding channel enhancements, conditional expressions and the three New UI updates. Share covers partner-managed channels and Enhanced Content display. Auto Care schema changes span Acquire, Manage and Share, and the six platform updates are platform-level.
The platform updates and expanded conditional expressions are included in base. PDX onboarding updates require the PDX Onboarding license, and expanded product status notifications require both the PDX Onboarding and PDX Syndication licenses. Auto Care schema changes require the Auto Care license, Enhanced Content display requires the Enhanced Content license, and partner-managed channels require a Channel Revenue Sharing Agreement and the PDX SDK License Agreement. Match Tuning by Data Owners is an Early Adopter Release. For node picker search, unified issue indicators and Collections in the New UI, the deck directs customers to their Account Manager.
Yes. Match Tuning by Data Owners is an Early Adopter Release, accessed by emailing simplifymatching@stibosystems.com. Auto Care support is staged, covering reference data schema changes in 2026.1 with full ACES and PIES support in later releases, and match rule creation by data owners is stated as coming in a future update.
Links to the 2026.1 update notes, overview video, YouTube chapters and overview deck are listed under Supporting assets. [Insert / confirm]