The most likely theory I can think of is that the printer is using cp437, as you say, and also the POS software is correctly written and is sending cp437 for the bits it controls… including 0x9C for ‘£’ in the price column.

But the cocktail description isn’t managed by the POS, it’s managed by some sort of product database, which is stored as ISO-8859-1 (or, more likely, as Win1252), and then the POS is pulling those descriptions out of the DB and sending them along untranslated.

That’s where the encoding error happens… the POS is treating the product DB as cp437, but the management software is treating it as cp1252. Likely, the two are made by different companies, so there’s probably endless specs somewhere that would tell you who was right… and if you locked the two comapnies’ lawyers in a room with a tarp and a straight razor you’d probably eventually get an answer as to who that is… but without that it’s not particularly obvious who’s to blame, other than “every programmer who allowed this encoding problem to continue”.