JCirocco - out of curiosity - do you have a method of creating such a search where it wouldn't send the email for every transaction once the item is below reorder point? That may not be relevant for what David is after but I'd be interested to see how to do this where its 1 email per out of stock instance, if you know what…

I reject! Too simple! :) Nah that sounds like it would work just fine, thanks. Pretty straightforward to add in the rest of the calculations to get the need comparison value for reorder point (committed, bo, etc).

We have a mass update that goes through and sets a custom 'Available' check box each morning. Then, a scheduled workflow is running throughout the day (every 15 min) and sending emails for any item that is no longer available (and unchecking the box). So not quite live but good enough for our purposes and you could try…

Also helpful to use a formula criteria using w/ NVL({quantity},0) function in many scenarios. 

Not sure if you can do this via workflow, but you can use a user event script (its beforeSubmit so doesn't actually set it until you save the record). function isResidential(type) {if (type == 'create' || type == 'edit'); { if(nlapiGetFieldValue('shipisresidential') == 'T'){ nlapiSetFieldValue('custbody119','T'); }…

I don't believe you can take an action regarding sublists (items) via a workflow. This is pretty easily done with a client script, and I'd think similar examples are probably listed in the help documentation if you want to attempt some scripting...