Page Comparison

Added

Catching changes of Magento Product Attributes

In current version M2E Pro extension can catch changes that were made using Update Attributes option in Catalog>Manage Products, that was not available earlier.

Thus such Updates of Magento Products cause the same actions (List/Revise/Relist/Stop) as common products changes (Catalog>Manage Products>[selected product]>[change]>Save).

Price Deviation feature of Synchronization Policy

Conditional Revise for Price changes was added in new version of M2E Pro.

When this option is enabled, there is an ability to specify percent value of maximum possible Deviation between Magento Price (Selling Format Policy settings) and Item Price on the Channel, that can be ignored.

So how it works? If Magento Price is changed insignificantly (for several cents), the Revise will be run. It is absolutely normal, expected situation. However, when Price changes for all Magento Products (for example, due to currency rate changes), M2E Pro has to Revise all Items. It is resource and time-consuming, but usually there is no practical sense to update minimum Price changes. So if Conditional Revise option will be enabled, minimum changes will be ignored and M2E Pro will not spend a time to update them (e.g. from 23.47$ to 23.48$).

If Conditional Revise option is disabled, M2E Pro will update Price (that most likely has no practical effect). While Price Revise will be running for that Product, all changes (e.g. from 1$ to 60$ etc.) for other Products will be placed in queue and will wait until Price will not be updated. It can also increase the passivity of Orders Import up to 12 hours.

If this option is enabled and "Revise When Deviation More than" set to 3%, M2E Pro will ignore all changed in Magento Price that are lower than maximum Deviation value. So Price will not be Revised until it’s change will not be more or equal to Deviation value.

For example, Price is changed from 23.47$ to 23.48$. As Deviation Value (0.7$) is more than Price change (0.01$), Revise will not be run.
If Price is changed to 25$, Revise will be run, as Deviation Value (0.7$) is less than Price change (1.13$).
After Revise, for further Deviation count new Magento Price (25$) will be taken.

You can always change "Revise When Deviation More than" value according to your needs. The more value = less unusefull calls + more Performance of M2E Pro.

So M2E Pro does not recommend to disable this option.

Note: For Sellers who synchronize Magento Inventory with Suppliers Inventory by any automatic software this option is critically required, as Supplier's Price Values are changed very often.

Programmatic Possibilities to work with Extension

In new version of M2E Pro several PHP Classes were added. Using these Classes it is possible to notify Extension about Magento Products changes in different ways. This option is useful in case you are using a principle of direct SQL requests to update your Magento Products or any similar principle.

This programmatic components you can find following the next way \app\code\community\Ess\M2ePro\Model\PublicServices\Product. The example of its possible usage is placed in a header of each code file.

Also there is no need to enable Track Direct Database Changes option if you are using any of these PHP Classes.

More detailed information you can find here.

Plugin for Magmi Import Tool

Starting from current version it is possible to use a M2E Pro Plugin for a popular Import Tool - Magmi.

You can find it in the directory following the way \app\code\community\Ess\M2ePro\Model\PublicServices\Magmi.

After installation of this plugin to your copy of Magmi, M2E Pro will be able to receive a notifications about Magento Products changes during an import of your Inventory to Magento via Magmi. It will save a performance and decrease a passivity of M2E Pro actions.

Also there is no need to enable Track Direct Database Changes option if you are using a Magmi Import Tool.

More detailed information you can find here.