You have the concept but we aren't clicking on what needs to happen.
This is very close:TRANSFORM Sum(pricing.Price) AS SumOfPrice
SELECT pricing.naive_id
FROM pricing
GROUP BY pricing.naive_id
PIVOT pricing.QTY;
The QTY table is static that is where the values (prices) go 
Your Query looks like this: 
You used the QTY in the pricing table to create the fields, which flattens the data, great but since this data is coming from a web site I have know Idea what quantities there will be, so I need to create a workable range, which is what I did in the QTY Table.
So with your SQL instead of creating the fields "QTY NUMBER" it needs to assess the price that corresponds with the quantity in the pricing table and then put those prices in the QTY table under the appropriate QTY using expressions to determine where the price goes.
For example naive_id 73cd70930b611b2d4fb000e6f61ef626 has a qty of 61,500 and a price of 0.0782, the 61,500 needs to be evaluated and then place the price, 0.0782 in the QTY table under 10,000, I know that doesn't make sense, but it will work because more than likely we will never order 10000, and if that happens we will search the naive_id and check the supplier
This is designed to give a quick look at pricing in a sub form so all the pricing data needs to be in one row.
Please don't give up on me, you have the concept down pat, I am just not explaining it well.