M2E Pro Version - 6.4.4

Added

Ability to install module via composer (composer.json file added)

Previously there was an ability to install M2E Pro module only via Magento Connect Manage or manually. Starting from the 6.4.4 version, the installation might be processed via composer. The according data is added to the pack.

Ability to install module via modman (modman file added)

Previously there was an ability to install M2E Pro module only via Magento Connect Manage or manually. Starting from the 6.4.4 version, the installation might be processed via modman either. The according data is added to the pack.

Fixes

Quantity could be calculated incorrectly in some special cases (high limited range of cases)

For a very limited number of cases, the quantity of the Item might be calculated incorrectly.

This problem is fixed and no related issues are observed in the version 6.4.4.

Improvements

Variation Options label can be renamed now without further errors from eBay Trading API

Previously if any Variation Option label of your Magento Product was changed, this Item cannot be properly updated on eBay because of the errors returned. These errors were caused by the restrictions of eBay system which do not allow to update all the data for the Items which have sales, etc.

The 6.4.4 version includes a mechanism which detects such changes and modifies the data which is sent to eBay to prevent further errors. This functionality passed an in-depth testing and the received results show that the issue is no longer persisting.

Let's look how it works using a particular example. You have a Variation Product in your Magento which consist of 2 Child Products.

This Product was listed to eBay with the same Variation Option labels.

The Variation Option label was changed in Magento.

The Item will be revised on eBay and the updated Option label will be displayed.

Preventing the eBay Trading API errors if Magento Child Product was unassigned from Parent

In previous M2E Pro versions for the case when you unassigned one of the Magento Child Products (which is already listed to eBay), the eBay system returned you an error related to the mismatch between Variations presented on eBay and the ones you sent.

For example, your Product has 2 variations - white and pink which are listed to eBay.

However, then the Pink variation was unassigned from the Magento Product.

And during the next Revise action running, the error used to arise.

But the current version contains a workaround which prevents these errors and allows the Item to be revised on eBay.

Preventing the eBay Trading API errors if Magento Child Product will be totally removed

In previous M2E Pro versions for the case when you completely remove one of the Magento Child Products (which is already listed to eBay), the eBay system returned you an error related to the mismatch between Variations presented on eBay and the ones you sent.

For example, your Product has 2 variations - white and pink which are listed to eBay.

However, then the Pink variation was removed from the Magento Product.

And during the next Revise action running, the error used to arise.

But the current version contains a workaround which prevents these errors and allows the Item to be revised on eBay.

Price will be sent to the eBay each time during Relist action (together with QTY and Variations Data)

Previously for the case when the Synchronize data option was enabled, the Price value was not sent to eBay during the Automatic Relisting. However, it might cause further issues.

So, to prevent any possible issues related to it, the improvement was implemented into the latest M2E Pro version and the Price value will be send to eBay along with Quantity and Variations data during the Item Relisting.

Fixes

Items duplicates if List Action was run manually for "Listed (Hidden)" Item

Under some circumstances when the Item was placed in M2E Pro Listing with the Listed (Hidden) status, the ability to run List action for it manually was available. It cause the further duplicating of this Item on eBay and the issues related to it.

This problem is fixed and no related issues are observed in the version 6.4.4.

Orders Synchronization could not work correctly sometimes if there are a lot of changes on eBay side

In some cases the Orders synchronization worked incorrectly if the the number of changes on eBay was high.

This problem is fixed and no related issues are observed in the version 6.4.4.

Wrong QTY could be set for Item after Relist action for items with "Listed (Hidden)" status

Sometimes when the Relist action was executed for the Item which currently has a Listed (Hidden) status the improper Quantity value might be set.

However, the necessary fix is implemented into the current version and no related issues are observed now.

Multiple fixes of different functionalities

Excluded locations were not removed from eBay when they were removed from Shipping Policy before

Under certain circumstances, for the case when you edited the Shipping Policy in order to remove the Excluded Locations, the according values were not removed from eBay.

This problem is fixed and no related issues are observed in the version 6.4.4.

Error "The Product was Listed as a Simple Product as it has limitation for Multi-Variation Items" during list item even if requirements are met

For some cases when you attempt to list the Variational Magento Product to eBay, the error "The Product was Listed as a Simple Product as it has limitation for Multi-Variation Items" arose even if the Item met all the requirements.

This issue is fixed in the current version and no related issues are observed now.

Added

Ability to create new ASIN/ISBN in Canada Marketplace using Description Policy

The new M2E Pro version contains an ability to create new ASIN/ISBN for Amazon Canada Marketplace. Thus, the ability to create Description Policy was added either.

The Description Policy can either be used in order to update the product information on Amazon.

The detailed information about it you can find here.

Fixes

Synchronization was broken due to error "Call to a member function getOptions() on a non-object"

For the case when there were some changes made to Child Products, the error "Call to a member function getOptions() on a non-object" arose. It used to prevent the Items from being properly updated on Amazon.

This problem is fixed and no related issues are observed in the version 6.4.4.

Product was not revised if their Policy settings were changed and it were in "Revise in progress" state

If there was a change made to the Policy settings applied to the Item which was currently processing and marked with the Revise in progress, this Policy change was skipped.

The needed fix is implemented into the current version and no related issues are observed now.

Full revise by Description Policy did not work, if change was performed on Definition tab

Under certain circumstances, the change made to the data placed on the Definition tab of the Description Policy was not properly reflected to Amazon and the Full Revise was not executed.

This problem is fixed and no related issues are observed in the version 6.4.4.

Fixes

Product was not revised if their Policy settings were changed and it were in "Revise in progress" state

If there was a change made to the Policy settings applied to the Item which was currently processing and marked with the Revise in progress, this Policy change was skipped.

The needed fix is implemented into the current version and no related issues are observed now.