As I was working on implementing the Maestro project in OpenERP v7, I came across a fundamental problem (for me) with product serialization. The out-of-box experience in OpenERP for managing serialized goods does not provide a consistent flow for receipt of serializing goods from a vendor or internal production, to the issue of serialized goods to a customer, and then the return serialized goods from the customer if necessary. It’s not that OpenERP isn’t technically capable, but the required software development is beyond the scope of the Maestro project.
(Tryton) Is a three-tiers high-level general purpose application platform under the license GPL-3 written in Python and using PostgreSQL as database engine.
It is the core base of a complete business solution providing modularity, scalability and security.
The Tryton framework was created by forking OpenERP v4.1 (when it was called TinyERP). The fork included both the server daemon and the desktop client. While OpenERP is concerned with being a superior ERP-like application, Tryton strives to be a superior framework for building ERP-like applications. The desktop client can be used by end-users, and is certainly up to the task, but some situations may find a simplified user interface more suitable (possibly web-type), tailored specifically to the end-user’s needs.
The Tryton framework and desktop client are licensed under the GPL v3. Although the GPL may not be considered as business-friendly as the BSD, MIT or Apache-style permissive licenses, it is far friendlier than the AGPL – which is the license used by OpenERP after v4.1.