In this article, you will find recommendations that may help you to improve your system performance
Please take a time and read our tips. Also, we suggest you keep regularly checking this article for further updates.
Always keep your M2E Pro updated
Unlike many other multi-channel providers, we release updates for our software quite regularly and it’s your responsibility to ensure your system is up to date. Regular updates contain fixes, new features, and system enhancements. Please, visit Release Notes/Policy to read more detailed information.
Some of our merchants signed up for hosted Magento+M2E Pro solution and get their systems updated regularly (free of charge) by the hosting partner.
Disable options/features that are not in use
Following the initial configuration please review your M2E Pro config and disable options, channels, and features that you do not intend to use.
- to check active channels:
go to System > Configuration > M2E Pro > Channels.
- to check geographic locations:
For eBay, go to eBay > Configuration > Marketplaces.
For Amazon, go to Amazon > Configuration > Marketplaces.
Please do not forget to review among others the following settings: 3rd Party Listing Import, Magento orders creation, Synchronization Policy, Selling Settings.
Use Conditional Revise Features
Starting from the version 6.3.x M2E Pro has “Conditional Revise” option implemented for both “Quantity Revise” and “Price Revise” in Synchronization Policy.
What is “Conditional Revise”?
The main purpose of the “Conditional Revise” is to limit a number of “Revise” actions performed. It allows improving M2E Pro Performance.
How “Conditional Revise for Qty” works?
Consider the following scenario: “Conditional Revise for QTY” is enabled, Product Quantity on hand is “105” and value for “Revise when Quantity is less or equal” is set to “5”. Given this setup, M2E Pro will not attempt to revise Product’s Quantity until QTY on hand in Magento falls below “6”. This will allow a system to avoid performing 100 “unnecessary” revisions. Clearly, this option is useful if a merchant carries large volumes for individual products.
Our recommendation is to Enable “Conditional Revise for Qty” and to set "Revise When Less or Equal" to some value. You can change this value at any time.
How “Conditional Revise for Price” works?
Sometimes merchants change prices in Magento but prefer these changes not to be reflected across marketplaces. For that very reason, M2E Pro has a “Conditional Revise for Price” functionality. The value to be set is a percentage of a maximum deviation between Magento Price (taken from Selling Policy settings) and a channel Product Price (eBay, Amazon).
Consider the following scenario: a Product Price in Magento is 10 $, “Conditional Revise for Price” is Enabled and "Revise When Deviation More than" value set to 10%. If the price in Magento changes (increase or decrease) by less than 10% (absolute value of 1$) then no price change across marketplaces occur. If the price changes (increase or decrease) by more than 10% (absolute value of 1$) then the price will be synchronized with marketplaces.
If “Conditional Revise for Price” is disabled then any price change in Magento will trigger a price update on the linked Channels. Bulk price revision may cause delay to all other data synchronization tasks including order import.
Do not Enable Track Direct Database Changes Option if in doubt
“Track Direct Database Changes” feature is normally used to detect changes that were made by direct SQL updates or by various import/export/update tools. However, enabling “Track Direct Database Changes” makes a huge negative impact on M2E Pro Performance. We ONLY recommend enabling “Track Direct Database Changes” if you are fully aware of the benefits this will bring to you given reduced performance.
Please do not use "Track Direct Database Changes” feature if you wish to interact with M2E Pro using some in-house/3rd party build tool/script. For better integration with M2E Pro, we have developed a Simple M2E Pro API and integrated Magmi Import Tool Plugin.
Disable Product Description Information
In most cases, there is no need to continuously update Product related information such as Title, Subtitle, Images or Product Description in real-time mode. For improved performance, M2E Pro recommends disabling these options under Synchronization Policy.
For eBay Integration:
- You can set partial Revise of Title, Subtitle, Description, Images to “no”;
- You can set Full Revise of Description to “no”.
For Amazon Integration:
- You can set Partial Revise of details and Images to "no";
- You can set Full Revise of Description Policy to “no”.
Disabling of above-mentioned options will make an extension to work faster, especially if your Magento Products Price and Quantity related data updates very often.
“Synchronize Data” option under “Relist Rules” in Synchronization Policy has a slightly different purpose. Enabling this option makes sense only in a few cases, disabling is strongly recommended and will increase the speed of M2E Pro Synchronization.
The main difference between “Enabled” and “Disabled” states:
- If it is “Disabled”, then an “Item” relist gets triggered by a Price and /or a Quantity update;
- If it is “Enabled”, then an “Item” relist gets triggered by a Price, Quantity or any of a Product Description Information update;
We recommend to ”Enable” this option only if you really (!) need M2E Pro excessive synchronization, which is in many cases very rare.
Note: for Amazon Integration only in very rare cases (i.e. “Description Policy” has been added to a large number of Products and urgent synchronization with Amazon is needed) we recommend “Enabling”
Details and Images updates under “Partial Revise”
Synchronize Data in Relist Rules” of “Synchronization Policy”
“Description Policy update” in “Full Revise” mode
But please be aware that due to technical restrictions of an Amazon API additional submission of product-related information cases issues with “Price” and “Quantity” Revisions.
In case you have “Enabled” any of above-mentioned options, please make sure that Product Description Information had already been sent to Amazon.
Correct usage of Product Details update options:
- Most of the time – “Disabled”;
- One-off update – “Enable” and then revert back to “Disabled”;
Duplication of the same Product in M2E Pro Listing
Some sellers maintain more than one duplicate of the same product (from Magento Catalog) in M2E Pro Listing and then list these duplicates on the same marketplace. This “bad practice” always results in multiple revisions for every copy of the same product which makes synchronization process very time-consuming.
Our recommendation is not to list duplicates of the same Magento Product.
Usage of M2E Pro Models to Update Magento Products
Advanced users can observe data changes triggered by M2E Pro by subscribing to a data change actions which are different to that of Magento Core Models.
Frequently Magento Products, Categories, Attributes, etc. are changed without the usage of Magento Core Standard Functionality (Magento Core Models) which leads to these changes being ignored by M2E Pro.
M2E Pro cannot identify changes that were made using:
- Direct SQL injections - changes of any data made via direct SQL requests;
- Changes made via side models of side modules;
- Changes made via Magento API (except the changes that trigger Magento events M2E Pro subscribed on);
- Any other means, that are not these of a Magento Core Functionality.
If a data in your Magento system gets updated by any of above-described methods, you will need to “notify” M2E Pro about such changes to make your extension work properly.
There are 2 different methods of alerting M2E Pro extension regarding changes:
- Object - uses all possibilities of M2E Pro (slower);
- Structural - only for tracking data changes in existing Magento Products (fast).
These models are available in the following path \app\code\community\Ess\M2ePro\Model\PublicServices\Product.
Detailed information about the usage of the above-mentioned models you can find here.
Plugin integration with Magmi Import Tool
Data changes actioned by other means than Magento Core Models can be identified by M2E Pro in a number of different ways. “Track Direct Database Changes” feature has already been discussed but very often sellers use Magmi Import Tool which makes Product changes in a form of SQL injections. If the latter is the case, then M2E Pro needs to be alerted in some appropriate way. For that, we have developed a Plugin for Magmi Import Tool. This plug-in notifies m2e pro extension about changes made from Magmi Import Tool.
You can find this plugin using the following path \app\code\community\Ess\M2ePro\Model\PublicServices\Magmi.
Detailed information about M2E Pro Plugin for Magmi Import Tool you can find here.
Maintain more than one M2E Pro Listing
You can create a number of M2E Pro Listings and add Products. There are several advantages of spreading Products across several M2E Pro Listings:
- you can maintain different listing settings;
- Products can be grouped accordingly depending on their price, quantity, listing conditions, categories, etc.
If you add all your Products to one M2E Pro listing, this will make an interface work slower.
Use ‘New Policy’ rather than ‘Custom Settings’ when possible (only for eBay Integration)
When you create your M2E Pro Listing, you can define custom values for Selling Settings, Payment and Shipping Settings, Synchronization Settings, etc.
On the other hand, it is much more convenient to define Policies which can be reused multiple times.