are you saying they may have a different price if they buy by Each vs Case vs Pallet

Yes, for example:

If product.udf_stockbaseprice = 'Y' then stockbaseprice*uomconversionqty
else if account.pricelevel = '1' and unitofmeasure = EACH then stockbaseprice
else if account.pricelevel = '1' and unitofmeasure = INNE then stockbaseprice*(1-.01)*uomconversionqty
else if account.pricelevel = 1'' and unitofmeasure = CASE then stockbaseprice*(1-.03)*uomconversionqty

I mean, I think I have 80% of the script logic done, it's a matter of the objects, getval, retval stuff for Sage I don't understand.

Yes, for example:

If product.udf_stockbaseprice = 'Y' then stockbaseprice*uomconversionqty
else if account.pricelevel = '1' and unitofmeasure = EACH then stockbaseprice
else if account.pricelevel = '1' and unitofmeasure = INNE then stockbaseprice*(1-.01)*uomconversionqty
else if account.pricelevel = 1'' and unitofmeasure = CASE then stockbaseprice*(1-.03)*uomconversionqty

I mean, I think I have 80% of the script logic done, it's a matter of the objects, getval, retval stuff for Sage I don't understand.

I think a Case statement would work better. Wonder what Kevin thinks about using Case instead of Else If

I prefer to manage this type of thing by UDT data instead of hard coded rates within a script (so changes can be made by users with access to the UDT).

Set up a UDT with an appropriate key field like ItemCode^PriceLevel^UoM (with the multiplier as a column in the UDT), then do a line pre-write script to look for a value in the UDT.  When you find a row in the UDT (for the SO line's item / price level / UoM) then get the multiplier and apply it.

(I'm guessing a Case statement might run faster than a significant number of nested If's).

a UDT would be great, but I've never set those up in Sage & I will still be spinning my wheels with a script.

If we setup a UDT, I could sync the values via SQL if they were to ever update (we set them in Salesforce)