Odoo & API Diagnostic

$150

Total, fixed scope. $150 to TechnoVision plus $0 of licences you buy from the Odoo Apps Store into your own account.

The problem

Something is wrong and nobody can say what. An integration posts sometimes and not others, a scheduled job stopped, a payment confirms an order it should not have. Two people have looked at it, both have a theory, and the next step keeps being "let us try something".

What you end up with

A written finding with the evidence behind it: what is actually happening, why, what it would take to fix, and what it would cost. It is yours to act on, to shelve, or to hand to somebody else.

What is included

• A scoping exchange to agree exactly which issue and which environment — one of each
• Investigation against a reproduction we can run, not against a description
• The evidence: logs, requests and responses, database state, or whatever the fault actually leaves behind
• A written finding naming the cause, or naming precisely what still stands between us and the cause
• A scoped repair proposal with a fixed price where the scope allows one
• The fee credited against the repair if you accept it within 14 days

What this does not cover

• The repair itself. This buys the finding; fixing it is quoted separately once we both know what it is
• Any promise that a cause will be found. Some faults are in a third party’s system, or in data nobody kept — you get what the investigation actually established, stated plainly
• Any promise of a timescale for a fix, which cannot honestly be given before the cause is known
• A second issue, or the same issue in a second environment
• Production changes. We investigate; we do not change anything without a separate agreement
• Work that depends on a third party’s support ticket, API approval or credential reset — those run on their clock, not ours

How it runs

1. 1Agree the one issueIn writing, including what counts as having reproduced it. This is the step that keeps a fixed fee fixed.
2. 2Get accessRead access to one environment, through your own mechanism. We never ask for a password by email.
3. 3InvestigateAgainst a reproduction where one exists, against evidence where it does not.
4. 4Write it upThe finding, the evidence behind it, and what we are not sure of — that last part especially.
5. 5Propose the repairScoped and priced where the scope allows, with the diagnostic fee credited if you accept within 14 days.

What we need from you

• One issue, described well enough that we can both tell whether it has happened
• A way to reproduce it, or logs from a window when it did happen
• Read access to one environment — staging is fine and often better
• The name of somebody who knows what changed recently

How we both know it is finished

• You hold a written finding naming either the cause or precisely what stands between the investigation and the cause.
• The evidence behind the finding is attached and you can follow it without us.
• Where a repair is possible, you hold a scoped proposal with a price or a clear reason it cannot yet carry one.
• You can hand the document to another engineer and they can pick it up.

What you do while it runs

Separate from the list above, which is what you supply before it starts. A missing prerequisite stops the work beginning; a missing one of these stalls it halfway, which is the one that turns a fixed price into an argument.

• Give us read access to the agreed environment through your own mechanism — never a password over email.
• Tell us what changed recently, including the change somebody would rather not mention.
• Be reachable for one short exchange during the investigation.
• Accept that the answer may be "the fault is in a system neither of us controls", which is still a finding worth having.

No licence in this one

This is work rather than software. Nothing here requires you to buy one of our modules, and if one would genuinely help we will say so and you can decide separately.

Questions