Bienvenue dans l’espace client magnalister

On Shopware 5, product images are now transferred in the same order as in the shop, and each variant gets its own images first. Before, images that share the same position in the shop (for example after an image import) could arrive in random order, so several variants could start with the same image. Images without a variant assignment follow after the variant's own images, and the product's main image comes first in the main gallery. Products that are already prepared keep their saved image selection: remove the preparation and prepare them again.

The "Replace inventory completely" button on the upload page has been removed for all marketplaces. It first deleted all listings on the marketplace and then uploaded only the selected products, so a single click could take an entire inventory offline. Uploads now only add or update the selected products; all other listings stay on the marketplace. In the inventory of OTTO, OBI and Temu, the stock column now has a short name like on the other marketplaces, e.g. "Shop Stock / OTTO Market". The French texts of this column were previously shown in German and are now in French.

Sellers who have more than one return warehouse or return carrier in the OTTO partner portal can now choose in the Orders configuration which one magnalister sends to OTTO when confirming a shipment. The return warehouse is set globally and can be overridden for each ship-from location under "Confirm Shipping and 'From' Address". If there is more than one return warehouse and none is selected, the configuration shows a warning, because OTTO rejects shipment confirmations without a return warehouse in that case. Sellers with a single return warehouse do not need to change anything; OTTO uses its default return warehouse.

With many marketplace tabs, the magnalister page could become wider than the window: a horizontal scrollbar appeared, and the tabs on the right (Global Configuration, Statistics, Help) and the icons in the header were cut off. In addition, opening a marketplace scrolled the page down by itself, in Shopware 6 also the administration around magnalister. The tab bar now always fits the window and the page stays where it is. The scroll arrows of the tab bar were also polished: marketplace logos no longer show through next to them, and the grey line beneath the tabs runs straight through.

OTTO reports the result of a product upload with a link to the uploaded SKU. This link was not evaluated correctly, so successfully created products were not activated in magnalister and remained in "creating" status. A renewed upload then reset them to failed with the error "Product is stuck in creating status with no pending check". Upload results are now assigned to the correct product, including SKUs that contain a slash.

In Shopware Cloud, the product import into magnalister stopped after 50,000 products, so shops with larger catalogs were missing products, and only one import process worked at a time. Product IDs are now collected step by step without a limit, and several processes import the products in parallel, which makes the import of large catalogs considerably faster. The regular product update now also applies changes that were made only to variants, e.g. the stock of a single variant. The progress of the product import can be followed under Tools > CloudShop Log.

The shipping template selected in the product preparation now takes precedence over the default template from the Temu configuration. Previously, the configured default could overwrite the product's selection during upload. Products without a template selected in the preparation continue to use the configured default.

The Temu configuration now correctly displays the connected account ID, market and authorization expiry date, including expiry warnings. It also shows whether the "Base Price Management" permission has been granted and explains how to enable it when price synchronization is blocked. A new "Disconnect account" button lets you reconnect with updated permissions or use another Temu account. Failed authorizations show the reason returned by Temu, and the configuration reloads when the authorization window closes.

The inventory deletion confirmation now explains Temu's behavior: selecting only some variants takes those variants off sale; the product is deleted only when all of its variants are selected. The inventory note column also displays the messages returned for the product. Images selected in the preparation are now sent as product detail images. Variants with their own images in the shop use those images during upload; other variants use the selected product images.

The Temu configuration now correctly displays the connected account ID, market and authorization expiry date, including expiry warnings. It also shows whether the "Base Price Management" permission has been granted and explains how to enable it when price synchronization is blocked. A new "Disconnect account" button lets you reconnect with updated permissions or use another Temu account. Failed authorizations show the reason returned by Temu, and the configuration reloads when the authorization window closes.

Shop attributes assigned to standalone products now resolve correctly in Temu attribute matching. Variant attributes are sent for each variant, while product-level attributes use a shared variant value only when it applies to every variant. Preparation errors also name matched variation attributes that have no usable value. The new "Client-Store" setting selects which store supplies product names and descriptions for the product list and upload and receives imported orders. This prevents products from appearing repeatedly in multi-store installations. Attributes of standalone products are labeled "Custom Properties" instead of "Variations".

When connecting a Temu account, magnalister now checks that the authorized Temu market matches the market selected in the configuration. If Temu reports that the required "Base Price Management" permission is missing, the connection is also refused. The authorization page explains the reason and how to connect again with the correct market and permission. Authorization details now include the price permission and the authorized market. Accounts can be disconnected so that you can authorize again or connect another account. The authorization result pages show clear, localized success and error messages.

Uploading a product that is already listed on Temu now updates its title, description, images and matched attributes. New variants are added to the existing Temu product instead of creating a separate listing. Changes that Temu does not allow, such as changing the category or the attributes of an existing variant, are reported with instructions. Updates blocked by an ongoing Temu review are retried automatically. If the review lock lasts longer than 24 hours, the error log asks you to upload the product again once the review has finished. Variants omitted from a normal re-upload remain on Temu.

Some Temu attributes depend on the value selected for another attribute. When the same dependent attribute applied to several parent values, magnalister previously kept only the last dependency. The dependent attribute could therefore be missing from the upload for other valid selections, and its required value was not always checked. All applicable parent values are now considered during preparation and upload, including parents with multiple selected values.

The "Access Data" tab now shows whether Temu has granted magnalister the "Base Price Management" permission. If it is missing, the tab and the price settings explain why price synchronization cannot work and how to grant the permission and connect again. Stock synchronization is not affected by this missing permission. A new "Disconnect account" button lets you reconnect with updated permissions or use another Temu account. Refused authorizations now show their reason, including a different Temu market. The configuration reloads when the authorization window closes.

The Amazon logo in the shop order overview and in the magnalister Amazon order list now shows the shipping service level of the order (Priority, Expedited, Next-Day, Same-Day or Second-Day) for regular, Prime and Business orders. Previously only Prime orders with Next-Day, Same-Day or Second-Day had their own logo. The logo now stays the same when the order is shipped or cancelled; shipped Prime Next-Day, Same-Day and Second-Day orders previously showed only the plain Amazon logo. Orders that are already imported keep their current logo until they are updated by the order import.

If the attribute matching of a product with more than 5 variants was changed and "Save" was clicked within a few seconds, the change was only saved for the first 5 variants. The other variants kept their previous matching and were uploaded without the new values. eBay then rejected the listing, e.g. because a name/value combination in the variation specifics was duplicated. The matching is now saved for all variants. Products that are already affected are corrected by saving their preparation once more.

For Amazon attributes that accept several values (e.g. "Material"), only the first value of a Shopware property with several values was sent. All values of the property are now matched and sent to Amazon as separate values. If one of the values has no matching Amazon value, the attribute is not sent, so Amazon never receives an incomplete list. Attributes that accept only one value are not affected.

From 1 November 2026, METRO restricts shipment confirmations with custom carriers. The order status synchronisation of the METRO configuration now has a "Carrier" setting with the carriers METRO accepts. When a shipment is confirmed, the carrier from the shop is checked against this list (name or ID, case does not matter); if it does not match, the selected carrier is used. Please select a carrier in the METRO configuration.

From 1 November 2026, METRO restricts shipment confirmations with custom carriers. The order status synchronisation of the METRO configuration now has a "Carrier" setting with the carriers METRO accepts. When a shipment is confirmed, the carrier from the shop is checked against this list (name or ID, case does not matter); if it does not match, the selected carrier is used. Please select a carrier in the METRO configuration. If neither matches, the shipment is confirmed without a carrier.

When a shipment is confirmed, the carrier is matched to METRO's carrier list. If there is no exact match, name and ID are now also compared regardless of case (e.g. "dhl" matches "DHL"), so these carriers are no longer sent as a custom carrier. This applies to all plugin versions.

From 1 November 2026, METRO restricts shipment confirmations with custom carriers. If the carrier option is set to the shop shipping method, free text or a shop free text field, the value must match the name or ID of a METRO carrier exactly (e.g. "DHL"); other values are sent as a custom carrier. The help text now explains this, and the METRO configuration shows a warning while one of these options is selected. We recommend selecting a METRO carrier directly or using the carrier matching.

When you changed the attribute matching in the eBay product preparation and then clicked "Save", the first save could overwrite your changes with the values that were loaded when the page opened. eBay then still received the previous item specifics. Your changes are now kept with the first save. The same could happen in the Amazon and Temu product preparation after the category or the variation theme had been changed on the page. Products prepared while the error was present may still carry the old values: please check their attribute matching and save the preparation again. Products that are already listed need to be uploaded again to send the corrected item specifics.

In the inventory and under "Deleted", you can now choose at the top how many items are shown per page: 50, 100, 200 or 500, as in the product preparation. The selection is kept per marketplace and tab. The search field has moved from the action bar at the bottom to the same row at the top. On Amazon, the B2B filter is now in this row as well. "Deleted" now has a search field on all marketplaces except Amazon. On Etsy, Kaufland, Ricardo, Cdiscount, Check24, idealo, Google Shopping, MercadoLivre and PriceMinister, deleted items could not be searched before. They can now be found by their SKU.

Amazon treats the battery cell composition and "Other battery cell composition than listed" as a mutually exclusive pair: as soon as a listed cell composition is chosen, the second field must stay empty. After Amazon reported missing battery data, the product preparation marked both fields as mandatory, so the second one could not be left empty and Amazon rejected the product with error 90248 - even when the field was filled with "0". Fields that Amazon's category data excludes depending on another field are no longer marked as mandatory. An existing match for "Other battery cell composition than listed" is still sent and has to be removed once.

Six fixes in the Temu product preparation and upload: 1. Weight and package dimensions matched in the product preparation are now saved to the product itself. Previously they were saved to the shared template, so the product was rejected for missing weight and dimensions until it was saved a second time. 2. A bulk preparation now writes these attributes to every selected product, not only to the first one. 3. The buttons "Undo Prepare Items", "Delete" and "Reset" in the Temu product lists work again. They previously did nothing, without an error message. 4. Products prepared in bulk now take their images from the shop automatically, so the upload is no longer rejected with "Temu requires at least 1 image per SKU". An image selection made in the preparation still takes precedence. 5. The stock setting from the Temu configuration, including the maximum quantity, is now also applied to variants. Previously variants were uploaded with the full shop stock, which could lead to overselling. 6. The SKU of a master product now follows the key type chosen in the configuration (product ID or article number), so the stock and price synchronisation no longer skips these products.

We can upload only 1 tracking code for an order. In case when the field contains multiple codes, separated by commas, semicolons etc., we use only the first one.

For some Amazon Business orders, Amazon reports more than one tax registration for the buyer, for example a French company registration number (SIREN) together with the VAT ID. In that case the VAT ID was not imported and the order was created in the shop without it. The VAT ID is now taken over correctly. This applies to newly imported orders; no plugin update is required.

With the option "B2B-Order with Tax ID" active, a business order with a tax ID delivered to another EU country is created tax-free (reverse charge). After such an order, all further orders of the same import run were created with 0 % VAT as well, including regular consumer orders and domestic orders. Each order is now checked on its own again. Orders that were already imported are not corrected automatically. Please check the Amazon orders imported while the option was active.

Shopware 6 stores the manufacturer guarantee in months, while eBay, Kaufland and Etsy expect whole years. The new shop field "Manufacturer guarantee in years (rounded down)" converts the value: 36 and 42 months become 3 years, 60 months become 5 years, and values below 3 years or above 99 years stay empty. A variant without its own guarantee takes the value of its main product. The field can be selected in the attribute matching and wherever product fields are offered, for example in the Kaufland setting "Herstellergarantie (Jahre)", and it is only offered in Shopware versions that have the guarantee fields. The update also contains three smaller fixes: selection fields in the configuration and preparation forms are displayed correctly again after the update of the form libraries; the help text of the Kaufland field "Herstellergarantie (Jahre)" now explains that every whole number from 1 to 99 is sent and read as years; and in Shopware 5 the browser loads new scripts and stylesheets right after a plugin update instead of old copies from its cache.

Since build 13418 (24 September 2026), the drop-down for adding an optional attribute was missing in the product preparation and the attribute matching of categories with more than five optional attributes, so these attributes could not be matched, for example the WEEE registration number at OTTO. This affected the marketplaces with the classic attribute matching, such as OTTO, Kaufland, METRO, Cdiscount, Hood, Check24, OBI and Etsy; Amazon, eBay and Temu were not affected. The drop-down is shown again. Optional attributes that had already been matched were kept. If a marketplace rejected products because an optional attribute was missing, please match the attribute in the preparation and upload the products again.

If the language selected under "Item Preparation" in a marketplace configuration no longer existed in Shopware, for example because it had been deleted or the shop was moved to a new installation, the "Order Import" tab and, for marketplaces with invoice upload, the "Invoices" tab stopped with an error. magnalister now uses the Shopware system language there, and both tabs open again. Please select the correct language under "Item Preparation" once and save it.

Since Shopware 6.7, an app needs an additional permission to start Flow Builder flows. The magnalister app did not request it, so Shopware rejected the trigger "magnalister.order.imported" after every order import, and flows bound to it, for example to send an e-mail, never ran. The app requests this permission from version 3.4.3 on. If Shopware asks you to confirm the new permission when the app is updated, please accept it.

The manufacturer guarantee in whole years that the plugin sends with the product upload is now transferred to Kaufland on the offer: new offers receive it when they are created, existing offers with the next upload if the value is new or has changed. The price and stock synchronisation does not touch it, so a value entered in the Kaufland Seller Portal stays unless a different value is uploaded. Values that are not whole years from 1 to 99 are not transferred and are listed per item in the error log.

New field "Herstellergarantie (Jahre)" (manufacturer guarantee in years) in the Kaufland configuration under "Artikelvorbereitung". Choose the shop attribute that holds the manufacturer's guarantee in whole years, or enter one value for all items. It is sent with the next product upload, for new and for matched products, but not with the price and stock synchronisation. Kaufland shows its guarantee label only for a free manufacturer guarantee on the whole product of more than two years, and only if manufacturer and manufacturer part number are also available. Only whole numbers from 1 to 99 are sent, and they are read as years, so a value kept in months (for example 36) would arrive as 36 years. Anything else, such as "5 Jahre", decimals, 0 or numbers above 99, is not sent and is listed in the error log. Clearing the field does not remove a value Kaufland already has; that is only possible in the Kaufland Seller Portal.

New field "Herstellergarantie (Jahre)" (manufacturer guarantee in years) in the Kaufland configuration under "Artikelvorbereitung". Choose the shop attribute that holds the manufacturer's guarantee in whole years, or enter one value for all items. It is sent with the next product upload, for new and for matched products, but not with the price and stock synchronisation. Kaufland shows its guarantee label only for a free manufacturer guarantee on the whole product of more than two years, and only if manufacturer and manufacturer part number are also available. Only whole numbers from 1 to 99 are sent, and they are read as years, so a value kept in months (for example 36) would arrive as 36 years. Anything else, such as "5 Jahre", decimals, 0 or numbers above 99, is not sent and is listed in the error log. Clearing the field does not remove a value Kaufland already has; that is only possible in the Kaufland Seller Portal.

New field "Herstellergarantie (Jahre)" (manufacturer guarantee in years) in the Kaufland configuration under "Artikelvorbereitung". Choose the shop attribute that holds the manufacturer's guarantee in whole years, or enter one value for all items. It is sent with the next product upload, for new and for matched products, but not with the price and stock synchronisation. Kaufland shows its guarantee label only for a free manufacturer guarantee on the whole product of more than two years, and only if manufacturer and manufacturer part number are also available. Only whole numbers from 1 to 99 are sent, and they are read as years, so a value kept in months (for example 36) would arrive as 36 years. Anything else, such as "5 Jahre", decimals, 0 or numbers above 99, is not sent and is listed in the error log. Clearing the field does not remove a value Kaufland already has; that is only possible in the Kaufland Seller Portal.

We can upload only 1 tracking code for an order. In case when the field contains multiple codes, separated by commas, semicolons etc., we use only the first one.

If the option "Use the value stored in the web shop" was switched on for an attribute such as "Size", and eBay later turned this attribute into a pure selection list, the option was no longer shown in the preparation but was still applied: the values you had matched in the table were ignored and the shop values were uploaded instead. A matching table you have filled in now always takes precedence. Attributes whose table is empty keep using the shop values as before. The same applies to all other marketplaces. Please note: eBay requires a different combination of values for every variation. If several shop values are matched to the same eBay value (for example the sizes 26/32 and 26/34 both to 26), eBay rejects the listing.

The identifier in the EAN field is now sent to Temu with its actual type. In book categories an ISBN is sent as ISBN, so Temu no longer rejects books for a missing ISBN. Values that are not a valid EAN, UPC, ISBN or GTIN (for example an Amazon ASIN) are no longer sent; the product is still uploaded and the error log shows a warning. For books, the preparation now checks that every product has a valid ISBN and only one variant, as Temu requires. In the preparation you will find two new optional attributes, "Barcode" and "Barcode type". Match "Barcode" to any shop attribute, for example a separate ISBN field, to send that value instead of the EAN field. The new attributes appear within 24 hours.

Temu requires at least one variation (for example colour or size) for every product, even in categories in which all variation attributes are optional. Until now, a product without a variation passed the check in magnalister and was only rejected by Temu after the upload, without any reason being shown. The preparation now reports the missing variation right away.

The plugin now tells magnalister whether your price synchronisation is switched on or off. Only with this information can we fetch the missing value from Kaufland instead of using our own. Please update your plugin, and then save the Kaufland configuration, if you synchronise only the stock or only the prices.

The plugin now tells magnalister whether your price synchronisation is switched on or off. Only with this information can we fetch the missing value from Kaufland instead of using our own. Please update your plugin, and then save the Kaufland configuration, if you synchronise only the stock or only the prices.

The plugin now tells magnalister whether your price synchronisation is switched on or off. Only with this information can we fetch the missing value from Kaufland instead of using our own. Please update your plugin, and then save the Kaufland configuration, if you synchronise only the stock or only the prices.

Until now, if you had switched on only the stock synchronisation but not the price synchronisation (or the other way round), we filled in the missing value from our own database. This could overwrite a price or stock level that you had changed on Kaufland yourself. From now on we fetch the current value from Kaufland right before synchronising, so your changes stay intact.

The labels need to be uploaded in item preparation already (otherwise we get an error).