Release Notes 1.3.0.14
Release Date: 06.09.2026
These release notes focus on the most important new features and improvements, independent of the development effort behind them and based on what they say. Continuous internal work on software architecture, performance and system stability happens as well, but is not listed explicitly.
Interface now available in English too
TRADElube can now be operated in English as well. The buttons "DE" and "EN" at the top right switch the language of the current session, immediately and until logout. Anyone wanting to work in English permanently sets that in the "Language" field of their own user account; that default language then also applies to emails TRADElube sends without an active session.
The language of the interface is independent of the language of the data: you can operate TRADElube in English and still maintain German product texts.
Substantial expansion of the documentation
The documentation has been expanded significantly. New are a getting-started section that walks new customers through the first steps once, a full reference for every area of the interface and the connected systems, and concepts that explain why TRADElube does something the way it does. The existing guides have been expanded significantly as well and now walk you through a specific goal step by step.
The bottom of every page links straight to the previous or next page, one step of a guide to the next for instance, with no detour through the overview.
The documentation is now available in English as well, switchable via the "DE" and "EN" buttons at the top right; pages not translated yet show the German version in the meantime.
Automatic retries after brief database faults
Transfers, a product upload or an order download for instance, occasionally ran into an error message like this one:
Deadlock found when trying to get lock; try restarting transaction
Messages of that kind, a dropped connection among them, come from brief technical faults on the database server or in the network, and there is no direct influence on them from outside. TRADElube now recognizes purely technical faults of this kind and repeats the affected save in the background on its own (three retries), so the operation usually finishes without a visible error message.
Errors that point at a real problem, faulty or incomplete data for instance, are still reported as before.
Fixing the cause instead of the symptom is a standing quality criterion at TRADElube. This case is a deliberate exception: the underlying fault cannot be prevented for technical reasons, which makes an automatic retry the most sensible solution here.
Duplicate order numbers after a database fault
In connection with the brief database faults described above, an order download could in very rare cases release an order number that had already been assigned. The next new order then ran into an error message like this one:
Duplicate entry '61076' for key 'idx_tlb_order_OrderNumber'
After that no further new orders could be created either. The assignment of order numbers now releases a number only where it is beyond doubt that the order behind it was in fact not created.
Automatic restart of a blocked background service
The trigger was a single incident, the only one so far: the service that runs the tasks in the background came to a standstill. The interface stayed available, but no tasks were running any more, so transfers simply stopped happening without an error message pointing at it. Only a restart by support helped.
TRADElube now recognizes a standstill of this kind on its own and restarts the affected service automatically, so the tasks carry on without anyone stepping in. Brief faults, a temporarily unreachable database for instance, are still bridged patiently and do not lead straight to a restart.
Error when categories are created for the first time
The task "Shopware Categories Upload" could occasionally report an error the first time a category tree was synchronized, because the parent category did not exist yet.
TRADElube has in fact always created categories in the right order, the parent category first and its subcategories after it. An internal check for whether a parent category already exists, however, wrongly counted a category from an entirely different channel as "already there". In such cases a subcategory was created before its parent category existed in the Shopware shop itself.
The effect was small: affected categories were corrected automatically on the next synchronization, as soon as the parent category had been created. The check has now been corrected, so the error does not occur in the first place.
Properties now for every object type, and with groups
Freely definable properties used to be available for products only. Under "Settings" > "Properties" they can now be created for all the main object types: products, manufacturers, categories, media, orders and customers. Characteristics of your own can therefore be held on a customer or a category as well, with no individual adjustment needed for it.
Properties that belong together can also be bundled into groups you name yourself, "Technical data" for specification values for instance, or "Appearance" for selection properties such as gloss level and color shade. On the object itself, on the product for instance, these groups appear as separate, clearly delimited sections.
Automatic ordering in properties, stores and prices
Creating or moving an entry in the settings for properties, stores and prices used to mean maintaining the position numbers of the remaining entries by hand, so that the order stayed consistent. TRADElube now takes care of that: put an entry at a particular position or move it with an arrow button, and the entries affected shift along by themselves.
The same holds for the options of a selection property, the individual color shades for instance. There an alphabetical ordering comes on top of it.
Sorting selection properties alphabetically
The configuration of a selection property under "Settings" > "Properties" carries the new setting "Sort Alphabetically". With the box ticked, the property options order themselves alphabetically throughout. That covers options created automatically during an import as well: a color shade arriving as new slots straight into the right place instead of being appended at the end. The buttons for moving an entry then fall away, and the Position column only shows the order that results.
For an order of your own that the alphabet does not suit, sizes from S to XXL for instance, take the tick out and order the options with the buttons "Move Up" and "Move Down" as described above. The alphabetical order visible at that moment is kept as the starting point.
On a newly created selection property the box is ticked by default.
What happens to existing properties
The upgrade checks every existing selection property. Properties where no position numbers, or only isolated ones, were maintained so far, which is the usual case, are switched to alphabetical ordering. Properties with an order maintained throughout keep it unchanged. No manual adjustment is needed.
Transfer into the shop
The upgrade changes nothing about the order in the shop. On the properties now sorted alphabetically the position stood at 0 on every option, so the shop was given no order by TRADElube in the first place. To keep it that way, the assignment "Position" is removed automatically for these properties in the tasks "Shopware Properties Upload" and "WooCommerce Properties Upload". Transferring a 0 has the same effect in the shop as transferring nothing at all, so an order adjusted there by hand is preserved.
Where the shop should take the order from TRADElube instead, activate the assignment "Position" in the transfer plan of the task in question. What is transferred then is the actual order, so the shop shows the same sorting as TRADElube.
A clearer split of the product data
On the product the former section "Specification", which had bundled the subsections Measures & Packing, Shipping and Properties, has been dissolved. Those sections are now available as independent sections of equal rank, which gets you to the information you are after faster. The shipping settings were merged with the stocks section into the new section "Stocks and Shipping".
Position field removed from order, shipping and payment status
The position field that had to be maintained by hand has been removed from the settings for order status, shipping status and payment status. The order of the entries follows automatically there now.
Skipped stocks after a manually deleted channel mapping
Where the channel mapping of an already existing product to the TriData channel was deleted by hand and the task "TriData Stocks Download" then ran before the task "TriData Products Download", the entry stayed skipped, even after the product import had restored the mapping. The stock was only updated again once it changed in TriData.
That was a special case, because it could not happen with newly created products. Skipped entries are now marked again automatically as soon as a product is newly linked to the channel.
Inheritance from the parent product on boolean and numeric fields
In the transfer plan of the task "Shopware Products Upload" the source "Inheritance From Parent Product" no longer reached the shop on some assignments in the area "Product Variant". Instead of the inheritance a fixed value was transferred, False on boolean fields and 0 on numeric fields. Affected were "Active", "Highlight Product", "Restock Time", "Free Shipping" and "Closeout", and only since the 1.3.0 series. Up to version 1.2.1 the inheritance worked correctly on these fields as well.
Variants carrying a wrong value are corrected on the next transfer. The exception is "Closeout": the assignment is set to "Only on Insert" by default and is not transferred again for existing variants. Take the tick out once and the correction is made up for, then for all products though. That only makes sense where the closeout flag is meant to come from TRADElube throughout, because flags set by hand in the shop are overwritten in the process.
More CAO-Faktura fields available for properties
Further CAO-Faktura fields unused so far (products_size, products_customsnumber [customs tariff number] and products_var_parent_artnum [article number of the parent product on variants]) can now be used for assigning custom properties, in the CAO-Faktura channel under "Transfer Plans" → "Products" tab → "Update" → "Properties".
Term "Vaterprodukt" replaced with "Elternprodukt" in the German interface
As part of an ongoing effort towards inclusive language, the term "Vaterprodukt" ("father product") has been replaced throughout the German interface and documentation with "Elternprodukt" ("parent product"), along with comparable terms such as "Vater Produkt Id" or "Vererbung vom Vaterprodukt". This affects, among other places, the product detail view and the corresponding assignments in the transfer plans of product-related tasks across nearly every channel. Nothing changes functionally, only the wording.
Anyone noticing non-inclusive or discriminatory terms elsewhere is welcome to let support know.
Update of .NET and packages
The underlying .NET platform and the packages in use have been updated to their latest versions, including the security updates that come with them.