Your storefront on Nexpura

Quick reference

• Your storefront lives at your-slug.nexpura.com — the subdomain you picked at signup. The root URL renders the home page; sub-routes render catalogue, appointments, repair enquiry, contact, and the tracking entry.
• Customer-facing surfaces under the subdomain: / (home), /catalogue (browse inventory), /catalogue/[itemId] (item detail with enquiry form), /appointments (consultation booking), /repairs (repair enquiry form), /enquiry (general contact), /track (tenant-scoped tracking entry).
• Catalogue items render from inventory rows where is_published = true, status = active, and quantity is greater than zero. Filtering by category, metal type, or stone type uses the same structured fields you set on the inventory row.
• Submitted enquiries (from any of the three forms) land in the jeweller-side /enquiries inbox. The conversion flow — turning an enquiry into a customer plus a repair / quote / sale — is covered on the Receiving web enquiries page.
• The storefront is a lead-capture and catalogue surface, not a checkout. Sales flow through your connected Shopify or WooCommerce store, not through the subdomain. The honest disclosure below names what is and isn't built today.

What your customer walks through

1. Home page

The root URL of your subdomain (your-slug.nexpura.com/) renders either a template-driven home page (if you applied a Phase 1 website template through the website builder) or the legacy hardcoded layout (the fallback when no template is published).

Both versions show: your business name, your tagline if set, a hero image if uploaded, a featured-collection strip (up to eight published items pulled from inventory, ordered by recency), an About section if you filled in the about-text field, a Visit Us block with address / phone / email if those are set, and a footer with your social links if you configured them. The template-driven version composes the same content into configurable sections; the legacy version is the hardcoded template the early storefronts use.

Customers arrive at the home page from a Google search for your business, a direct URL share, a QR code on printed marketing, or a link from your main website if you have one. The nav strip at the top points them at Catalogue and Enquire — the two surfaces the home page funnels into.

2. Catalogue

The customer browses your published inventory at /catalogue. The grid shows each item's primary image, name, metal type and stone type if recorded, and price (if your website config has show_prices = true). Items where is_published = false or the quantity is zero don't appear — your “not for the storefront” and “sold out” items stay off the public page.

Filter chips at the top of the catalogue narrow by category, metal type, and stone type. The filter options are sourced from the actual distinct values on your inventory rows, so a store that doesn't stock platinum doesn't see a Platinum filter chip surface. Filters compose — “Rings + Gold + Diamond” shows only items matching all three.

3. Item detail

Clicking an item in the catalogue lands the customer on /catalogue/[itemId] — a single-product page with the primary image (and any additional images you uploaded), the structured fields (metal, stone, ring, provenance), the price if your config allows showing it, and an item-enquiry form beneath the product details.

The enquiry form on the item page is pre-keyed with the item — when the customer submits, the inbound row in /enquiries references the specific item the customer was looking at. This is the lead-capture surface for “I'm interested in this piece” — see the Receiving web enquiries page for how the inbound is converted into a customer plus a downstream record.

4. Appointments

The customer books a consultation at /appointments — pick an appointment type (general consultation, ring-sizing, valuation, etc., configurable on your side), a preferred date and time, and submit. The submission lands in /enquiries as an enquiry-typed row, which you can convert into a booked appointment with the right customer attached.

The appointment surface is intentionally a lead form, not a live calendar booking. The customer requests a time; you confirm or counter-propose through the enquiry conversion flow. This keeps you in control of which appointments actually land on the calendar — the customer asks, you accept.

5. Repair enquiry

At /repairs the customer fills in a repair enquiry form — item description, the issue, photos if they have any, contact details. The submission lands in /enquiries flagged as a repair-typed enquiry; you convert it (Convert → Repair) and the system creates the customer row (if new) plus a repair record carrying the enquiry details across.

This is the entry point that pairs with the take-in counter for stores who want to capture repair leads before the customer physically arrives — the photos and description give the bench an early read on what the job involves before the piece is in hand.

6. General enquiry / contact

The catch-all contact form lives at /enquiry — the customer types a name, email, phone, and a message. The submission lands in /enquiries as a general-typed enquiry. From there you can convert into a customer plus optionally a quote or repair, or just reply directly without a downstream record.

7. Tracking entry on the subdomain

The subdomain also exposes a tracking entry at /track — a customer-friendly lookup page scoped to your shop's repairs and bespoke jobs. The customer types their tracking ID and lands on the per-order tracking detail. This is the same underlying tracking surface as the marketing-domain /track, presented as part of your storefront's nav so customers don't leave your subdomain mid-flow. See Repair tracking for the order-page details.

Common questions

Troubleshooting