Pricing rules in Logik Or ServiceNow

snehapatel · 55m ago

Hi,

ServiceNow CPQ(logik) is capable of handling different pricing rules - base product pricing, attribute-based pricing, bundle pricing, configuration dependent pricing etc.

Now, ServiceNow Product & Pricing Rules application is also capable of handling different pricing rules - customer type, sales channel, region, product configuration, bundles, non-product attributes etc.

For a ServiceNow SOM + Logik.ai implementation, what is the recommended implementation best practice for the placement of pricing logic - which rules should be in CPQ and which rules should be in ServiceNow SOM

Thanks,

Sneha

sachinvic · 10m ago

@snehapatel

Hi Sneha,

For a SOM + Logik.ai implementation, it is better to keep the pricing decision in CPQ and avoid duplicating the same pricing rules in SOM.

A practical split would be:

CPQ / Logik.ai

Base/product pricing
Attribute/configuration-based pricing
Bundle pricing
Volume/tier pricing
Customer/segment-specific pricing
Region/channel-specific pricing
Contract or quote-specific discounts

SOM

Use the price returned from CPQ during the quote/order process.
Keep SOM focused on order capture, order management, decomposition, orchestration and fulfillment, rather than maintaining a second pricing engine.
Any downstream adjustments that are strictly related to fulfillment/order processing can remain in SOM.

The main principle is “price once, consume downstream.” Avoid maintaining the same pricing rule in both CPQ and SOM, otherwise the two systems can produce different prices over time.

This also aligns with ServiceNow's current positioning of CPQ as the capability for configuration and dynamic pricing, while SOM connects the quote/order through fulfillment.

CPQ / Logik.ai >> Calculate & finalize price >> SOM >> Capture & fulfill order

FYR: https://www.servicenow.com/products/cpq.html