Archives
Contributors
[RFC] marketplaces connector module
Hello
We are working on a little maketplaces connector for small companies. It
connects Odoo with a feed provider which will transform data to export towards
marketplaces, prices comparators, etc. Everything is done with CSV files
export-import because a lot of feed provider, specially small ones, work like
this.
It was previously discussed in Roadmap Odoo 13 for retail industry :
https://github.com/odoo/odoo/issues/28179#issuecomment-462323744
(and next comments).
First step is to have something working with Iziflux, a little french feed
provider. But... How does field mapping should be build ?
I ask because looking at OCA/connector-lengow (Lengow is a big feed provider),
a lot of code is not Lengow related, but field mapping is hard-coded in a file.
It's a pity.
I don't care if first step use hard-coded mapping. But later I would like to
have something as generic as possible because all feed providers use nearly
the same data and thus the connector should be easily adaptable.
Should we use a form ?
or simply a CSV to put in the module directory ?
or hard coding is good ?
or something else ?
(please CC me)
--
Librement,
Xavier Brochard / zeroheure
« La liberté est à l'homme ce que les ailes sont à l'oiseau »
(Jean-Pierre Rosnay)
by xavier - 04:10 - 18 Oct 2019
Follow-Ups
-
Re: [RFC] marketplaces connector module
Hi Xavier, hardcoded mappings are easily getting a huge mess. I'd definitely suggest a "per feed" export mapping that can be configured using the backend. Best Frederik Am Freitag, den 18.10.2019, 14:11 +0000 schrieb Xavier Brochard: > Hello > > We are working on a little maketplaces connector for small companies. > It > connects Odoo with a feed provider which will transform data to > export towards > marketplaces, prices comparators, etc. Everything is done with CSV > files > export-import because a lot of feed provider, specially small ones, > work like > this. > It was previously discussed in Roadmap Odoo 13 for retail industry : > https://github.com/odoo/odoo/issues/28179#issuecomment-462323744 > (and next comments). > > First step is to have something working with Iziflux, a little french > feed > provider. But... How does field mapping should be build ? > I ask because looking at OCA/connector-lengow (Lengow is a big feed > provider), > a lot of code is not Lengow related, but field mapping is hard-coded > in a file. > It's a pity. > I don't care if first step use hard-coded mapping. But later I would > like to > have something as generic as possible because all feed providers use > nearly > the same data and thus the connector should be easily adaptable. > > Should we use a form ? > or simply a CSV to put in the module directory ? > or hard coding is good ? > or something else ? > > (please CC me) > > -- > Librement, > Xavier Brochard / zeroheure > « La liberté est à l'homme ce que les ailes sont à l'oiseau » > (Jean-Pierre Rosnay) > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 04:26 - 18 Oct 2019