I would suggest using the FIND-ALL operator to sort only the ids that have a price. I don’t know the back end programming for RTML, but FIND-ALL should be a O(n) operation at the most. Thus cutting out undesirable ids from your sequence first should have the additional benefit of shaving a bit of overhead off the sort as well.

Also, using the REVERSE operator will certainly work, but why run an additional operation on the list? Sheridan’s solution is more proper.

I also found — looking through the various RTML tags — that if you put the REVERSE tag on the INDEXED-SORT, you get the reverse sort order.

One other question:
When I use the sort-item-by-price template, can I ask the INDEXED-SORT to exclude all ids without prices?

Right now, if I reverse the sort by price, so highest to lowest, it lists all ids without price first.

Of course, if sort by price, lowest to highest, all ids without price appear at the end of the list.

One final off-topic question:
Is there any easy RTML way to paginate section pages, say 12 or 15 items per page?

Thanks again for the help.

How can the sort-item-by-price template be tweaked to sort price from highest-to-lowest (it defaults as lowest to highest)?

Thanks for the help.