Bespoke Jewellery Websites: From Customer Enquiry to Quote, Design Approval & Deposit

Why Custom Orders Need a Different Journey

A ready-made necklace can often be purchased from a product page. A commissioned ring may require a conversation about proportions, materials, stone choices, budget and timing before a jeweller can price it. Forcing both experiences into the same checkout creates uncertainty for customers and staff.

The goal is to make a custom process understandable without pretending that design decisions are automatic. This article proposes a practical workflow for a bespoke jewellery website. It does not assume your workshop needs a 3D configurator or that every enquiry should become an immediate online payment.

Our existing Birmingham jewellery website guide covers broader product content and shopping journeys. Here, the focus is the handoff from a custom request to an approved, traceable production brief.

1. Explain the Process Before Asking for Details

Show a short sequence near the enquiry button: tell us your idea, discuss feasibility, receive a proposal, review the design and confirm production. Match that sequence to the workshop's actual process. If a consultation or design stage has a fee, explain it before a customer spends time completing the form.

Distinguish an indicative budget discussion from a binding proposal. Customers should know whether an initial figure includes the stone, setting, engraving, shipping or further revisions. Do not present a starting price as a finished quote when important choices remain unresolved.

Use representative examples to explain the range of work you accept. Label concept illustrations and completed commissions accurately. Obtain permission before showing identifiable customer stories, private messages or photographs supplied during an enquiry.

2. Collect a Useful First Brief

Start with contact details, jewellery type, a description of the idea and the desired date. A budget range and material preference can help assess feasibility, but allow unsure as an answer. A customer seeking advice should not have to choose a technical specification before speaking to the workshop.

Reference uploads can be useful, provided accepted file types, size limits and upload errors are clear. Explain that inspiration images guide the discussion and do not promise permission to reproduce another designer's work. Offer a text-only route for people who cannot upload a file.

Follow the practical principles in W3C's forms tutorial: label controls, explain required information and provide understandable feedback. On a phone, test long notes, an interrupted upload and a corrected email address. Save the enquiry before relying on an email notification.

3. Use Stages That Staff Can Act On

A workable internal sequence might be new enquiry, awaiting information, consultation arranged, quote prepared, quote accepted, design under review, design approved, deposit confirmed and in production. These are recommended examples, not a mandatory software standard. Remove stages your business does not use.

Every open request needs an owner and a next action. A status such as pending means little if nobody knows whether the customer, designer or accounts team must act. Record the last contact and make stalled requests easy to find without exposing private customer details to unnecessary users.

Send customers a plain confirmation with a reference number and a realistic next step. Only promise a response time the team can consistently meet. Avoid saying that a successful enquiry guarantees availability for a particular occasion.

4. Turn the Quote into a Versioned Proposal

A proposal should identify the commission, material assumptions, stone specification where applicable, included work, estimated timing and price currency. Record what remains subject to confirmation. If a supplied stone needs inspection, explain that dependency before presenting a final production commitment.

Give each proposal a revision identifier and issue date. When a customer changes the design, generate a new version rather than silently editing the document they previously accepted. Keep an accessible summary of what changed, particularly if the price, delivery expectation or included revisions changes.

An illustrative version sequence is quote Q104-A for the original concept and Q104-B for a revised setting. The website should identify which version the customer accepted and prevent an expired or superseded proposal from being treated as the current instruction.

5. Separate Design Feedback from Final Approval

A design-review screen can show reference views, measurements, material notes and outstanding questions. Clearly label which images are renders or sketches. Display variations that matter to the approval rather than overwhelming the customer with indistinguishable attachments.

Let a customer request a change without accidentally approving production. Separate request changes and approve this version into clearly explained actions. Where measurements or visual proportions are important, give customers a readable confirmation summary and access to workshop guidance.

Record the approved design version, approval time and relevant customer acknowledgement. This supports a shared project record; it does not replace properly reviewed business terms. If the workshop makes a material change afterward, return the affected details for review instead of assuming an earlier approval covers everything.

6. Connect Payments to the Agreed Milestone

Define when a design fee, deposit or final balance becomes due. A quote acceptance and a cleared payment are separate events. Production should move forward according to the workshop's approved rules, including how delayed or failed payments are handled.

Use the payment provider's hosted or approved collection flow rather than asking customers to email card details. Identify the quote and commission associated with each request. When a customer retries a payment, staff should be able to determine whether the original attempt succeeded before creating another request.

Describe any payment schedule, cancellation handling and scope-change process in customer-facing terms reviewed for your business and jurisdiction. This article does not prescribe a universal deposit percentage or refund rule. Those choices depend on the commercial arrangement and applicable requirements.

7. Give Customers Visibility Without Overbuilding a Portal

For a small workshop, secure links to the current proposal and design review may be sufficient. A full customer account can be useful if people need ongoing access to several commissions, invoices and delivery updates. Decide based on the workflow rather than adding accounts by default.

Use access controls and an appropriate expiry or reauthentication process for sensitive documents. Reference images, addresses and private commission notes should not become public attachments discoverable through a predictable URL. Define retention and deletion practices with the business owner.

A useful customer summary contains the current stage, what the workshop is waiting for, the accepted proposal and the next expected update. Do not expose internal speculation, supplier discussions or other customers' records through a shared project view.

8. Test the Exceptions Before Launch

Walk through an enquiry with an unsupported attachment, a revised quote after acceptance, a requested design change, a failed deposit and a customer who returns to an old link. Confirm that the correct version remains visible and production cannot be triggered by an obsolete approval.

Also test staff absence. Another authorised person should be able to understand a commission without searching someone's personal inbox. Confirm that notifications reach the intended recipient and that the original request remains stored if email delivery is delayed.

Measure time to first useful response, quotes awaiting a decision and revision loops that require clarification. Use those findings to improve instructions and handoffs. A polished approval screen cannot compensate for an unclear workshop process.

Frequently Asked Questions

Does a bespoke jewellery website need a live price calculator?

Not always. If feasibility, stone availability or workshop assessment affects the price, a structured enquiry and reviewed proposal may be more accurate. A calculator is useful only when its assumptions are reliable and clearly explained.

Can customers approve designs online?

Yes, a website can record approval of a specific version and keep a project history. Decide which details need acknowledgement and have the business review its approval terms before launch.

Should I ask for ring size in the first form?

Only if it is useful at that stage. Allow customers to say they need help, and provide the workshop’s measuring guidance. An unverified size should not silently become a final production specification.

Is a customer portal essential at launch?

No. Secure review links and a well-managed internal workflow can be enough initially. Add accounts when repeated commissions, document access or ongoing status updates justify the extra complexity.

Plan Your Next Step

For a broader store project, explore Birmingham ecommerce development. For a custom-order workflow, send an anonymised example of how your team currently handles a commission.