News and announcements

New OpenERP Magento connector: EUR 45’000 collected in 2 months!

Written for Magento OpenERP Connector by Maxime @ Camptocamp on 2013-04-09

Dear Magentoerpconnect Community,

The fundraising campaign - - to finance the new OpenERP Magento connector allowed to collect so far an amount of EUR 45’000, providing the community the means to develop the first version of this connector, fully compatible with OpenERP 7.0 and the latest versions of Magento.

Initiated mid-January 2013 and driven by Camptocamp, this campaign recently experienced a quantum leap thanks to the EUR 12’000 investment made by the company Debonix, an loyal e-commerce client of Camptocamp.
Out of the EUR 150’000 expected by mid-May, a total amount EUR 45’000 has been raised for this unprecedented innovation for all e-commerce businesses using not only Magento, but PrestaShop as well!

On the technical side, this amount has already allowed to rewrite the core of the OpenERP Magento connector, as follows:

1. First layer: a development environment – the connector framework – intented for giving developers the power to connect OpenERP to any other application; this connector framework is also fitted with an innovative system to manage data synchronizations as single tasks;

2. Second layer: generic e-commerce features for any e-commerce platforms (Magento, PrestaShop…), for the management of specific e-commerce workflows associated to orders and payments;

3. Third layer: specific features for the optimized synchronization of orders, products, clients, stock levels, shipping and tracking numbers, etc. between Magento and OpenERP.

The synthesis of the work conducted to-date is available in a form of a short video:

Our fundraising efforts are scheduled to end mid-May. The community still needs additional financial contributions to complete a number of important developments, including the management of all Magento-specific products and the automated export of each invoice that has been generated by OpenERP in the client account of Magento.

Just one more push to reach our forecast goal!

E-commerce businesses, integrators of e-commerce solutions and/or ERP, visit now Indiegogo - - , the community fund raising platform, and help the community to develop the OpenERP Magento connector, an amazing tool allowing the automation of the management of dozens or even hundreds customer orders per day!

Any financial contribution of EUR 2’000 or more will grant exclusive rights to test prior release this powerful bi-directional synchronization between Magento and OpenERP! For more info, just send us an email:

As a strategic member of the community of developers on the project, Camptocamp would like once again to thank all current investors: Logic Supply, Debonix, Linko Solutions, B-informed, Savoir-Faire Linux, Avanzosc, Zupy!,, Eric Vernichon, Marcello Bello, Mark Felling and also all other anonymous entities.

On behalf of the Core Developers and the project teams, thank you so very much for your participation, involvement and support!

The Magentoerpconnect Core Developers

Updated .

OpenERP Magento Connector New Generation: Call for Funding

Written for Magento OpenERP Connector by Maxime @ Camptocamp on 2013-01-28

Dear Magentoerpconnect Community,

As you might already know, the Core Developers – most specifically Camptocamp and Akretion – are gathering funds to ensure the financing of all new developments required for the OpenERP Magento Connector New Generation.

Why an OpenERP Magento Connector New Generation?
     * The solution currently implemented has been existing for more than 4 years (since v5). With the release of OpenERP v7, it is now a good time to completely rethink the architecture of the connector, both on the Magento side and the OpenERP side.
     * The new improvements will truly guarantee e-commerce business owners and integrators a simpler and more powerful solution, meeting the ever-increasing needs and expectations.

The foreseen developments are estimated to cost about EUR 150'000.- and to be completed by the end of April 2013. A funding campaign has been launched mid-January 2013.

So far, EUR 16'500.- have been collected: this is a good start!

With USD 20'000.- (~EUR 15'000.-), Logic Supply is the very first main financial contributor of the project. This US-based e-commerce store - - specializes in providing specific computers and computer components for custom-built systems in the USA and Europe. This has been possible with the collaboration of US-based IT company URSA Information System, OpenERP Gold Partner -

Thank you very much for your substantial investments! It does indicate that this project is regarded as essential in developing a new dimension for e-commerce business owners as well as OpenERP and/or Magento integrators!

The Core Developers also warmly thank the following companies and/or individuals for their donations or contributions: Maxime Chambreuil from Savoir-faire Linux, Avanzosc, Fabio Martinelli from Zupy!, Linko Solutions And Kyle Waid from Gekko Tek.

Until today, the connector has only been financed through Core Developers and all developments made available to the community. With new OpenERP 7.0 version, it is now a perfect time to invest a lot of effort and time to re-engineer the magentoerpconnect so that the Connector New Generation becomes faster to learn, simpler to implement and easier to maintain.

The OpenERP Magento Connector New Generation is under AGPLv3 license; any financed development will be made available to all.

We need your help to ensure that this code refactoring will bring the community all the required levels of satisfaction when connecting OpenERP 7.0 to Magento.
     * For donations up to EUR 2’000.-, please visit:;
     * For investments higher than EUR 2’000.- please send us an email at

The more you invest, the more you increase your visibility on this project (see:
Donation levels and associated bonus:
     * EUR 100.- and over → a thank you note on LaunchPad;
     * EUR 500.- and over → a white book on the topic by Core Developers;
     * EUR 1’000.- and over → your name with a short description on the white book;
     * EUR 5'000.- and over → your name mentioned as a financial contributor on project's overview page;
     * EUR 20'000 and over → your special requirements are taken into account in the development roadmap to ensure you an optimized return on investment when you implement magentoerpconnect.

On behalf of the Core Developers and the project teams, thank you so very much for your participation, involvement and support!

The Magentoerpconnect Core Developers

Updated .

Announcement on Magentoerpconnect series and releases

Written for Magento OpenERP Connector by Guewen Baconnier @ Camptocamp on 2012-05-30

Dear Magentoerpconnect community,

Here is an announcement on the current and future state of Magentoerpconnect,
the explanations of the differents branches which have maybe mislead you,
and our last updates on the release policy.

In february, Sébastien Beau at Akretion has initiated a huge refactoring
on the modules base_external_referentials and base_sale_multichannels.
This work started during the Camptocamp-Akretion code-sprint
on the prestashoperpconnect project [1].
The goal was to improve the generic blocks between the connectors,
allowing to have as less code as possible in each connector (magento, prestashop, ...).
Which required a rewriting of the base_external_referentials API, breaking the

Taking advantage of this refactoring and new structure of the base_external_referentials API,
Sébastien introduced a lot of new features on the new magentoerpconnect "future" branch.
I'll let him resume his work in a further e-mail ;-)

During this time, the development on the "current" version pursued on its own way,
mainly with fixes or optimizations, but also with some more ambitious changes
like the refactoring of the partner addresses management.

So we had to maintain 2 version of each modules together :
the current "legacy" version, and the "future" version which is not backward compatible.
Both run on OpenERP 6.1.
This has led to some misleading in the community / users of magentoerpconnect
and I think we clearly lacked communication here, I hope that this announcement
will remedy to that.

Today, the "current" magentoerpconnect [2] branch is going to be stable, meaning stable
enough to be able to run in production. I see some fingers rising, you are right,
there are still some bugs, especially with some workflows like prepaid. We change the
state of this version to "stable", which means that we won't develop any new feature
on it, and avoid API changes, we'll still fix bugs and merge your bugfixes.
This branch will be attributed to a new serie called "legacy".

Today, the "future" magentoerpconnect [3] branch is going to be soon stable enough to be
able to run in production. Some changes done on the "current" branch still have to
be ported to this one. Our intention is to stabilize it up to the hilt to be a
replacement for the legacy branch. Soon, no new feature will be accepted in
this branch, so this is the last moment to submit your merge proposals.

When the "future" magentoerpconnect will be considered as stable and freezed,
any new feature development / API changes will have to be proposed on the trunk branch.

The new branches are not backward compatible with the legacy branch, so if you start
a new implementation, and are brave enough to face some bugs, we'll recommend you to go with
the "future" branch.

On the developer / committer side, we'll from now always create a merge proposal which
have to be accepted by another committer for any change on a stable / stabilization branch,
this will allow a double-check and peer review before committing anything on a branch used in
production. By the way, we hope to see the community members review and comment the merge
proposals as well.

We also took the opportunity to move out the modules from the pell-mell extra-trunk
branch in smaller project branches (listed below), so extra-trunk won't be necessary anymore

In short, we introduce new series :

 - A serie with the legacy code (before refactoring)
   The current branch compatible with the modules in extra-trunk,
   which have to be replaced by the "future" branch. Stable branch.
   Merge proposals mandatory for any commit.

 - Series with the refactored code (named "future" so far)
   The stable branch with the refactored code.
   The branch on this serie will stay in state "Development" until
   it is stable enough to be usable in production.
   To be considered currently as a "beta" version.
   Soon, no new features will be merged, only bugfixes.
   Merge proposals mandatory for any commit.

 - The development branch

Required branches for each serie :
- openerp6.1-legacy-module
lp:openobject-addons/extra-trunk => for base_sale_multichannels, base_external_referentials, product_m2mcategories, ...
lp:c2c-ecom-addons/6.1 => for product_links
lp:magentoerpconnect/magento-module-trunk => Magento module

 - openerp6.1-module
lp:magentoerpconnect/magento-module-trunk => Module for Magento
lp:extra-trunk is still needed for some modules (product_images_olbs, product_m2mcategories),
they will be moved very soon to e-commerce-addons so lp:extra-trunk won't be required anymore.

 - trunk
lp:openobject-extension => for base_external_referentials, ...
lp:e-commerce-addons => for base_sale_multichannels, product_links, ...
lp:magentoerpconnect/magento-module-trunk => Module for Magento

Thanks to all the people involved in this project, contributors, bug reporters,
and all who carry forward the project...
In the future, we'll try to communicate more, using this community mailing list.

For the Magentoerpconnect team,
Guewen Baconnier (Camptocamp)

[2] previously known as lp:magentoerpconnect
[3] previously known as lp:~magentoerpconnect-core-editors/magentoerpconnect/futur-trunk

Magento Extension Released for magentoerpconnect

Written for Magento OpenERP Connector by Sharoon Thomas on 2009-11-14

The magento connect extension (Latest) for the new magento open erp connector has been released as an extension. The extension key is:magento-community/Openlabs_OpenERPConnector

Please use magento extension manager to use the magentoerpconnect


14 of 4 results