CTR-CPQ · version 1

Configure, Price and Quote — Quote lines

Security review is open on the discount approval field, which carries an approver identity.

In reviewNever checked

What the contract says

These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.

Entity

Quote line · inbound

Primary key

quoteId + lineNumber

Declared volume

14,000 records a day

Freshness commitment

30 min

Owner

A. Whitfield · Revenue Systems

Vendor

Salesforce CPQ · high criticality · modeled

Cardinality

One quote to many lines. One line to exactly one product and at most one discount approval.

Write-back rule

None. The contract declares this feed read-only.

Review state

Neither review is performed by the team that wrote the contract.

Security reviewIn review

D. Contreras · Jul 2, 2026

Privacy reviewApproved

Maitre Olivier Lascaux · Jul 10, 2026

Validation and drift

Drift is only detectable on a contract that has been read against a sample.

Last validatedNever

No sample has been read against this contract.

No sample has been taken. Nothing is known about whether the source matches this contract.

The field list

5 fields · 2 key · 1 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.

Field	Source	Target	Type	Flags	Drift	Validation
Quote id	SBQQ__Quote__c.Id	quoteLine.quoteRef	string(18)	keyinternal	Never checked	Eighteen-character id.
Line number	SBQQ__Number__c	quoteLine.line	integer	keyinternal	Never checked	Positive, unique within the quote.
List price	SBQQ__ListPrice__c	quoteLine.listPrice	decimal(15,2)	internal	Never checked	Positive.
Discount percent	SBQQ__Discount__c	quoteLine.discountPct	decimal(5,2)	nullableinternal	Never checked	Between 0 and 100. Above the band ceiling the line must carry an approval reference or it quarantines.
Approved by	Approval__c.ApproverId	quoteLine.approverHash	string(64)	nullablepersonalconfidential	Never checked	Pseudonymized. This field is the reason the security review is still open.

What has passed the staging boundary against this contract

1 batch · 1,180 arrived · 0 admitted · 1,180 quarantined · 0 rejected

Staging boundary

Batch	Arrived	In	Admitted	Quarantined	Rejected	Result	Gate
STG-0011	Aug 18, 04:00	1,180	0	1,180	0	Nothing admitted	No record cleared the gate. 1,180 are in quarantine and 0 were rejected outright.

Rejects raised against these batches

1 reason covering 1,180 records. Each one names a field, what was observed and what the contract expected.

Document date outside the declared extract window1,180 records · 5 h oldOpen, no owner

Observed: The whole batch sits outside the window because the feed is fourteen minutes past its commitment

Expected: Inside the declared extract window

STG-0011 · field quoteDate · queue quarantine · no owner assigned

Replay windows

1 window recorded against this contract.

Replay register

RPL-015Awaiting approval

Late arriving · Aug 12, 2026 to Aug 17, 2026

The quote feed has been outside its freshness commitment for six days and the missing window has to be re-read before the pricing figures can be trusted.

0 replayed · 0 held at the idempotence key · 0 duplicates created

Write-back routes into this system

No write-back route is designed into this system.

Write-back register

What this contract is, and what it is not

A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.

This contract has never been validated against a sample. Every type, every cardinality statement and every validation rule on this page is a declaration taken from documentation, not an observation. Its drift state is unknown rather than clean.