Inventory

Share a Certificate with a Customer

Text or email a stone's cert PDF to a customer in two taps. Uses your phone's native share sheet — Messages, Mail, WhatsApp, AirDrop, whatever your customer prefers. No app to install, no SMS gateway, no audit trail (yet).

Share a Certificate

The Share button appears next to every certificate in JewelTrak. Use it to send the cert PDF link to a customer in two taps — no email composer, no SMS gateway, no contact list to maintain. Your phone’s own share sheet does the work.

Where the Share button appears

Stone detail pages (/diamonds/[id], /colored-stones/[id], /pearls/[id]) — next to View Certificate PDF in the Certificate panel
Certificate preview modal — opens when you tap a cert thumbnail on a stone list page, the Share button sits next to the close X

The button only renders when a cert PDF is actually attached to the stone.

How it works (on a phone)

Tap Share.
Your phone’s native share sheet slides up — same one you see when sharing a photo from your camera roll.
Pick Messages, Mail, WhatsApp, AirDrop, or any app that accepts links.
Pick the customer’s contact.
Tap Send.

The customer receives:

Certificate 2185476321
Cert for stone #503048 - 3.03ct Round D/SI2
https://storage.jeweltrak.com/.../500346_cert.pdf

Tapping the link opens the PDF in their browser — no JewelTrak account, no login. They can save it, forward it, print it.

How it works (on desktop)

If your browser doesn’t expose a native share sheet (mostly Linux + older Windows browsers), the Share button opens a small menu instead with three options:

Copy link — drops the URL on your clipboard so you can paste it anywhere
Email — opens your default mail app pre-filled with the cert
Open in new tab — opens the cert PDF in a new browser tab

Mac Safari and modern Chrome support the native share sheet on desktop too, so the menu only appears as a fallback.

Why this beats SMS automation

A common question is “why don’t you use Twilio?” — the short answer is deliverability. Texts sent from your own phone number (P2P) land directly in the customer’s Messages app like any other personal text. Texts sent from a Twilio business number (A2P) go through carrier filtering with mandatory 10DLC registration in the US since 2023; new business numbers often start with “Likely scam” labels until reputation builds, and many recipients block unknown numbers entirely.

The share-sheet path:

Goes from your number (the customer already trusts)
Has no registration cost or compliance burden
Has no per-message fee
The customer can reply directly to you

The tradeoff is no audit log inside JewelTrak (we don’t know what you texted to whom) and no automation (you can’t schedule “auto-text every cert nightly”). If those become important, layered automation can come later — but the manual path covers the field-jeweler use case completely.

Privacy

The cert link is public — anyone with the URL can view the PDF. That’s how the existing legacy S3 + R2 buckets work today, and it’s what lets the recipient open it without an account. If you don’t want a cert to be world-readable, don’t share the link.