Tryton Vs Odoo
Andres Politi
Cédric Krier
--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
Axel Braun
Raimon Esteve
Andres Politi
Dominique Chabord
- if the customers wants to work with you and Tryton is the plateform
you are used to, he should stay with your original choice. Explain why
you choosed Tryton, should be enough if this customer trusts you and
witshes you to part of the solution.
- there are many sport federations who might benefit from an
association verticalisation of Tryton. They can spread it over
hundreds of small to large clubs, and will probably improve it. Your
customer will benefit from these improvements.
Now regarding Odoo as an alternative :
- I would NOT recommand using Odoo without the Enterprise contract. It
is the only possibility to get upgraded over time, in particular when
Python2.7 support will end (sooner than expected). Odoo
cummunity-edition is a dead end, Odoo from OCA (association) is not
more than a question mark. So Odoo is not free of charge and can be
expensive if there are many users.
- I would NOT recommand customizing Odoo, first because it is less and
less designed for customization, second because it contradicts
Enterprise contract. Odoo is a take it or leave it, a kind of
off-the-shelf solution, not a flexible framework. Any change to Odoo
will have huge consequences over time.
- Odoo has many bling-bling functions that won't just work, and
because of the project leadership, nobody can effectively fix them.
Tell your customer not to trust Odoo integrators who hide difficulties
to put a foot in the door, ansd make think Odoo Entreprise is just an
option to reduce the bill artificially.
Hope this helps.
> You received this message because you are subscribed to the Google Groups
> "tryton" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tryton/bf7a4601-8d45-4027-94c6-c4e8e33d6df3%40googlegroups.com.
Cédric Krier
> It's a system for a football club that needs to manage the invoicing of its
> members.
difficult to implement (I guess neither in Odoo).
So the best advantages you can show are:
- migration are in Tryton core development instead of being a
business model like for Odoo;
- the Tryton native client can be much faster than the Odoo web
interface on large data set (if it is relevant in this case);
- a better correctness in computation thanks to Decimal instead of
float for Odoo (quite technical but it talk to some users);
- better scalability when working on large dataset for Tryton;
- protected by the Tryton Foundation and shared license (like Linux)
instead of owned by a single company;
Also what I see is that Tryton is better to adapt to the user needs
when Odoo has more feature out of the box but user must to adapt its
needs.
PS: Please don't top-post on this mailing list, see
http://groups.tryton.org/netiquette
Axel Braun
> On 2016-01-22 06:08, Andres Politi wrote:
> > It's a system for a football club that needs to manage the invoicing of
> > its members.
>
> There is no module for that in Tryton base but it doesn't look like very
> difficult to implement (I guess neither in Odoo).
Andres Politi
Mark Hayden
Nice to see more interest in Tryton vs. Oodo!
On 22 Jan 2016 7:50 am, "Andres Politi" <andres...@tecso.coop> wrote:
>
> It's a system for a football club that needs to manage the invoicing of its members.
>
This would involve the creation of a "membership" or subscription module which would establish a relationship between party and account_invoice. I have played with that concept a bit so I know it is pretty straight forward.
My overall impression is that Tryton is backed by a more collaborative developer based community whereas Odoo is backed by a commercial entity and a network of partners or "dealers" that are more product-based.
With Odoo you may get a prettier more featureful out-of-the-box experience but custom development and upgrade support are more costly and troublesome. Therefore if you cannot adapt to Odoo it is more difficult to deal with.
Tryton is kind of like Debian vs Odoo being more like Ubuntu in terms of leadership and goals. As a result Tryton makes reliability and maintainability a priority over appearances and features. It is regarded more as an application platform or framework than a canned product and users are more apt to be involved in development. This makes it a far better choice if you are looking to tailor a system to your needs rather than change the business to conform to the system.
>
> El jueves, 21 de enero de 2016, 17:30:05 (UTC-3), Cédric Krier escribió:
>>
>> On 2016-01-21 11:33, Andres Politi wrote:
>> > Hello. We have been developing for Tryton for several months and we found
>> > it very powerful and simple. We need to convince a client to use Tryton
>> > instead of Odoo, with which we are not very familiar. Is there any recent
>> > document comparing the two that we can use to bring them to Tryton's side?
>>
>> What will be the usage?
>>
>> --
>> Cédric Krier - B2CK SPRL
>> Email/Jabber: cedric...@b2ck.com
>> Tel: +32 472 54 46 59
>> Website: http://www.b2ck.com/
>
Peter Müller
1. Better code base: any code base will need an initial learning how are things are doing. There is doc, but the source will be with you.
2. "Native" client: tryton has web and native client. Odoo drops native client completely some time ago. Maybe Odoo web client is better (i'm using only native client) but web technology is a lot of blinky-blinky and not suitable for "power" user ( i hardly can imagine working in a warehouse only with standard web client)..
3. Upgrades included: Odoo will need a contract for version upgrading. That isn't not a great issue, but IMHO against open source idea. My experience is that ERP systems has very low upgrade needs. When you have a running system you need long time support. 10 yrs is a reasonable long term support and you won't change the (mayor) version if not really needed. That won't include bug fixing, that must be always on.
Armand Mpassy-Nzoumba
I do not know Odoo at all and I am new to the Tryton world. I run a consultancy company in Central Africa. I selected Tryton a number of Open source ERP systems (including Odoo) after conducting a serious comparative study, and testing a few of them.
I can ensure you that Tryton is jungle proofed. I have implemented it in Franceville, a small city of Gabon (Africa). Until now (5 months), I have not got any complaint from my clients. It has great functionalities, it is robust, it is stable, it is very cost effective, it is great.
If it can run in „the African jungle“ without any issue, it can run anywhere in the world.
I have a lot of experience in IT and in Africa and I can confirm that none of these "big ERP" from the big IT companies had ever produced such a performance. There is also a great team of developers behind Tryton, with a wonderful spirit. In my opinion theses guys are among the best programmers in the world.
I can still continue writing hundred of words about it. However, I suggest you just do it, and implement a pilot project. This is the best way to convince yourself.
Kind regards,
Armand
Guillem Barba Domingo
Nice to see more interest in Tryton vs. Oodo!
On 22 Jan 2016 7:50 am, "Andres Politi" <andres...@tecso.coop> wrote:
>
> It's a system for a football club that needs to manage the invoicing of its members.
>This would involve the creation of a "membership" or subscription module which would establish a relationship between party and account_invoice. I have played with that concept a bit so I know it is pretty straight forward.