How to use bundle and component attributes in a Revenue Cloud Pricing Procedure?

Hi everyone, 

I'm currently working on a Salesforce Revenue Cloud implementation and would appreciate some guidance on a pricing scenario. 

Business Scenario

We sell telecommunications service bundles.

For example:

Parent Product

• Internet Service Bundle

Component(Child product)

• Router

During product configuration, the user selects different attributes.

Bundle attributes (Parent)

• Bandwidth (20 Mbps, 50 Mbps, 100 Mbps, etc.)
• Contract Term (12, 24, and 36 months)

Component attribute (Child)

• Router Model (FortiGate 40F, FortiGate 60F, etc.)

These attributes impact the service price.

Requirement

The customer wants to manage pricing without having to update Product records every time a price changes.

As an initial approach, I created a custom Price Table object that stores information such as:

• Product
• Selling Model
• Bandwidth
• Contract Term
• Router Model
• Monthly Recurring Charge (MRC)
• Non-Recurring Charge (NRC)
• Effective Start Date
• Effective End Date

My idea was to use this table together with Lookup Tables and a Pricing Procedure to retrieve the correct MRC and NRC based on the selected combination of attributes.

Where I'm blocked

The part I'm struggling with is building the Pricing Procedure when the price depends on attributes coming from different levels of the product configuration.

For example:

• The Bandwidth attribute belongs to the parent bundle.
• The Contract Term attribute also belongs to the parent bundle.
• The Router Model attribute belongs to a child component within the bundle.

I need to use the combination of these attributes to retrieve a single price from my Price Table.

My questions are:

• What is the recommended way to access both bundle attributes and child component attributes within a Pricing Procedure?
• Is it possible to expose those attribute values through the Pricing Context or SalesTransactionItem so they can be used in a Lookup Table?
• How have you implemented similar scenarios where pricing depends on attributes distributed across both the bundle and its child components?

If anyone has implemented a similar solution using Context Definitions, Pricing Procedures, or Lookup Tables, I would really appreciate any guidance, examples, or best practices you can share. 

Thank you in advance!