Happy to be wrong, but that's quickly going to get unmanageable

Yes its bad design

Yes a MR script is not a good fit

the problem is the bad design is NS itself and the MR is not a good fit simply because NS lacks a option that can satisfy the requirements in a scalable method

I need to be able to update pricing on ~1.5M items on a schedule basis, our pricing model is complex in terms of what NS can handle.

It is not possible to load a search across ~1.5M products without timing out a MR script

Therefore the only solution is to segment the MR in separate deployments based on preferred vendor.

We have tried the approach of doing a triggered updated based upon field change, but when your trying to do this across 50k-100k product updates at a time the file import approach slows to a dead crawl and will take days to complete.

So back to my original question, is there any approach to creating these is some automated fashion?