Compatibility & Release Policy

Clear version targets, controlled releases and honest support boundaries for CESDevelopment apps and maintained Odoo solutions.

1. Purpose and scope

This policy explains how CESDevelopment describes compatibility, classifies releases and separates app-level defect support from broader implementation and maintenance services. It applies to CESDevelopment-authored apps and to other software or custom deliverables that we expressly agree to support.

The applicable app listing, order, quote, statement of work, software licence, Care Plan or other written agreement may contain product-specific terms. Those specific terms control if they differ from this general policy. Third-party software remains subject to its own publisher's licence, compatibility rules and lifecycle.

2. What “compatible” means

A CESDevelopment app is considered compatible only with the environment expressly identified in its product information or other written scope. Compatibility may depend on all of the following:

Compatibility means that the app is intended to perform its documented functions in the declared environment. It does not mean compatibility with every third-party module, customization, future Odoo release, operating system, browser, external API or undocumented workflow.

3. Before purchase or installation

Before buying, installing or updating an app, the customer or responsible technical provider should confirm:

• The exact Odoo major version, edition and hosting model.
• Every required module, package and external-service dependency.
• Whether existing customizations or third-party apps modify the same models, views or workflows.
• That the licence permits the intended installation and use.
• That a representative staging or test environment is available.
• That a current, restorable database and filestore backup exists before installation.
• That the responsible party has defined acceptance tests and a rollback plan.

4. Release types and versioning

CESDevelopment uses release labels to communicate the nature and expected impact of a change. The label does not replace the release notes or the environment-specific testing requirement.

Release notes

For material releases, CESDevelopment will identify the applicable app version, target Odoo version, significant changes, known issues, dependencies and required customer actions where relevant. A release may also identify migrations, configuration changes, deprecations or testing priorities.

5. Updates within a major version and major Odoo upgrades

Database upgrades, configuration migration, third-party app migration, custom-code conversion, data correction and end-to-end regression testing are not included merely because a new version of a CESDevelopment app exists.

6. App-level support included

Unless the product information states otherwise, app-level support is limited to reasonable investigation of a reproducible defect in the standard, unmodified app when it is used in the supported environment and the documented function does not operate as described.

Receipt or acknowledgement of a report does not establish that the app is defective. Investigation that identifies an out-of-scope environment, conflict, customization or service request may be quoted as paid work.

7. Exclusions from standard app support

Unless expressly included in an order, Care Plan or statement of work, standard app support does not include:

8. Care Plans and the Supported Stack

Purchasing an app does not create a Care Plan and does not transfer responsibility for the customer's entire Odoo environment to CESDevelopment. A Care Plan is a separate recurring service covering only the systems, apps, versions, dependencies and responsibilities identified in the customer's approved Supported Stack and plan documents.

• A System Baseline Audit may be required before an inherited or unknown environment can enter a Care Plan.
• The plan identifies included monitoring, maintenance, triage, update handling, response commitments and exclusions.
• New apps, customizations, integrations or infrastructure changes must be disclosed and may require review before they enter the Supported Stack.
• Unsupported or end-of-life components may require upgrade, replacement, an expressly priced extension or documented risk acceptance.

This separation allows customers to buy a focused app without paying for managed service, while giving customers who need lifecycle accountability a defined path to ongoing coverage.

9. Testing, backup and deployment safety

Every installation and update changes a live software stack. Unless CESDevelopment has expressly accepted deployment responsibility, the customer or its technical provider is responsible for the deployment process and production decision.

1. Use a representative staging, test branch or restored database copy.
2. Take and verify a current database, filestore and relevant code/configuration backup.
3. Read the release notes and complete every dependency, configuration and migration step.
4. Test the affected workflow, access rights, scheduled actions, integrations and critical adjacent processes.
5. Define the production change window, responsible person, monitoring period and rollback decision.
6. Promote the tested release—not a different or subsequently modified package.

10. Security, dependencies and external change

Security reports and fixes

Potential vulnerabilities should be reported privately through our contact channel with the affected app and version, Odoo environment, reproduction details and business impact. Do not send passwords, access tokens, private keys or unnecessary personal data. We prioritize confirmed issues according to severity, exploitability, affected scope and available mitigation. A specific response or resolution time applies only when stated in an active agreement or Care Plan.

Dependencies and third parties

Odoo, operating systems, Python packages, browsers, APIs, payment services, carriers and third-party modules follow their own release and support cycles. A provider change can affect an otherwise unchanged CESDevelopment app. Where commercially reasonable, we may adapt, replace or deprecate an affected integration, but substantial redesign, migration or third-party remediation may require a separate scope and fee.

11. Support lifecycle and end of support

Support status is app- and version-specific. When published, the app listing, release notes or customer communication will identify the applicable lifecycle state.

Where practical, CESDevelopment will provide reasonable notice of a planned end-of-support change and identify an available upgrade, replacement or paid transition option. Urgent security, platform, legal or third-party changes may require a shorter transition or immediate restriction.

End of support does not by itself disable an installed app or revoke rights already granted under its applicable licence. It means continued operation is at the customer's risk and future fixes, backports or assistance are not included unless separately agreed.

12. Reporting a compatibility or release issue

A useful report should include:

• The app name, app version and purchase or order reference.
• The exact Odoo version/build, edition and hosting model.
• Relevant dependency versions and recent system changes.
• Clear reproduction steps, expected result and actual result.
• Complete relevant error text or logs with secrets and unnecessary personal data removed.
• Whether the issue reproduces in staging with the standard, unmodified app.
• The operational impact and any safe workaround already identified.

CESDevelopment may request additional evidence needed to reproduce and classify the issue. If the evidence shows a customization, dependency conflict, infrastructure problem, unsupported environment or requested enhancement rather than an app defect, we will identify that boundary and may recommend a Baseline Audit, Care Plan or scoped development engagement.

13. Related terms and policy changes

Refund and cancellation eligibility is governed by the applicable product information, order terms, our Refunds & Cancellations Policy and any non-waivable rights provided by law. This policy does not create a refund right merely because a customer's actual environment differs from the compatibility information supplied before purchase.

Our Terms & Conditions, applicable software licence, order and service agreement also remain relevant. Nothing in this policy limits rights or obligations that cannot lawfully be excluded.

We may update this policy as our products, services, security practices or platform dependencies evolve. Material changes will be reflected by the updated date. A general policy update does not silently replace a signed agreement or product-specific commitment already in force.