Bienvenue dans l’espace client magnalister

Listings that Amazon rejected after an upload, and listings deleted through magnalister, were not removed from the magnalister inventory right away; they stayed visible until the next inventory report from Amazon was imported. They are now removed as soon as Amazon confirms the rejection or the deletion. If the product was uploaded again in the meantime, its new inventory entry is kept.

After a product upload, magnalister checks on Amazon whether the listing has been created. When several Amazon accounts were checked in the same run, this check only worked for the first account, so products of other sellers stayed in the pending items list, in some cases for weeks, although they were already live on Amazon. The check now uses the correct Amazon account for every seller. Products that Amazon still does not know 48 hours after it accepted the upload no longer wait indefinitely: they leave the list with Amazon's error "SKU not found", so they can be corrected and uploaded again. Errors of a previous upload are no longer shown for a new upload of the same product.

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.

In "Create new products" and "Product Matching", some products showed the "i" lock ("This product was prepared in the tab …") although they were never prepared. "Remove preparation" did not help. This happened when a variant of another, prepared product had the same number as the product's own ID. The lock now uses magnalister's own product ID, so only products that are really prepared are locked.

Our eBay variation processing could get confused when 2 dimensions use the same value (like "none" or "ohne"), This is fixed.

The "Absolute Enable Right Click & Copy" extension in Firefox 158 has made our dropdowns disfunctional. Now it works also with this extension.

Since 22 September 2026, the price and stock synchronization for Kaufland sent the minimum transport time as handling time, so a handling time set on Kaufland (e.g. 17 days) was replaced by 1 day. The synchronization now only sends a handling time when the plugin transmits one; otherwise Kaufland keeps its current value. Offers already affected have to be corrected once by uploading the products again or by setting the handling time on Kaufland.

Some buttons, like the "Expert Settings" button on the global configuration page in Shopify, could lead to endless spinning. This is fixed.

It could happen that, when a preparation of an item with many variations got error messages from the API, the plugin returned to the overview page and some of the variations where shown as prepared correctly, which was false. This is fixed.

Don't show "Request creation failed" when contact phone, e-mail or postal code are invalid. Show a real error message.

In the upload view, the "Filter (prepared on)" could show the time of a product preparation shifted by one or more hours, because the time sent by the browser was interpreted again in the time zone of the server. Preparation times are now stored in UTC and shown in the time zone of your browser, also in automatic and manual matching and when many products are prepared at once. Preparations saved before this update keep the time shown so far; preparing them again stores the corrected time.

During the eBay inventory synchronisation, items that carry only an old (strike-through) price on eBay raised the PHP warning "Undefined array key ManufacturersPrice", which could appear as an error message in the shop. The old price is now read correctly and the warning no longer occurs.

In the eBay product preparation, you can add several custom attributes under "Custom attributes". After clicking "Save data", only the first new one was kept. The others were gone after reopening the preparation and were not sent to eBay. Now every custom attribute added before saving is stored and uploaded to eBay. Custom attributes with several values are sent to eBay as one text, e.g. "a, b".

Temu returned the attributes of a category and their values in English, even when the Temu Seller Center shows them in German or French. Values were therefore hard to find in the attribute matching: leather materials, for example, are listed as "Top Layer Cowhide" rather than "Leder". The category attributes are now requested from Temu in the language of the plugin interface (currently German and French; other languages stay English), so names and values match the Seller Center. Attribute matchings saved with the English values remain valid and are uploaded as before.

Large amounts of orders could lead to memory exhaustion. Configuration pages could sometimes break with PHP 8. Both fixed.

For shops with very large catalogs, the product import and the product update now load the data of many products and variants at once instead of several requests per product and variant, which makes them many times faster. A new separate cron keeps price, stock and the active state of all products and variants up to date within minutes, also while the product update is still busy after a re-import of the whole catalog. Products that the Shopware search index still lists after they were deleted no longer stop the import, the cleanup of deleted products and property values no longer slows down the database, and the translations of property values are loaded per page instead of one by one. In addition, product images are saved without database lock errors, and the CloudShop Log shows the progress of the new price and stock cron.

The "Cancel prepare" button in the preparation form only removed the preparation of the first five selected products. For a product with more than five variants the other variants stayed prepared, the form showed their category again after reloading, and the automatic save of the attribute matching could store the removed variants again, so the preparation seemed unchanged. The button now removes the preparation of the whole selection.

When a product was opened in the Amazon preparation under "Create new products" and the form was left without saving, the automatic save of the attribute matching stored it as a matched product, so it no longer showed up as a new product preparation. The automatic save now keeps these products as "Create new products" preparations. Products that were already affected can be reset by cancelling their preparation.

The stock synchronization now transmits the changed stock in the field the Temu connection reads, so stock changes of the shop are applied to the Temu inventory.

The country of origin is now chosen from the list of countries Temu accepts, and shop values can be matched to it. For countries where Temu also requires the province of origin, such as Mainland China, a "Province of origin" field is requested and checked before the upload. Values that Temu does not know are reported with instructions instead of being rejected later by Temu. The GPSR responsible person and manufacturer are now sent in the certification information of the product. Temu silently ignored them when they were sent the previous way.

The stock synchronization of the Modified Shop and xt:Commerce plugins sent the new stock in a format the Temu connection did not read, so stock changes of the shop were not transmitted to Temu. The stock, including relative increases and decreases, is now accepted and applied to the Temu inventory. Items that carry neither a stock nor a price are no longer counted as updated but are written to the error log. Variant products from these plugins also keep the shipping template selected in the product preparation when they are merged into one Temu product during the upload.

Some countries of origin, such as Mainland China, require a province of origin at Temu. In the product preparation, the "Province of origin" field now appears below "Country of Origin" and only for the country it belongs to, so it can be filled in before the upload.

Some countries of origin, such as Mainland China, require a province of origin at Temu. In the product preparation, the "Province of origin" field now appears below "Country of Origin" and only for the country it belongs to, so it can be filled in before the upload.

The stock synchronization now transmits the changed stock in the field the Temu connection reads, so stock changes of the shop are applied to the Temu inventory. For variant products, the shipping template selected in the product preparation is now also sent with the product, so it is no longer lost when the variants are merged into one Temu product.

Some countries of origin, such as Mainland China, require a province of origin at Temu. In the product preparation, the "Province of origin" field now appears below "Country of Origin" and only for the country it belongs to, so it can be filled in before the upload.

The marketplace price can now be taken from a Shopify metafield instead of the Shopify price. To use it, enable the expert option "Price from metafield" in the global configuration under "Product attributes". The price settings of every marketplace then show a "Price source" with two selections: a product metafield for single products and a variant metafield for products with variants. Metafields of type decimal, single line text (e.g. 19.90 or 19,90) and money can be selected. The metafield value is treated like the Shopify price (gross); the surcharge and price rounding of the marketplace are applied on top. For a product with variants, the main product takes the price of its first variant. If the metafield of an item is empty or not a positive number, the Shopify price is used for that item. Money metafields are not converted to another currency. The option is off by default, so existing prices do not change.

In the order status sync configuration, each row of the carrier matching (and of the Amazon shipping method matching) now has a match mode: "Exact match" (as before), "Starts with", "Contains" and "Any (fallback)". With "Starts with" and "Contains", one row covers all shop shipping methods whose name fits, e.g. every method containing "DHL". The fallback row is used for all orders no other row matches, so shipping confirmations are no longer sent without a carrier. Existing rows keep working as exact matches. If a shipping confirmation cannot get a carrier or shipping method because nothing is configured or no row matches, this is now listed in the marketplace's error log together with the marketplace order number, and shown in the sync output. Affected: Amazon, eBay, Kaufland, METRO, Cdiscount, PriceMinister, Etsy, OTTO, OBI, Temu.

Stock changes from your shop were in some cases not transmitted to Etsy, although the inventory sync detected them on every run. This happened when the stock on Etsy had changed in the meantime (for example through a sale on Etsy) while the quantity to be transmitted stayed the same, e.g. because a quantity limit is set. These changes are now transmitted. Draft listings on Etsy are no longer published by the inventory sync; only their stock is updated.

When updating variation items on eBay, having other variations with invalid sizes (no longer in the shop), from now on, we remove the invalid variations, so that the update works.

For some items, it happened that an item preparation displayed success but didn't really check the data. This is fixed.

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.