Prerequisites:

Pricing trigger configured for family pricing - defined by QL support.
Custom-function configures for leading products - can be coded by QL or the client.

Basic design:

Each product is assigned a role.

The product can be either “leader” or “follower”

The leader is the product on which we base the rest of the product's recommendations.

This is the basic flow for Leader-Follower pricing:

The role is determined by an attribute named “pricing_definition”, containing the role specification.

Followers should be updated with the most recent data before the leaders.

The leader will be updated a few minutes later and will send all of the followers associated with it.

Payload:

All products should receive two additional attributes:

“pricing_definition” - the value will be either “leader” or “follower”
“family_id” - The value will be the unique identifier of the product group.

The leaders should receive one additional attribute on top of the previous two:

“related_products” - The value will be the product IDs of the rest of the products in the group.

Here is an example of the additions to the payload:

Leader:

{"attributes"=>[{"name"=>"pricing_definition", "value"=>"leader"}, {"name"=>"family_id", "value"=>"ABCDEFG"}, {"name"=>"related_products", "value"=>"A123,B123,C123"}_s}]

Follower:

{"attributes"=>[{"name"=>"pricing_definition", "value"=>"follower"}, {"name"=>"family_id", "value"=>"ABCDEFG"}_s}]

Related to

Sending a family of products to pricing via API

Prerequisites:

Basic design:

Payload:

Here is an example of the additions to the payload:

Comments

Prerequisites:

Basic design:

Payload:

Here is an example of the additions to the payload:

Related articles