Terms of work

These terms apply to work carried out by Private Entrepreneur Zubak Oleg (Ukraine), who runs odoo-dev.org. They cover work agreed by email or by a separate written contract. Where a signed contract says something different, the contract wins.

What is agreed before the work starts

The scope is written down before anything is built: what is included, what is not, and which stages the work is split into. An estimate is an estimate and not a fixed price, unless it says in writing that it is fixed. If the scope changes, the estimate is revised and agreed again before the change is made.

How the work is billed

Work is billed by stage or by time at an hourly rate agreed in advance. The invoice names the currency and the payment method. Invoices are payable within 14 calendar days unless the invoice itself says otherwise.

If an invoice stays unpaid more than 30 days after its due date, work on the remaining stages pauses until it is settled. No penalty interest is charged and no debt collection is involved unless a separate signed contract provides for it.

Your code, your access, your data

Everything written for you goes into your repository and onto your infrastructure from the first day. Once the stage it belongs to is paid, the rights to that code are yours. Third-party components keep their own licences, and Odoo modules are usually LGPL: that is stated where it applies.

Access to your systems is used only for the agreed work. Copies of your data are made only where the work needs them, kept on the infrastructure agreed with you, and removed when the stage closes.

Confidentiality

Anything seen during the work stays between us: data, processes, prices, code. Your name appears in public only with your written agreement, and the case pages on this site are published the same way.

What is fixed for free and what is not

Defects in my own code, found within 30 days after the stage is handed over, are fixed at no charge. That does not cover changed requirements, updates to Odoo or to third-party services, or problems in code written by someone else.

Odoo itself, hosting, and third-party services with their APIs are not under my control, and no promise is made on their behalf. Delivery dates are targets agreed in good faith; a date becomes binding only if a signed contract makes it so.

Liability

Liability is limited to the amount paid for the stage in which the problem arose. Lost profit and indirect losses are not covered. Nothing here limits liability that the law does not allow to be limited.

Stopping the work

Either side can stop at the end of a stage by saying so in writing. Work already done is invoiced, and the code, the accesses and the environments stay with you. Nothing is held back as leverage.

Law and changes to these terms

These terms are governed by the law of Ukraine, unless a separate signed contract names another. The current version is published at odoo-dev.org/terms; the version that applies to an order is the one in force when the order was agreed. Questions about these terms go to the email address in the footer of this site.