Maybe you could think about your expectations: > The product are imported with the basic fields : name, sku, price, taxes What more do you need? Marketing fields do not concern the ERP. > The product data are sync only from Magento to Odoo The reverse proved to be a failure for many reasons in the previous implementation (due to the Magento API, to the fact that it implies to neary develop the entire Magento product datamodel in Odoo, ...). This particular points represents months or years or work if you want to fully support all types of bundles, options, ... > The stocks are NOT imported > The stock changes are NOT imported from Magento to Odoo, but only from Odoo to Magento Of course! the stock operations are done on Odoo so there is no point to import them from Magento. If you think about an initial sync, nobody needed it so far that's why it does not exist (because usually people do an initial inventory). But we would be glad if you add it. > The main images for the simple product are imported Yes, Odoo supports 1 image per product and we don't think you need more of them on an ERP. > Also all for with cron job, there is no instant synchronisation... Imports from Magento work with cron jobs, because we have to poll Magento for new records. Exports to Magento (or whatever is triggered on the Odoo side) are not using cron jobs, but the Connector's Queue Job which execute the job as soon as possible (understand: immediately when no other jobs is already running). It is better than an instant synchronisation for many reasons. I think you really really don't realize what amount of work and so the price of what you expect. But it is open source, you can contribute and propose the things you want. Finally, the connector is made extensible so you can add your own new fields or synchonizations.

At least I expected that this was clearly define in the doc... There is even no way to import EAN, we have to develop it by ourself... Importing product from Magento without importing the stock, do you really think nobody need it ? The initial inventory are on Magento, because the products are here. Maybe I mistake, but I debuged the process to sync the stock to Magento: it checks the stock changes on all the products, each time it is executed, so you cannot execute it "as soon as possible", or you like to hurt your server. Having a Magento with out of stock products availables to purchase is the hell.

@Guewen,

Thank you for your hard work on this module, it's proving to be very useful for various projects i'm working on at the moment. I've successfully setup the connector with magentoerpconnect_pricing from your personal branch (waiting to be merged with OCA).

I was wondering if this connector (particularly your branch of magentoerpconnect-pricing in it's current state here - https://github.com/guewen/connector-magento/tree/8.0-magentoerpconnect_pricing-migr) is designed to push pricing to Magento from Odoo after changes in Odoo pricelists.

I'm in the process of testing out the connector for an upcoming e-commerce project and need the connector to pull the main image (and if possible, image gallery using product_multi_image by Pedro B.), as well as push pricing and inventory changes to Magento from Odoo.

Is your module (in it's current state awaiting merge with OCA) setup to handle main image sync (including syncing changes when main image in magento is changed), and pricing (by pricelist) changes between Odoo and Magento?

I've read the documentation, i'm just interested specifically in the two modules waiting to be merged and whether the pricelist update function specifically has been updated according to the roadmap.

Yes, Work has already begun. Development is set to be complete in a few weeks. Once it is complete, the source will be made available for free.

hello, any update on the status of the connector?

Hello, Work still in progress. This particular project involves much more than just the Magento connector. It is a complete management solution for Magento. The connector portion is finished, but still undergoing testing.

This is a critical feature, in camptocamp connector currently all sales orders imported apply the sales tax by default. It would be quite helpful to set a conditional ruling and only apply Sales Tax to orders from a certain state. Similar to how Magneto, eBay and Amazon settings are. If there is a module this is available please advise.

Hi, This work is already completed. We added an addition to the sales order info API to return the tax name and details. If the tax does not exist in Odoo at the time of order import, it will be created exactly as it is on Magento. ;)

Hi, Some of the features you mentioned have already been developed. Multiple customer addresses, with a light built in de-duplication feature, Discounts & Taxes, Shipping methods and payment methods. The payment method on sales order is another module we developed because this functionality was missing. You can map any payment method in magento to a journal in Odoo. If the payment method is not found, it will create it and you only have to assign a journal for it to work when you go to do payment. The inventory/stock synchronization is still being developed. We have written a custom API to do the import. With this we have already tested syncing 30k product to Odoo in around 2 hours. This could still be improved. For the export of product we are considering using the Magmi datadump API. We could use contribution for this development. Lastly, we will also provide modules to support payment gateway integration with Authorize.net for customers using it with Magento. This will support Tokenization with CIM. This module will be standalone free release.

Hello, I have no idea what your problem is with the information provided, There are schedules you have to activate for products to sync.

When I try to sync the products from the job it shows invalid api error. Can you please give me the information about the installation of OpenobjecConnector, which are .php files as my former package was of python.

Hi, Yes the project is moving along quickly. We estimate at this time the development will be complete for the first release in 2-3 weeks.

Would you like to test this? It is ready for testing. Please email me openerpmaster@gmail.com if you are still interested in testing.

Luke, Thank you for the detailed spec. This would be the ultimate ideal solution. Currently the project is being funded by a single client. Most of the features the connector will support in the first release will be the clients requirements. The focus for this connector is unique. The design is focused on businesses with complex attributes. Specifically, Retail stores that sell Shoes/Clothing items with many different sizes/shapes/colors. Some high level features the connector will support in the initial release: 1. Attributes management. Magento uses whats called a Sparse Matrix to implement it's attribute system. This is a very complex storage model (EAV) that is not supported in odoo, and most other ERP software. This connector will support it. This means you could have a different product description per website instead of having a single field for description, create attributes dynamically in odoo and sync them with your Magento instance. 2. Order Management/Payment Management. Manage orders and payments in odoo. More on this later. 3. Stock Synchronization. Sync stock from odoo to Magento. More on this later. 4. Mass product updates. The connector will provide the ability for you to export and import spreadsheets with product data and push to Magento from odoo. The focus will be speed and flexibility. Much like what Magmi offers today for Magento. Some features the connector will NOT support in the initial release: The connector is designed to work exclusively with Magento. It will not support eBay, Amazon, etc. Why? This significantly simplifies the design of the connector and makes it much easier to work with. The connector will support only a single Magento instance. Why? Again, the project is being funded a client and they only have 1 instance. It will however, support multi storeview/websites. The connector could support multiple instances in the future if funding becomes available.

@OpenERP Master, Thanks for the detailed reply. I look forward to seeing this project once it's ready for release. Do you have a github profile you'll make it available on once it's finished?