Tool news

66 news

1C
Reduction of boxed deliveries for standard 1C:Enterprise 8 products

The release of boxed versions of standard products is being reduced as distribution shifts to electronic delivery.

1C
Joint project using the Demand Driven MRP (MRP 3.0) methodology on the 1C platform

A joint project was announced to implement the DDMRP methodology (MRP 3.0) on 1C:Enterprise for supply management in unstable conditions. It is accompanied by a series of webinars based on 1C:ERP.

MRP module with replenishment rules built into the core Odoo →
1C
Release of 1C:ERP WE version 2.5.27.52

A new release of the standard 1C:ERP WE 2.5.27.52 configuration has been issued; related 2.5.27 releases updated the ERP/KA and UT stacks.

1C
“Compatible!” certificate for 1C:UT and Customer Relationship Management (CRM) 3.1

Compatibility has been confirmed for the sales management suite with the built-in CRM v3.1 features and the CRM module for 1C:ERP.Holding Management.

CRM is the product core, not a separate module 1C-Bitrix →CRM is built into a unified ERP core Odoo →
Anthropic Claude
US orders Fable 5 and Mythos 5 disabled for all foreign users

Three days after release, a U.S. export directive required Anthropic to disable access to Fable 5 and Mythos 5 for all foreign nationals inside and outside the country. Closed weights in a vendor cloud can be revoked instantly by regulators, leaving enterprises with no lever to preserve access.

1C
Mandatory transition to electronic transport documents (ETD) from September 1, 2026

1C launched a training program for the mandatory transition to EPD from 01.09.2026; support is being implemented in sales and ERP configurations. A regulatory requirement in CIS.

MCP
MCP 2026-07-28 RC: stateless core, session ID and initialize handshake removed

The RC removes the initialize handshake and sessions: state is passed via explicit handles, follow-ups go through InputRequiredResult without SSE. Load balancing over plain HTTP without sticky sessions.

Loose coupling and stateless scaling have long been the norm for brokers; MCP is only arriving at this now. Apache Kafka →Load balancing of stateless calls over HTTP is handled by the ESB/API gateway; MCP moves it into the protocol. MuleSoft →
Magento
Adobe Commerce released Commerce MCP Server for AI agent access to the catalog and checkout

An MCP server was announced at Adobe Summit 2026: AI agents gain access to the catalog, cart, prices, stock and checkout. It depends on the Integration Starter Kit and AppBuilder.

MCP is the agent access protocol itself (see /instruments/mcp); Magento only wraps its API in MCP MCP →API-first and GraphQL-native are built into Saleor from the start; Magento is catching up by wrapping its monolith in MCP Saleor →
MCP
2026 MCP Roadmap published: shift to a Working Group model

The roadmap sets 4 priorities (transport, agents, governance, enterprise) and a shift from a release-centric plan to Working Groups. Enterprise via extensions, not the core.

The enterprise bus was built for audit trails and manageability from the start; MCP is only now building governance through modules. Datareon →
Apache Kafka
Kafka 4.2.0: queues (share groups, KIP-932) are now production-ready

Share groups declared production-ready: consumers read the same partitions with per-record acknowledgment — a classic queue on top of Kafka.

Point-to-point with guaranteed delivery and confirmation is Datareon's standard bus model. Datareon →Queues and point-to-point messaging (JMS/Anypoint MQ) are a long-standing core MuleSoft pattern. MuleSoft →Queues with per-message acknowledgment and dead-letter handling were an ESB standard in Talend ESB long before KIP-932. Talend ESB →
Akeneo
Akeneo Winter Release: native MCP server as a data management layer

Akeneo released a native MCP server: the catalog as resources, agent edits as tool calls, and server-side quality rules. The release also includes Digital Showroom and Custom Components

Akeneo is not inventing MCP, but implementing an existing standard on top of PIM; the protocol itself is described separately. MCP →MCP serves the catalog via synchronous tool calls; for event-driven integration an event bus delivers the same effect. Apache Kafka →
Akeneo
Akeneo and Stripe partnership: Agentic Commerce Suite

In its Winter Release, Akeneo announced a partnership with the Stripe Agentic Commerce Suite: product discovery by AI agents and acceptance of agent payments. The release's MCP server is covered separately

Stripe and the MCP server are separate release components; the value lies in the connector to the payment provider. MCP →
Odoo
Odoo expanded Indonesia localization: e-Faktur, Shopee, local payments

Odoo detailed its Indonesia localization package: Coretax XML e-Faktur, native Shopee, Xendit, and InterActiveQRIS integrations, plus tax adjustments. For ERP projects this signals that localization is becoming an architectural decision, not an after-the-fact add-on.

Magento covers the e-commerce perimeter, but tax compliance and ERP localization typically require a separate accounting system or integrations Magento →
1C
Final release of the 1C:Enterprise 8.5.1 platform

The final 8.5.1 release of the 8.5 line is out, with a new interface (light/dark theme, beta status within the release) and backward compatibility with 8.3. UNF 3.0.13, Retail 3.0.13, and Cashier Workstation 1.1.1 were updated at the same time.

web-native interface and built-in themes for a long time Odoo →
Odoo
Odoo and QFPay HK Announce a Partnership for Offline Retail and F&B POS

The partnership combines POS ordering, a payment terminal, and backend management in Odoo for retail and F&B in Hong Kong. In practical terms, Odoo continues to strengthen scenarios where ERP, POS, and payments must work as a single operational flow.

Magento excels at storefront, catalog, and checkout; POS and payment flows are usually assembled via third-party modules Magento →
Pimcore
Pimcore Platform 2025.4: experimental MCP server and 3-year LTS

The last release with Admin UI Classic alongside Studio. An experimental MCP server reads data over Elasticsearch/OpenSearch. Symfony 7 alongside 6.4, with 3-year LTS.

MCP endpoint in Datahub Simple REST — the same LLM access protocol as in the catalog (/instruments/mcp). MCP →MCP access relies on the Elasticsearch/OpenSearch index (/instruments/elasticsearch). Elasticsearch →Reading an LLM catalog on top of an index follows the same grounding pattern as RAG (/instruments/rag). RAG →
Saleor
Official Saleor × Adyen partnership

Saleor shipped an official Adyen integration for international payment acceptance and refunds. It is implemented through the App model rather than a built-in core plugin.

Odoo
Odoo Awards 2025 highlighted partner ecosystem growth

Odoo wrapped up its 2025 Partner Awards at Brussels Expo, recognizing integrators across Europe, the Americas, Africa, and MENA. For buyers this is not a product feature but an indicator of the platform's implementation network maturity.

Pimcore
Pimcore Platform 2025.3: Copilot on OpenAI Chat Completions, documents in Studio

Copilot generates text through Chat Completions, so it connects to different LLM providers (OpenAI, Hugging Face, RunPod). Documents appears in Studio for the first time (preview).

Chat Completions uses the same interface that the LLM gateway intercepts (/instruments/llm-gateway). LLM & Security Gateway →LLM-based product content generation overlaps with Akeneo GenAI (/instruments/akeneo). Akeneo →
MCP
Official MCP Registry launched (preview)

A public catalog and API of MCP servers opened at registry.modelcontextprotocol.io (Anthropic, GitHub, PulseMCP, Microsoft). Preview, with no data guarantees and breaking changes until GA.

Akeneo
Data Architect Agent: automatic PIM data model generation

Akeneo introduced its first AI agent, Data Architect Agent: based on sample product files and context, it drafts a data model. GA for Product Cloud is July 12, 2025

GenAI assistants in PIM are not unique: Pimcore's GenAI/Copilot arrived earlier, and the data model is already there. Pimcore →
Sber GigaChat
GigaChat 2 (Lite/Pro/Max): longer context, CIS environment

The GigaChat 2 lineup expanded context and quality. For CIS enterprise, data processing in CIS data centers and ruble pricing matter more than open weights: the flagship remains cloud-based.

Yandex YandexGPT
YandexGPT 5 Lite: partially open lightweight model

Yandex published a lighter version of YandexGPT 5 Lite with an open pretrain checkpoint, but it is a lightweight model, not a flagship. The senior models remain cloud-based and closed.

Sber GigaChat
GigaChat MAX: Sber's top-end version, processing in CIS data centers

Sber introduced GigaChat MAX as the top-end version of the line. The model runs in a CIS cloud with ruble billing and claimed compliance with GDPR; the flagship weights are closed.

Discuss the news and your stack

Send via: