[IMP] Sales: Invoicing project milestones

[jero-odoo]

Rewriting the Sales doc for invoicing based on milestones

[robodoo]

[jero-odoo]

Hey @theRealThagomizer this is ready for review. Thanks!

[theRealThagomizer]

Hiya, @jero-odoo! This looks good. Certainly it's a heck of a lot more elegant than the sprawling version that proceeded it. I caught a few typos that I made suggestions to correct and a few things that got me pondering where I left comments, but I think this is ready to go forward once the typos are fixed.

I'm not sure what the rest of the review procedure is for you and Lara, so I'm just going to mark this as approved and figure you know if anyone else need to see this before it can be merged. Thanks!

[jero-odoo]

Thank you @theRealThagomizer !

@StraubCreative this is ready for review!

[Felicious]

Hi @jero-odoo!

I appreciate the effort to reduce redundancy from the original version and to streamline content that now lives in the updated Project documentation. The writing in this draft is noticeably more concise. However, the underlying structural issue from the original doc is only partially resolved. Previously, the workflow was buried in procedural detail without a clear explanation of what happens in Sales, what happens in Projects, and what happens during Invoicing. And how clicking one button affects something else (e.g. Reached in projects --> updates Delivered on the SO)

This draft shortens the text, but the lack of a clear, high-level overview remains. Without an explicit breakdown of which actions occur in which app, users still have to infer the workflow. To make the documentation fully actionable, the revision needs clearer guidance and a more explicit framing of the end-to-end process, in addition to the trimmed-down writing. To summarize:

• Milestone creation steps are unclear. The text references another document but does not clearly indicate that milestone creation is handled elsewhere, leaving the workflow incomplete.
• Behavior of the Milestones smart button is ambiguous. It is not clear whether users are expected to create milestones directly from the sales order or rely on default milestones provided by a product or project template. This needs explicit clarification.
• Invoicing instructions lack specificity. The invoicing flow relies on conceptual descriptions instead of concrete field names, menu paths, and button labels. This prevents users from following end-to-end steps.
• Delivered % explanation is inconsistent. Does Odoo use percentage or cost?

The second revision requires substantial tightening to provide clear procedural steps, unambiguous explanations, and references to related documentation for each step. Looking forward to reviewing that once it's ready!

[Felicious]

I understand why this section was removed because it's unrelated to the sales flow, and it's covered in the project milestone doc

However, we should acknowledge that the milestone can be marked as reached and link to the doc that outlines how

[Felicious]

I like how concise you've managed to write the milestone product creation process!

However, this document is currently missing step-by-step instructions on how to create milestones. You acknowledge that milestone creation is handled in a different document, but the current text does not explicitly indicate which prerequisite steps are external.

The result is a structural gap: users cannot tell where milestone creation actually occurs, nor whether the current doc expects them to arrive with milestones already defined.

To do for the next revision: Add a clear, unambiguous pointer that milestone creation is not covered here, e.g., “Milestones must be created in the Project app; see Project milestones for step-by-step instructions.” Without this, the workflow appears incomplete.

[Felicious]

To me, this is concise but has an ambiguous implication that milestones can be manually created from the SO

This section suggests that users can click the Milestones smart button and create milestones directly from the SO. You need to clarify whether this is a supported workflow or merely an editing surface.

The text also avoids addressing whether Odoo supports default milestone sets tied to a milestone product (via a project template or project task structure). That is a major functional assumption the reader needs resolved.

Todo for the next revision:

• Explicitly confirm whether milestones can be created manually from the SO.
• If default milestone sets are expected to come from a project template or from another Project configuration, state that explicitly and point to the exact documentation.
• If this behavior depends on product configuration, and isn't explicitly covered in the other doc, include the precise field names involved (“Project Template,” “Create on Order,” etc.).

Note: making this doc clearer may also imply we need to make changes to the project doc. If you feel that is the case, let me know and we can begin communicating with BE!

[Felicious]

Suggested change

	corresponding `25%` of the total number of hours is marked as *Delievered* on the invoice.
	corresponding `25%` of the total number of hours is marked as *Delivered* on the invoice.

[Felicious]

this example is clear but seems to be in the wrong place, in my opinion? It's trying to do two things at once:

• Give context as to what milestones are and how they can be added (good, but seems to belong in an explicit "project milestones setup" section
• Give procedural instructions to navigate to milestones, (doesn't explicitly say how to mark them as reached), and navigate back to the SO to show the invoiced column is filled. Let's rewrite to include operational specificity of the whole invoicing workflow! (my feedback given in the next comment)

[Felicious]

The invoicing workflow is described in conceptual terms but leaves out necessary navigational and field-level instructions. Users cannot reconstruct the actual UI path or the required field interactions.
Examples of missing specificity:

• The path to reach milestones in the Sales or Project apps.
• The explicit field name that must be toggled to mark a milestone as reached.
• The menu path and button labels to return to the SO.
• What appears on the invoice after clicking Create Invoice.

Todo: Rewrite the invoicing steps with explicit UI elements, e.g.:

• "After a sales order is created, navigate to the milestones by going to [menuselection path]".
• “Enable the Reached checkbox on the milestone line.”
• “Go back to the SO by [navigational steps]. Then, click Create Invoice.”

Avoid abstract phrases like “can be tracked through” and “is updated”; replace them with concrete instructions and field names.

[Felicious]

I might be overthinking here, but the draft mixes two concepts—percentage-based delivery and cost of the SO delivered—without defining how Odoo interprets the Delivered % field. There is an implicit assumption that the system prorates invoiceable quantity strictly by percentage, which may not match actual configuration.

I believe there are two methods: invoicing based on milestone percentage or sales price, so I'd like your help doing some testing to find out how this works, and likely need to document them separately using different examples or workflows.

Todo:

• Define the Delivered % field precisely.
• Clarify whether it translates into delivered hours, amount, or quantity depending on product setup.
  • document multiple methods if applicable