What you sell: the jewelry on your dashboard
Choose the jewelry you sell when you send your business details, or later in Settings, What you sell: rings, earrings, pendants, necklaces, bracelets or other pieces. Your dashboard shows the tools for the types you choose, and your plan decides which of them you can use. Until you choose, the dashboard shows rings. Owners and admins can change it, and so can an API key with the account:write scope.
3D Jewelry Designer1 min read
Where you choose
- When you sign up. The business details form asks What do you sell? right after the type of business. It is optional, and our team doesn't review it.
- At any time after. Open Settings → What you sell, tick the types and select Save.
Owners and admins choose. Other members of the team can see the choice.
What it changes
What you choose decides what your dashboard shows. It never changes what you can use: your plan decides that.
- Until you choose, your dashboard shows rings, as it always has.
- Rings stay in the studio and in your ring builders, whatever you choose.
- A store that doesn't sell rings sees Saved design selected first when it creates an embed.
- When you sell more than rings, Leads shows each lead's jewelry type. The
Export CSV file has a
typecolumn for every store.
Under the types, Settings lists the tools for the ones you ticked:
- Ready on your plan: the ring builder and ring try-on, when your plan includes them.
- With an upgrade: the tools your plan doesn't include yet.
- Coming as each goes live: types with no builder or try-on here yet. When one arrives, your dashboard adds a card for it, but only if you chose that type.
On the API
Read what the account sells, and each type's builder and try-on on your plan, with
GET /api/public/account/jewelry-types and a key that has the account:read
scope. Set it with PUT /api/public/account/jewelry-types and a body such as
{ "types": ["ring", "earring"] }, with the account:write scope;
{ "types": null } goes back to rings.
In GraphQL, read organization { jewelryTypes { chosen } } and set it with the
setJewelryTypes mutation. The SDK has account.jewelryTypes.get() and
account.jewelryTypes.set().
Related
- How an integration fits together
From a shopper building a ring to the order in your systems: what runs where, which price to trust, and how products and 3D models stay in step.
- The ring builder's JavaScript SDK
Mount a ring builder on any page with one script, read every selection and add to cart, and size, theme and tear it down from your own code.
- Webhooks: events, payloads and signatures
Send leads, saved designs, carts and orders to your CRM or backend as signed webhooks, and check each delivery with a few lines of code.