İçereği Atla

Websers agreement

General terms and conditions


  1. Insufficient client input on the analysis shall lead to insufficient analysis, system configuration and SOPs development reflecting directly on the quality of the implementation spent hours and deadlines.

  2. The partner is not obligated to any deadline latency occurs due to late or insufficient clients requirements submission, latency in payment, rescheduling analysis, training or any other sessions requiring client’s presence.

  3. The project hours allocation is an estimation which should be agreed upon during the project planning phase in case of discovering new requirements.

  4. The actual timesheet spent hours are the measurement unit recognized in invoicing within this project scope.

  5. Any new requirements not mentioned on this contract points shall be considered as out of scope to be agreed upon on a separate offer/contract.

  6. Any change request shall be reported from the partner, which would reflect directly on the final invoice.

  7. Any bug found by the client/ partner caused purely from the partner’s code shall not be reflected neither on timesheets and final invoices.

  8. Support hours are considered within the scope of SLA not from this project.

  9. Regardless of the situation the partner is not obligated or expected to be involved in entering the regular data entry, updating , deleting or reviewing it unless this contract, the planning agreement or the SLA refers to such an act.

  10. The client is required to test the delivered tasks and give feedback shortly after task, project delivery.

  11. The client is expected to take the required arrangements to ensure smooth transformation from his side by preparing his team, their environment and efforts for the upcoming changes to minimize the change risks and escalations.

  12. The partner shall not be obligated to deliver working hours additional to the working hours cap set on this contract without early notice or agreement.

  13. Unless it is a support ticket or training session the partner shall be contacted officially through the focal points of contacts set on identified on this contract from the client side.

  14. Termination shall be one week prior to termination date, where the spent hours of the project shall be invoiced and paid immediately.

  15. Project handover, either after termination or due to agreement, the client is obligated to inspect, examine the delivered work and report shortly it to the partner with all the concerns raised, where the partner shall review the report and coordinate either to schedule an answering session, or official response in form of paid timesheet hours.

  16. By signing this agreement the client acknowledges their direct impact on the success of the implementation due to employees comprehension, performance and collaboration.

  17. Each receiving party of this project is entitled to sign the partner’s receiving party non-disclosable agreement, and by the terms of this contract the partner holds the right to prevent any 3rd party from accessing the project.

  18. The delivery of work is 100% remotely and on site trining is quoted sportily with markup price.  

  19. Odoo user license, odoo.sh hosting or any other server hosting fees are not included in our offer where the client shall seek this price quotation from odoo directly.

  20. The ready solutions and apps have a free amount of implementation hours within and any extra hour of usage shall reflect on the SLA hours therefore it shall be invoiced to the client.

  21. The apps are handled as final build apps not as open source unless it was offered as open source. 

  22. app stores and social media platforms verifications and fees are the client’s responsibility.

  23. Payment plan: 40% upfront to confirm the order with monthly timesheet settlement.