First things first: we have no published Limango connector. If you came looking for an Odoo module you install and forget, it is not in our catalogue and we know of none built specifically for Limango. What we can tell you is how its two channels work and what has to be solved inside Odoo before the first order lands.
Limango is two channels: shopping club and marketplace
Limango is a German shopping club within the Otto Group, aimed mainly at families. In the club, the difference from a marketplace is not size, it is the calendar: a campaign opens, runs for a few days and closes. Outside that window your product does not exist for the buyer; inside it, all the demand is concentrated. Alongside the club, Limango runs a marketplace with a permanent range where the seller ships straight to the customer, and that marketplace runs on Mirakl. They are two channels with different rules, and you want to know which one you are selling on before designing anything.
In the club, the short window decides almost everything else
A campaign packs into a few days the sales another channel would spread over weeks, and two operational consequences follow. First: units committed to the campaign cannot stay published on your other channels, or you will sell the same one twice. Second: the picking peak arrives all at once when the campaign closes, not drop by drop. An Odoo that copes easily with twenty orders a day will choke on six hundred in a morning if the scheduled actions and the picking routes were not designed for the peak.
Before accepting a campaign ask for two numbers: how many units you are committing and how long you have from the close. With those two you already know whether it fits in your warehouse. Without them, any planning is a wish.
Two channels, two different flows in Odoo
In a shopping club the usual arrangement is that, when the campaign closes, you send the aggregated goods to the club's warehouse and it distributes them: in Odoo that is one large sales order, its delivery and almost always a despatch advice with carton detail. The marketplace is the other way round: you ship each parcel to the end customer from your own logistics, with the returns label inside, and orders arrive one at a time. If your club contract asks you to serve the end customer on Limango's behalf, the flow resembles retailer dropship. Designing the integration for one mode and finding out later it is the other means rebuilding it.
The first thing to ask for is the spec, not a quote
On the marketplace, the exchange is Mirakl's: catalogue and offers as CSV, XML or XLSX, over SFTP or through the API, and Mirakl's seller API is documented. Limango also lists middleware partners to connect through, including Tradebyte, ChannelEngine, JTL, plentyONE and Billbee. The club is different: we have not found a public, documented API for it, and what you receive depends on your supplier contract and on the team that onboards you. Whichever the channel, until you have the specification in front of you nobody can honestly tell you how much work there is. The five questions that unblock it: which format, over which channel, how often, which fields are mandatory and who supplies the shipping label.
What Odoo needs, whatever the format
What changes is the transport of the data, not the underlying work. You need the external order reference stored in Odoo and looked up before anything is created, or the first retry leaves you duplicate orders. You need an explicit mapping between Limango's code and your product, usually by EAN, in a table somebody can review. You need the campaign price to be its own price list, not a discount typed line by line. And you need the committed deadline to reach the delivery note, which is where the picker sees it.
We have no Limango connector: this is custom work
Plainly: our catalogue of 117 modules has Amazon, Shopify, Mirakl, AliExpress, Temu, ManoMano, ChannelEngine and WooCommerce, but no Limango. We do publish a Mirakl connector, the natural starting point for the marketplace, but we have not tested it against Limango's instance, so we do not sell it as a Limango connector: every Mirakl operator sets its own categories, attributes and mandatory fields, and the campaign club may take a different route altogether. A Limango integration is custom development, built on the same foundation as the published connectors: a job queue with idempotent retries, a log of everything in and out, and tests on Odoo 17, 18 and 19.
When integrating is not worth it
If Limango is going to mean two campaigns a year and three hundred orders, integrate nothing: export the order file, import it into Odoo with the standard wizard and spend the money elsewhere. Development starts paying for itself when campaigns are recurring, when the same stock sells across several channels with a real risk of overselling, or when the deadline from the close is so tight that manual work simply does not fit. That allocation of stock across channels is covered in several marketplaces in one Odoo.
Frequently asked questions
Do you have a Limango connector for Odoo?
No. There is no published Limango module and we do not advertise one. We have a published Mirakl connector, but it has not been tested against Limango. The integration is custom development, and the scope depends on the specification Limango gives you.
Does Limango have a public API?
It depends on the channel. The marketplace runs on Mirakl, whose seller API is documented. For the campaign club we have not found a public API: the exchange is agreed during supplier onboarding. Ask for it in writing before quoting anything.
Does the same development work for other shopping clubs?
The foundation does: campaign orders, external reference, EAN mapping and deadlines. What always changes is the file layout and who supplies the shipping label.
Useful links inside FlexigoTech
Selling on Limango and not sure where to start?
Send us the specification they gave you and tell us which channel you sell on: club campaigns or the marketplace. We will tell you what can be automated, what is not yet worth automating and where we would start. Write to comercial@flexigobe.com or book a call.