Hello,
I thought that uStore 25.3 (and older versions) was simply mimicking the uProduce Job Ticket of the uProduce Job, which is referred to when you create of modify a uStore Product in uStore Admin.
So obviously, if the "template" uProduce Job was processed with the "Compression > Compress Output (ZIP)" option enabled (with versions older than 25.2) or a "Compress" Post Composition Operation (from version 25.2), then it would make sense that uStore serves a zipped file.
Now, you said that it's not zipped with JPEG, whereas it is with PNG, so certainly you did not jump into such an easy trap.
May I ask, if your document / data were exactly the same, between the JPEG composition and the PNG composition?
I'm asking this, because you wrote "the image in JPG"... as if there was only one JPEG, because your document had only one page and there was only one recipient.
Could you elaborate, on what are the several PNG files in the unexpected ZIP? Has the template document several pages? Or are there more than one recipient in this PNG composition? That you had not in the JPEG production?
Anyhow, I'm also wondering something else: regardless the number of pages in the XLIM / INDD document and the number of recipients, what do we expect from the uStore "OrderOutputProxy.ashx" service, when several production files have to be served to the User's web browser? Regardless it's JPEG or PNG or - why not - a "Separate file for each record" PDF composition. Maybe is there something smart in this service, that forces the uProduce job to compress, as soon as there are several files? So that the web browser does not complain or warn that there are several files to download simultaneously?
I could not test immedialy, due to a temporary lack of license on our server.