ElanoryaSellers of sized pieces
Selling sized pieces when the frame cannot carry the size
Fit is the part of a jewelry listing that has to be settled before the order rather than after it. A photograph can show placement and drape; it cannot state a measurement. When the strongest image in the set is a generated on-model frame, that gap is wider than it looks, because the frame was produced from an instruction that never referred to the buyer at all.
What an on-model frame answers
Most of what a jewelry listing sells can be judged from a picture. Colour, finish, proportion against a hand, how a chain falls — a buyer forms a reasonable opinion from the images alone. Fit is the exception. It is a question with a single correct answer, it has to be answered before the order rather than after it, and no photograph has ever answered it.
A generated on-model result makes that easier to forget. The request behind it names a body region and a way of wearing the piece. It does not name a finger size, a wrist measurement or a chain length, and nothing comes back carrying one. What returns is placement and drape: useful, and about a different question.
So the working split for a sized piece is simple. The result answers how the piece sits. Everything about how large it is has to be routed somewhere else — and the rest of this page is about where.
The close frame is the one to watch
This site's guide on mixing real and generated photos owns the mechanism, and it is worth stating once rather than rebuilding: the app works by category, the category decides the body region, and close framing is instructed for rings and bracelets only. The bracelet page adds the wording of that instruction, which asks for the piece around the wrist rather than on it — again a placement, and again not a measurement.
The consequence for a seller of sized pieces runs against intuition. A wide result invites nobody to estimate a measurement from it; the piece is small in the frame and clearly there to be seen in context. A close result looks like the opposite. It fills the frame, it sits against a hand or a wrist, and it presents itself as the image where scale is finally visible. It is not. How large the piece appears there is a property of the rule that framed it.
That is why the close-framed result is the expensive one to publish without a stated measurement: it is the frame that offers itself as evidence of scale, and the frame with nothing to say on the subject. Rings and bracelets are also the two categories where fit is decided by a single figure rather than by preference, which is exactly the figure the picture cannot supply.
Where the size has to live instead
Size lives in text, and specifically in the text a buyer cannot skip. An option or variant name is passed through on the way to the order. A title is read before anything is opened. A measurement block in the description is read by the buyer who was already going to ask. Ranked that way, the description body is the weakest of the three places to put the only figure that decides whether the piece can be worn.
For chains this is not a preference. The necklace page owns the point that length is a property of your piece rather than a setting in the app, which means there is nothing in the flow that could ever state it for you. The same holds for a bangle's inner measurement and a ring's size: the app has no field for them, produces no statement about them, and does not ask.
Nor is there anything downstream that would carry them across. The app has no connection to any shop or marketplace — no integration, no export, no sync. Whatever size field your channel offers is filled in by hand, in that channel's own listing form, in a step the app takes no part in. Treat that step as part of preparing the images rather than as something that happens afterwards, because it is the step that carries the product.
The generated frame still has a place in the set beside it. The mixing guide covers how the slots in a set get assigned when real and generated images sit together; the only rule this page adds is that the measurement slot is never the generated one.
Where the text and the picture stop matching
There is one place in the app where preservation becomes something you can withdraw. The image edit tool carries a switch for product detail and a switch for person identity. Both start on, either can be turned off, and with a switch on an extra line goes into the request. With it off, that line is simply not there. Everywhere else in the product, preservation is instructed on your behalf; here it is a default you can reverse.
For a sized piece that is a real decision rather than a setting. Band width, link size, the shape of a clasp — these are the details a buyer reads against the figure you wrote in the option name. If the product-detail switch was off for a round trip, the size sentence and the published file were checked at different moments, and only one of them was checked against the piece.
If a result comes back changed enough that it no longer matches what you wrote, the result screen carries a report path, and one of its named reasons is that the product changed. That is the route for it. Publishing the file and handling the difference in messages afterwards moves a picture problem into a fit complaint, which is the more expensive of the two.
Before the listing goes up
Only the last of these is about an image.
- The measurement appears in a field the buyer passes through, not only in the description body.
- For a chain, the length is in the option name, because nothing in the flow states it.
- An adjustable closure is described from the piece in your hand, not from the result.
- Any result edited with the product-detail switch off has been re-read against the size sentence.
- No line in the listing text invites the buyer to judge scale from a generated frame.
What this page does not cover
- How to measure. Finger, wrist and chain measurement methods are outside what this site has sources for, and no figures appear here for that reason.
- Earrings. They are one of the app's categories, but the instruction that governs them concerns whether a single piece or a pair is kept, which is a different problem from fit.
- Channel size fields. Every marketplace and store platform names its size, option and variant fields differently, and the app connects to none of them — there is no integration, no export and no sync.
- What a result will look like. Preservation of detail, openings, links and closures is instructed; instruction is not a guarantee, and nothing here promises an outcome.
Questions
How do I show ring size in a photo when the hand in the photo is generated?
You do not show it — you state it. The request behind an on-model result names a body region and a way of wearing the piece, never a measurement, so nothing comes back that can stand as a size. Put the figure in the option name and the title, and let the result do the job it can do, which is showing how the piece sits.
Is there a scale or sizing setting in the app?
No. Nothing in the flow sets how large a piece appears; the framing follows the category, and no framing or background choice is presented to you along the way. For chains this is stated most plainly on the necklace page: length is a property of your piece rather than a setting.
Do I still need a real photograph with a measuring reference?
Yes, and it belongs in the same set. A listing's images are read together, and the mixing guide covers how the slots get assigned when real and generated images sit side by side. The rule this page adds is narrow: the measurement slot is never the generated frame.
What if a result no longer matches the size I wrote?
Do not publish it. The result screen carries a report path with a named reason for the product having changed, and that is the route for it. It is also worth checking whether the file came from an edit round trip with the product-detail switch turned off, since that switch starts on and can be reversed.