Release Notes - Febraury 2026 - Backend
This release cycle introduces several major improvements to the platform focused on three key areas: asset publishing for sellers, flexible delivery and payment terms, and a better experience around RFQs (Request for Quotes). In addition, a number of reliability fixes and usability improvements have been made across the board.
Highlights at a Glance
- Sellers can now publish and manage their assets directly on the marketplace
- Delivery and payment terms are now fully configurable for trades (spot, standard, and custom)
- RFQ invitations can now be filtered, and participant handling has been improved
- Clearer messaging when user accounts are expired or deactivated
- Improved data accuracy for trade contracts and related documents
- Performance improvements for news and interest feeds
What's New
Asset Publishing
Sellers now have the ability to publish assets directly from their company profile. Published assets become visible to potential buyers on the marketplace.
- Publish assets — Sellers with the appropriate role can publish assets for sale, including vintage information.
- Unpublish assets — Assets can be withdrawn from the marketplace at any time.
- View published assets — A new endpoint allows retrieval of currently published assets.
Flexible Delivery and Payment Terms
A significant upgrade to how delivery and payment timelines are handled across all trade types. Previously, these were largely fixed; they are now configurable and clearly displayed.
- Pre-delivery days and payment days — Trades now carry explicit delivery and payment day counts, giving both parties clear expectations on timelines.
- Spot trades — Existing spot trades have been migrated to use 5 pre-delivery days and 5 payment days as the default.
- Standard trades — Historical standard interests and trades have been converted to a new "Legacy Standard" category to distinguish them from the new flexible format.
- Improved date calculations — End-of-day and delivery date logic has been refined for better accuracy across time zones.
RFQ (Request for Quote) Improvements
- Filtering on RFQ invitations — Users can now filter and search through their RFQ invitations and limited RFQs, making it easier to find relevant requests.
- Unique participants — The system now ensures that RFQ participant lists contain no duplicates, preventing confusion and duplicate notifications.
Improvements
User Account Handling
- Clearer error messages — When a user account within a company has expired or been deleted, the platform now shows a clear, human-readable message instead of a generic error. This applies to trade-related features and other company-level functionality.
Trade Contract Data
- Complete trade contract information — Fixed an issue where certain fields were missing when trade contract data was sent to external processing (Azure Functions). All relevant data is now included.
- Correct formatting — Resolved minor formatting issues with payment dates and delivery descriptions in trade documents.
Database and Performance
- Faster news and interest feeds — Improved database indexing for news messages and interest listings, resulting in quicker load times.
- Better data integrity — Updated database schema to enforce stricter constraints on key fields such as maximum capacity unit and product group.
- Audit trail — Database save operations now record which user made the change, improving traceability.
Internal Reliability
- Fixed a bug where buying a spot interest could fail under certain conditions.
- Fixed an infinite loop that could occur during the creation of special delivery terms.
- Resolved test failures related to execution approval workflows.
- SignalR hub deployment — Improved the build and deployment pipeline for real-time notification components.
Migration Notes
- All existing spot trades have been automatically converted to carry 7 pre-delivery days and 7 payment days.
- All existing standard interests and trades have been re-categorized as "Legacy Standard" to distinguish them from newly created ones using the updated format.
- No action is required from users — these migrations were applied automatically.
47 changes included in this release cycle across 14 deployments.