EV_PRODUCT_004 — Quote acknowledgement and sales-order confirmation implementation path
Deployment-specific product evidence for the quote acknowledgement and sales-order confirmation workflow. It establishes inspectable product structure and execution paths, not buyer use, field-copy correctness, final project award, or a customer result.
kind: evidence_catalog
schema_version: 1
evidence:
- id: EV_PRODUCT_004
type: internal_validation
title: 'Quote acknowledgement and sales-order confirmation implementation path'
source: >-
MCP server d8189168 project_graph, flow_documents, and hook_graph
responses captured during the Codex create-proof task for P_00005 and
S_00013 on 2026-08-01.
publisher_or_owner: 'Naologic product repository via MCP server d8189168'
published_at: null
accessed_at: 2026-08-01
supports:
- >-
The sales quote table exposes a Create sales order row action. The
public quote form exposes Review and Confirm Quote and displays quote
number, quote expiry date, quantity, price, shipping-start information,
and total.
- >-
The Quote document is a prospect quotation convertible to an Order once
won. Quote data.salesOrderId references sales/order, while Order
data.salesQuoteId references sales/quote and data.salesQuoteNumber
retains the source quote number.
- >-
Quote data.accountsAndContactsLines represents associated accounts and
contacts. This structure does not by itself establish external-partner,
contractor, authorization, or stakeholder-role semantics.
- >-
Quote statuses include draft, open, acknowledged, rejected, expired,
canceled, won, and lost. The public quote-acknowledgement flow updates
the quote through the acknowledged-status path.
- >-
Order statuses include draft, open, acknowledged, in-process, completed,
canceled, and rejected. The Order status definition states that
acknowledged means the customer accepted the order received through
email or the salesperson marked it acknowledged.
- >-
Quote and Order expose line-level shippingStartDate and quantity and
price candidates. Order also exposes expectedDeliveryDate.
- >-
The generate-sales-order-from-sales-quote hook is triggered by
sales/sales.generate-order-from-quote. The
process-sales-order-from-quote hook processes a new sales order from an
existing quote.
- >-
The Confirm Sales Order flow invokes sales-ai/confirm-sales-order-v2,
which transitions a draft sales order into a confirmed state after
enforcing its pre-confirmation invariants.
scope: >-
Naologic sales quote acknowledgement, quote-to-sales-order relationship,
public quote and order review, and internal sales-order confirmation
workflow.
confidence: medium
notes: >-
MCP matches include sales/sales.quotes-table-with-pivoting,
sales-order-public/sales-order-public.quote-public-form,
sales/sales.retrieve-sales-order-for-confirmation,
sales/sales.confirm-sales-order, sales/quote, sales/order,
inventory-management/generate-sales-order-from-sales-quote,
inventory-management/process-sales-order-from-quote, and
sales-ai/confirm-sales-order-v2. No dedicated acceptance or outcome
confirmation-date field resolved. Quote date searches returned dueDate,
expiryDate, and lastEmailSentDate; Order searches returned dueDate,
expectedDeliveryDate, and lastEmailSentDate. Exact external-partner
authorization semantics and stakeholder-role mapping remain unverified.
Exact quantity and price storage paths remain ambiguous among several
order-line candidates, although the public quote surface exposes Quantity
and Price. The MCP establishes implementation structure and execution
paths, not buyer use, field-copy correctness, dashboard configuration,
final project award, or a customer result.