Context variables provide the business data that pricing and configuration rules need to evaluate a transaction, such as the shipping country, currency, or customer tier. Before this data can be used in rules, the context variable definition must be available in the rules engine. Syncing a context variable to CPQ publishes its definition, including its type, mapping, and whether it applies at the transaction header or line level to the rules engine, where you can reference it directly in blueprint rules without writing scripts.

Administrators can sync context variables to CPQ, if not already. Context variables are synced automatically when newly created or updated. Existing context variables that are not synced can be synced manually.