A photo shoot ordered for the front of a product could come back rendered from the back. It happened whenever a product had an approved packshot for more than one of its photos — which is the normal state once you have used "Use original" or "Upload your own" for both a front and a back photo.
The cause was in how the shoot chose its source. It resolved the product from the photo you picked and then took the product's most recently approved packshot, whichever photo that belonged to. The side you asked for played no part in that choice, and the model rendered the packshot it was handed faithfully. A product with only one packshot was unaffected, which is why this was easy to miss.
The shoot now uses the packshot of the photo you picked. Nothing else about ordering one changes.
A photo without an approved packshot of its own is refused instead of substituted. You are told which photo needs a packshot, and no credits are reserved. Previously the platform quietly used another photo's packshot, which is what produced the wrong side.
The product card now lets you choose the source photo. Opening the shoot configuration from a product shows the product's photos that have an approved packshot, with a front photo selected for you when the product has one. Until now the product card picked the most recently uploaded eligible photo and offered no way to say otherwise, so a merchant working from the card could not order the front once a back photo existed.
The source shown beside a finished image is the packshot that image was made from. It used to be re-derived from the product, so for a product with packshots of several photos it could show a source that had nothing to do with the picture beside it.
Integrations calling POST /api/external/image-picker/register-ideas should know that config.product.id names a product photo and now decides which side is photographed. A photo with no approved packshot of its own is answered 422 rather than being served from another photo's packshot. The API reference has the details.