We have run into this same problem. The way we got around this problem was by by moving the RemoveExistingProducts standard Action to before the costInitialize action (we normally set ours to 790 to accomplish this).A couple things to remember here....
MichaelU wrote:It is possible in the Premier edition, but undocumented. By looking at the provided themes it shouldn't be to hard to figure out what to do (the current capabilities are not very extensive), but we've not yet made any forwards compatib...