# Tryton vs. ERPnext

**URL:** https://discuss.tryton.org/t/tryton-vs-erpnext/3738
**Category:** User
**Created:** [January 28, 2021, 2:18pm UTC](https://discuss.tryton.org/t/tryton-vs-erpnext/3738 "2021-01-28T14:18:55Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![udono](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/udono/32/2114_2.png) [@udono](https://discuss.tryton.org/u/udono)
#### Post date: [February 18, 2021, 8:59pm UTC](https://discuss.tryton.org/t/tryton-vs-erpnext/3738/6 "2021-02-18T20:59:07Z")

</div>

Thank you @htgoebel for your comparison.

For the Tryton side I would like to share some additional information.

> [@htgoebel](#):
>
> E.g. ERPnext has quite some functions (“onboarding”) making it easy to get started and testing, whereas in Tryton such wizards are rejected since there are other (manual) means to achieve the result.

The first-install-wizards infrastructure in Tryton is already in use in several modules:

- Create User
- Create company
- Create chart of accounts

Also we have separated user configurations for every functional topic. And don’t forget to participate our [_Blank State_ and _Onboarding_ discussion.](https://discuss.tryton.org/t/blank-state-improvements/)

> [@htgoebel](#):
>
> E.g. you can easy customize reports by simple dragging “variables” to the right place.

In Tryton you can customise most reports with LibreOffice or an text editor.

> [@htgoebel](#):
>
> This not only imposes quite some problems when changing entries, but also is slow and increases storage and memory consumption. The later is esp. true, since [every table contains a “modified-by” and “owner” user-id](https://github.com/frappe/frappe/blob/3d922183c78a2d58857dcc26ab80d3d1e6e86547/frappe/database/mariadb/schema.py#L24) as a string.

Tryton also uses these fields for every table:

- id as primary key,
- create-uid,
- create\_date,
- write-uid,
- write\_date

but we use `integer` for `id` and `uid` and `timestamp(6)` for the dates. `id` has default database INDEX and uses sequences. The `uid` refers to the `res_user` table, but is not `JOINT` for some reasons, but Tryton disallows the deletion of `res_user` entries.

> [@htgoebel](#):
>
> …which is a thread to GDPR compliance.

Please become part of [our GDPR discussion.](https://discuss.tryton.org/t/general-data-protection-regulation/) E.g. [Art. 17 of the GDPR](https://gdpr-info.eu/art-17-gdpr/) in Tryton is addressed with the possibility to _Erase_ parties at any time. The deletion of a party is done by [removing personal identifiable data in fields,](https://hg.tryton.org/modules/party/file/tip/party.py#l797) but keeping the records to satisfy the existing relational data integrity.

---

_[View the full topic](https://discuss.tryton.org/t/tryton-vs-erpnext/3738)._