PF_MULTI_004 — Partner-coordinated customer acknowledgement from quote to sales order
This proof tests one bounded customer-accepted path: acknowledge a representative channel quote, generate its associated sales order, inspect the reciprocal references and selected commercial fields, and confirm the order's customer-acknowledged state. It does not claim a dedicated acceptance date, comprehensive project outcomes, or dashboard reconciliation.
kind: proof_catalog
schema_version: 2
proofs:
- id: PF_MULTI_004
vertical_ids:
- M1_V1
- M1_V2
- M1_V3
- M1_V4
- M1_V5
- M1_V6
- M1_V7
name: 'Partner-coordinated customer acknowledgement from quote to sales order'
status: approved
proof_type: 'workflow test'
safe_artifact: >-
One sanitized, non-sensitive customer-accepted sales quote for a
channel-mediated manufacturing account, using a generic customer and
project label, one internal sales user, one representative associated
external partner or contractor, predeclared quote and delivery dates,
quantities, price, and an associated sales order. No live
customer-identifying, commercial, or financial data is required.
procedure:
- >-
Record the representative quote's expected expiry or due date,
line-level shipping-start date, quantities, and price before beginning
the test.
- >-
Create or select the representative quote and add the external partner
or contractor through the quote's accounts-and-contacts association,
using the intended test authorization.
- >-
Open the public quote-review surface and inspect the quote number,
expiry date, quantity, price, shipping-start date, total, and Review and
Confirm Quote step.
- >-
Have the representative external stakeholder coordinate the quote dates
with the internal user, subject to the configured authorization model.
- >-
Complete the public quote-acknowledgement step and verify that the quote
reaches acknowledged status.
- >-
Run Create sales order from the quote and verify that Quote
data.salesOrderId and Order data.salesQuoteId or data.salesQuoteNumber
resolve the same pair of records.
- >-
Open the public order-review surface and inspect the order's status,
expected delivery date, line shipping-start date, quantities, and price.
- >-
Complete the customer-acknowledgement step. If the internal Confirm
Sales Order action is also run, record it separately from customer
acknowledgement because it enforces internal pre-confirmation
invariants.
- >-
Reopen the quote and sales order and inspect their acknowledgement
states, reciprocal references, and predeclared commercial fields.
expected_observation: >-
The public quote surface exposes the representative quote details and
supports acknowledgement. The acknowledged quote resolves to an
associated sales order, the sales order resolves back to the quote, and
the public order-review surface exposes the agreed order or delivery
dates, quantities, and price. Customer acceptance is inspectable through
the acknowledged state; no dedicated acceptance or
outcome-confirmation date is claimed.
acceptance_criterion: >-
The test passes only when the representative quote reaches acknowledged
status, Quote data.salesOrderId and Order data.salesQuoteId or
data.salesQuoteNumber resolve the same quote-order pair, the associated
order reaches its customer-acknowledged state, and the inspected quote and
order values for the selected due or expiry date, expected delivery or
shipping-start dates, quantities, and price match the predeclared
representative values with no unexplained mismatch.
owner: sales
capability_boundaries:
- >-
Quote data.accountsAndContactsLines corroborates associated accounts and
contacts but does not establish external-partner authorization,
contractor semantics, or stakeholder-role mapping.
- >-
The public quote surface exposes Review and Confirm Quote, quote number,
expiry date, quantity, price, shipping-start information, and total.
Quote acknowledgement uses the implemented acknowledged-status path.
- >-
Quote data.salesOrderId references sales/order, while Order
data.salesQuoteId references sales/quote and data.salesQuoteNumber
retains the source quote number.
- >-
The Order status catalog defines acknowledged as customer acceptance by
email or a salesperson marking the order acknowledged. The proof must
record which path the representative test uses.
- >-
The internal Confirm Sales Order action invokes
sales-ai/confirm-sales-order-v2, which validates and promotes the draft
order before downstream fulfillment hooks. Internal confirmation is not
by itself proof of customer acceptance.
- >-
MCP did not resolve a dedicated acceptance or outcome-confirmation date.
The grounded dates are quote due or expiry date, Order expected delivery
date, and line shipping-start date.
- >-
Exact quantity and price storage paths remain ambiguous among several
order-line candidates, although the public surface exposes Quantity and
Price.
- >-
EV_MULTI_006 reports production use across more than 25 buyer accounts
collectively spanning M1_V1 through M1_V7 over one year, with buyers
agreeing that the features worked. Exact account identities, calendar
dates, observations per vertical, and role participation per account
were not supplied.
- >-
Customer acknowledgement of a quote or order is not independently
verified final project award in every channel workflow.
- >-
This proof covers only the customer-accepted path. It does not capture
or demonstrate projects awarded to another supplier, cancelled projects,
or no-decision outcomes.
- >-
The configured dashboard capability is not demonstrated. Product
availability evidence alone is not a buyer dashboard result.
- >-
This proof does not establish comprehensive outcome coverage, winning
supplier, win rate, market share, price elasticity, revenue, margin,
conversion, reporting accuracy, time saving, or any quantified
improvement.
transfer:
level: prohibited
from_vertical_ids: []
conditions:
- >-
Use is limited to M1_V1, M1_V2, M1_V3, M1_V4, M1_V5, M1_V6, and
M1_V7. Any future or otherwise unlisted vertical requires separately
validated evidence and an explicit applicable canonical transfer
rule.
evidence_ids:
- EV_MULTI_006
- EV_PRODUCT_003
- EV_PRODUCT_004