Elanorya

Gemstone dealers

A loose stone has no body region

If what you sell is the stone itself, one half of this app was not written for your catalogue. That is worth knowing in one page rather than after a dozen attempts, and it also decides which half is still useful to you and what you have to check before anything gets published.

The app places pieces on people, and a stone is not placed anywhere

Everything on the on-model side of this app is written one category at a time: rings, bracelets, necklaces and earrings. Each of those instructions names a body region, because placing a piece on a person requires knowing where it goes. The listing guide on this site sets out that mechanism in full, and nothing about it changes here.

What changes is the catalogue. A dealer selling loose stones has a product that is not worn at all, so the question the instruction is built around does not apply to it. This is why the honest answer to a gemstone dealer is a boundary rather than a workaround: there is no category to select, and selecting one anyway does not create a placement that makes sense for the item.

The boundary moves as soon as the stone is set. A stone in a ring is a ring, a stone in a pendant is a necklace, and from there the ordinary category behaviour applies. Until then, the part of the app that is still yours is the other one.

The editing tool, and the two switches that matter here

The editing tool starts from a photograph you already have rather than from a category. That is what makes it the applicable half for this catalogue: your stone photograph is the input, and the work is done to that image.

It carries two switches, and both are on when you arrive. One asks that the product's detail be kept, the other that a person's identity be kept. While a switch is on, the request sent from the app carries an extra line asking for that. Both can be turned off.

That detail is worth pausing on, because it is unusual. Elsewhere in the product, preservation is part of the instruction and not something a user chooses. Here it is a default that can be reversed, and the switch a stone dealer would be most tempted to reverse is the one about product detail. A cleaner-looking result obtained that way was obtained by removing the request that the stone be kept as it is.

Instructed, not guaranteed — and stone count has its own line

Everything above is a request made of the model, not a promise about the result. The vintage sellers page explains why that gap is expensive when the product's own detail is what the buyer is paying for, and a loose stone sits in exactly that position: there is no other subject in the frame to carry the listing.

The result screen has a live report path, and among the reasons it lists is that the stone count changed. Read that as information rather than as reassurance. The product names this as a way a result can differ from the source, which tells you what to compare when you check a result and what to do with one that fails the comparison.

There is also nothing to adjust after the fact inside the app. The result arrives at a fixed size, and no resolution, background or aspect-ratio control is shown. So if a sales channel states a size it wants, that comparison happens outside this app.

Before a generated image of a stone reaches a listing

Five checks. The first two are the ones specific to selling stones.

  • The number of stones in the result matches the number in your own photograph, checked at full size.
  • The product-detail switch was on for the whole edit.
  • Your unedited photograph is still in the set, carrying anything the description asks a buyer to verify.
  • Nothing written in the description depends on something visible only in the generated image.
  • A result that changed the product goes to the report path on the result screen rather than into the listing.

What this page does not cover

  • Anything about the stone itself. Identification, cut, colour and clarity are outside what this site has sources for, and nothing here should be read as a claim about them.
  • There is no integration with any sales channel. No marketplace is connected to this app, nothing is exported automatically, and nothing is kept in sync. Every file moves by hand.
  • Size requirements and file rules stated by individual channels, which the channel pages carry. No figures appear here.
  • How each wearable category behaves, which belongs to the category pages rather than to a page about a catalogue that has no category.
  • What a result will look like. Preservation is instructed, and this page makes no promise about output quality.

Questions

Which part of this app applies if I sell loose stones rather than finished jewelry?

The editing tool, which starts from a photograph you already have. The on-model side does not apply, because it is written per wearable category and every one of those categories names a place on the body. A stone on its own is not worn, so no instruction there has anywhere to put it.

Why is there no gemstone category?

Because the categories exist to decide a body region — hand, wrist, neck, ear — and that decision has no answer for an item that is not worn. It is a scope boundary rather than a setting that has yet to be added. If the stone is set into a piece, the piece has a category and the ordinary behaviour applies from there.

Should I turn the preservation switches off?

Not for this catalogue. Both start on, and while one is on the request carries an extra line asking for that thing to be kept. Turning off the product-detail switch does not make the result more careful with your stone; it removes the line that asked for it. What is left is instructed, not guaranteed.

What should I do if the result shows a different number of stones?

Keep it out of the listing, and use the report path on the result screen — stone count is one of the reasons named there. Comparing the result against your own photograph at full size, before anything is published, is the check that catches it.