Photography guide
Sequencing photo edits for a product catalogue
The same two edits, run in the opposite order, do not produce the same file. One order leaves your options open; the other removes information the later step needed. This page sets out which edits are reductions, why reductions belong at the end of the sequence, and where an app that returns a fixed-size result sits in the order.
The same edits in a different order are not the same file
Editing a catalogue photograph is a short list of operations: check the result, remove the background, set the framing, reduce the size, flatten where a destination requires it. Written out like that, the list looks like a set of independent tasks that could be done in any convenient order.
It is not. Two of those operations read information that another one of them removes. Run them one way and each step has what it needs; run them the other way and a step arrives to find that what it was going to work from is already gone. The file that comes out is not a slightly worse version of the same thing — it is a different result, produced by the same instructions.
That is the practical reason to fix an order once and then stop deciding it per image. The order is not a preference about workflow tidiness. It follows from which steps subtract.
Which steps subtract, and why they belong at the end
Sort the operations into two groups. In the first group are steps that change what the file describes while keeping the material to work from: a crop decision, a background removal, a correction judged against the full-size image. In the second group are the reductions — making the picture smaller, and replacing transparency with a colour. A reduction leaves the file holding less than it held before, and no later step restores it.
Once the list is sorted that way, the sequence follows on its own: everything in the first group runs while the file is still complete, and the second group runs at the end, on copies, as late as the destination allows. This is the same principle as keeping a source and making renditions from it, which the multi-channel page sets out; the sequencing view simply says which individual steps are the renditions.
The cutout is the clearest case. Removing a background is a decision about the boundary between the piece and everything behind it, and jewelry has the least forgiving boundary of any product category: open links, prongs, a clasp with a gap in it, a chain that is mostly edge. Reduce first and that boundary has already been coarsened before the step that depends on it runs. Remove the background first and the reduction afterwards is only a reduction — the boundary decision has already been made from the complete file.
Where transparency enters, and where it has to end
The background remover returns transparency by design, which the multi-channel page explains along with why that single file receives different verdicts at different destinations. What matters for sequencing is narrower: transparency is a state the file can be in, and flattening is the step that leaves it permanently.
So transparency should enter the sequence early, at the cutout, and end as late as possible — after the framing decision, after the size reduction, on a copy made for the one destination that requires it. Etsy does not support transparent PNGs and transparent areas appear black there, and the Etsy page carries what that means for what you upload. Treat that as a rendition requirement rather than as a property of your source file.
The failure this avoids is quiet. A flattened file looks correct, opens correctly, and uploads correctly. Nothing announces that the transparency is gone. It only becomes apparent later, when a second destination needs the cutout and the only remaining file has a background permanently attached to it.
The sequence, from result to upload
Seven steps, in this order. The last two are the reductions, and they are last for that reason.
- Compare the result against the real piece at full size: pair counts, openings, links, closures, stone count, metal colour.
- If the piece itself came back altered, use the report control rather than starting to edit.
- Make any correction that has to be judged against the complete file while the file is still complete.
- Remove the background here, before anything has been made smaller.
- Decide the framing and the aspect ratio once, for the whole set rather than per image.
- Save that transparent, full-size version as your source and make every following file as a copy of it.
- Reduce the size per destination, then flatten only for the destinations that require it.
Where the app sits in the order
The app occupies one position in this sequence: it produces the result you begin from. It does not render a picker for output size, background or aspect ratio, and the result arrives at a fixed size rather than one you select. Framing, resizing and flattening are therefore steps you run afterwards in your own editor, and there is no per-destination export inside the app to run them for you.
This makes the first step of the sequence a check rather than an edit. The prompt instructs the model to preserve mirrored and duplicated elements and to keep openings, links and closures as they are — earrings are instructed to hold their pair, and openings are instructed to stay open. Instructed is not the same as guaranteed, which is why the comparison against the real piece happens before any editing, while the evidence is still at full size and while the report control is still the appropriate response.
What this page does not cover
- Anything before the file exists. Lighting, framing and the shooting order for each category belong to the per-category guides, and this page starts after the result is in front of you.
- The specific rules of any destination. Accepted formats, size expectations and transparency rules live on the marketplace pages, which carry them with the sources they come from.
- Numbers. No pixel dimensions, file sizes or percentages appear here, because this page does not interpolate marketplace values.
- How the background removal or the generation reaches its result. This page treats both as steps with inputs and outputs, and makes no claim about what happens inside them.
- Any claim that a particular order performs better commercially. The argument here is about what information survives each step, and nothing more.
Questions
Should I resize a photo before or after removing the background?
Remove the background first. The cutout is a decision about the boundary between the piece and what is behind it, and reducing the file first coarsens that boundary before the step that depends on it runs. Resizing afterwards is only a reduction, applied to a decision that has already been made from the complete file.
Does it matter whether I flatten a transparent image before or after resizing?
Yes. Flattening replaces transparency with a colour and cannot be reversed, so it belongs at the very end, on a copy made for the destination that requires it. Flatten before resizing and you have attached a background permanently to the file you were still going to work on.
Can I prepare one edited file and use it everywhere?
Not reliably, because destinations do not agree about transparency — the multi-channel page documents where the conflict is. Keep the transparent, full-size version as your source and produce a separate rendition for each destination. There is no per-destination export inside the app to do this step for you.
Where does the app fit into this order?
It produces the result you start from, at a fixed size, with no rendered picker for size, background or aspect ratio. So your sequence begins with a comparison against the real piece — pair counts, openings, links, closures, stone count, metal colour — and if the piece came back altered, the result screen carries a report control for that instead.