Let us start with what matters: we have no published connector for OBI or for Hornbach. Neither is in our module catalogue and we are not going to pretend otherwise to keep you reading. If you sell on German DIY marketplaces and want orders to land in Odoo on their own, today that is custom development. What we can tell you is what makes this sector different, because it is not a fashion marketplace with a different logo: the product data changes, the freight changes and the returns change.
What already exists and what has to be built
In DIY we do have published connectors: ManoMano and the operators running on Mirakl, such as Leroy Merlin, Brico Dépôt, Decathlon or GACD. If the operator you care about runs on Mirakl, the work is done and it is a matter of configuration. OBI and Hornbach are not on that list. There the integration has to be written against their API, and that is quoted as custom integration work, not as a module licence. The first thing we ask for in those cases is their API documentation and a test account: without those, any deadline anyone gives you is invented.
A Baumarkt product record is the most demanding one you will ever fill in
A power drill does not sell with two photos and a title. You have to supply real package weight and dimensions, material, power or voltage, and for many categories an attached document: a safety data sheet for paints, solvents and adhesives; an energy label for lighting and climate products; a fire reaction class for insulation. The EAN is usually required per variant, not per product, and DIY variants are long: size, finish, quantity per box. All of that has to live in Odoo as product fields, not in a spreadsheet somebody updates by hand, because the marketplace rejects incomplete records and rejections arrive in batches. The same work, told through Amazon, is in syncing product data.
Before you publish anything: selling into Germany requires registrations that are yours, not your integrator's. Packaging in LUCID under the Verpackungsgesetz, power tools in the WEEE register, batteries in theirs. The marketplace will ask for the numbers before letting you list. Odoo can keep track of what you declare, which we cover in extended producer responsibility, but the registration is yours to do.
Goods that do not fit in a parcel
Bags of mortar, doors, sanitary ware, panels: a good share of a Baumarkt catalogue is bulky freight and travels by forwarder, not by parcel carrier. That breaks three things in a normal integration. The rate, because the price comes from volumetric weight, maximum length and sometimes from whether it has to be carried upstairs. The tracking, because a freight consignment does not emit an event every hour: it produces a delivery appointment, and if your delivery order expects a tracking number with events it stays empty. And the package, because one order can leave on four pallets and the marketplace wants to know before delivery. In Odoo you model this with packages per delivery and a carrier picked by weight and volume rules; the approach is in logistics integration.
Returning building material is not returning a T-shirt
Cut-to-size material does not come back. Neither does an opened bag. Broken sanitary ware does come back, but the forwarder moves it and the return can cost more than the product. A DIY integration has to accept partial returns by quantity, five tiles out of twenty, distinguish the reason — defect, transport damage, change of mind — because each one decides who pays, and it must not issue the credit note before somebody has looked at what arrived. If the connector refunds automatically the moment the marketplace says so, the margin leaves without anyone seeing it and you find out at quarter end.
What carries over from one connector to the next
The good news about there being no connector is that the expensive part is already solved elsewhere. The order identifier checked before anything is created, the mapping table between the operator's SKU and yours, stock allocation across channels, the fiscal position per destination country and the invoicing are identical on OBI, on Hornbach and anywhere else. What is specific to each operator is its API, its catalogue format and its order state machine. On a real project that distinction is the difference between weeks and months. And if you sell the same goods in several places, stock allocation is the problem of several marketplaces in one Odoo, not an OBI problem.
When you should not hire us
If you have two hundred SKUs and five orders a week on a single operator, custom integration does not pay for itself. A CSV and twenty minutes a day are cheaper than any development, and they leave you free to switch channels having invested nothing. The conversation changes when orders arrive every day, when you sell the same goods in three places and run out of stock in the worst one, or when month-end reconciliation occupies a full person. At that point the development pays for itself. Before that it does not, and we would rather say so than bill you for a project you do not need.
Frequently asked questions
Do you have an OBI or Hornbach connector?
No. There is no published module for either. It is built to order against their API and quoted as integration work, not as a module licence.
If the marketplace runs on Mirakl, does your connector work?
Yes. With Mirakl the connector already exists and what remains is configuring the operator and mapping the catalogue. If the operator is not on Mirakl it does not help and the integration has to be written.
Does it work on Odoo 17 and 18 or only on 19?
Our published connectors run on Odoo 17, 18 and 19, and on 20 the day it ships. Custom work is built for the version you run, and if you plan to migrate it is worth saying so before we start.
Useful links inside FlexigoTech
Selling on a DIY marketplace that is not on the list?
Tell us the operator, how many SKUs you have, how much of the catalogue is bulky freight and which Odoo version you run. We will check whether their API allows a clean integration and how much carries over from what we have already built. Write to comercial@flexigobe.com or book a call.