Which Pricing Procedure is used on Quote? What is the basis of the decision?

When refreshing Developer sandboxes, core configuration data like Products, Catalogs, Attributes, Price Books, and Price Rules do not automatically carry over. To seed this data efficiently, you should use data migration tools like Data Loader, SFDX data CLI commands, or specialized CPQ data migration utilities. To preserve parent-child relationships and avoid duplicate keys, maintain consistent External IDs across environments for all catalog and pricing records before performing bulk data inserts. 

For your deployment workflow from Dev to downstream environments, split your tasks cleanly between metadata and configuration data. Use VS Code and your metadata pipeline to deploy Context Definitions, Expression Sets, and Decision Tables, while using data migration or integration tools (such as Dell Boomi or data loaders) for price books and pricing rules. Follow a strict deployment sequence by deploying metadata components first, followed by your pricing and catalog data records. 

Finally, execute the necessary post-deployment steps to prevent runtime errors like "Price Not Found." You must refresh Decision Tables, synchronize pricing data, and rebuild Product Indexes in the target environment so that runtime calculations resolve correctly against the newly deployed context definitions and catalog hierarchies.