BDS0.1

Offer in CRM

Local use of Offer (mirror) in the CRM.

Reviewed 2026-10-28Markdown

An Offer belongs to Products & Services. CRM selects it through Deal.Product*. Read the Product°, Price*, Price Currency*, Unit*, seller, validity and lifecycle before proposing. Value* on Deal is negotiated locally; changing it does not change the Offer. Deals (Proposed) is the local inverse.

An active-looking catalog row is not proof of commercial availability: inspect dates and Offer Check. The full Products & Services system is not documented here. Correct catalog facts at that source; this page covers consumption only.

Local usage

Field Storage Current configuration
Deals (Proposed) Linked records Deal; Multiple-record picker
Tags Linked records Tags; Multiple-record picker

Tags was added on 2026-10-22 by the Universal Tags rollout. It is an optional local classification from the shared catalog; it does not grant access, create tasks, change status or enroll a campaign, and it never writes back to the source.

Maintenance

Correct shared facts at their owning source and local links in CRM. A table name or field description alone does not verify sync direction, field mapping, refresh interval or API write support. Campaign has a separately verified contract; do not generalize it to the other mirrors.

Domain boundaries · All entities