Shopify for Luxury and Made-to-Order Brands: Handling “Price on Request” and Product Enquiries

When “price on request” makes sense

A Shopify price-on-request journey suits products whose final specification needs a conversation before purchase. A couture garment may depend on measurements and finishing; a commissioned piece may depend on materials or availability. The product page should help someone begin that conversation with enough context to receive a useful response.

It is less useful when the product already has a fixed price, clear options and straightforward delivery. Requiring an enquiry adds effort for both customer and team. Keep ordinary checkout for products that can be bought confidently, and introduce consultation where it resolves a real uncertainty.

Give the product page a complete purpose

Removing the price does not remove the need for product information. The visitor still needs to understand the piece, see relevant photographs and know why a conversation is useful. Explain available customisation, the production process and whether an appointment is part of the next step. Only show timelines your team can support.

• Use a specific action such as “Enquire about this garment” rather than a generic “Contact us”.
• Keep the product title, reference and selected option attached to the enquiry.
• Explain the next step beside the button: a team response, consultation booking or specification review.
• Provide a clear alternative for visitors who cannot use your preferred messaging app.

Avoid presenting an unknown price as zero or implying that an item is free. The storefront, customer messages and any product feeds should describe the same offer. An enquiry-led catalogue can still be useful even when the final commercial terms are agreed later.

Use a deliberate product rule, then test every entry point

Shopify documents a product-template approach for hiding the buy buttons, with an optional hidden price block, on selected products. See Shopify’s product-template instructions. The exact controls depend on the theme, so check the current theme before choosing an implementation.

For a mixed catalogue, agree a maintainable way for the merchant to identify enquiry-only products. That might be a dedicated template or a product field used by custom theme code. Write down who can change that setting and what happens when a new product is added. A rule based on a fragile product-title match is difficult to maintain.

• Product pages, collection cards and quick-add controls.
• Search results, recommendations and saved or shared cart links.
• Accelerated purchase buttons and any installed sales apps.
• Other sales channels in which the product is published.

Collect enough detail to continue the conversation

A good first enquiry is short enough to complete on a phone and specific enough for the sales team to understand. Ask for a contact method, the product reference and the question the customer needs answered. Add fields such as an occasion date or preferred variant only when they affect the response.

Avoid asking for a full set of measurements or sensitive personal information before anyone has spoken to the customer. For a messaging link, include a readable product name and page URL in the starting message. Do not put private customer details into a URL. For a form, validate the fields and show a success message only after the submission is accepted.

Define a fallback for a failed submission. A customer should not lose a carefully written request because an integration is unavailable. Keep the enquiry text available and show another contact route. The team also needs a named inbox or owner; a polished form is not useful if nobody knows who should answer it.

Connect the enquiry to a quote and an order

Map the internal process before adding an app. Decide who reviews the brief, who confirms the specification, how the customer approves it and when payment is requested. Keep the agreed scope and any promised delivery details with the order record instead of relying on a conversation that only one staff member can access.

Shopify supports draft orders and invoices with checkout links. That can support a staff-reviewed quote followed by payment, subject to the store’s configuration. Shopify’s draft-order guide explains the available actions. An enquiry form does not automatically create this workflow; connecting those steps is a separate requirement.

1. Receive the product enquiry with its reference and contact details.
2. Clarify the specification and record the agreed commercial terms.
3. Prepare the appropriate quote or draft order after staff review.
4. Obtain customer approval and request payment through the agreed route.
5. Hand the confirmed order to production or fulfilment with its approved details.

A couture storefront example: Nidhi Halani

Our Nidhi Halani case study describes a Shopify storefront combining collection browsing, editorial product presentation and product-specific consultation enquiries. The work includes custom Liquid theme development and catalogue organisation. It is a useful example of keeping the product and the conversation connected.

The lesson is about the buying journey, rather than a universal feature list. A brand selling both available pieces and commissioned work needs clear paths for each. Your catalogue, staff process and customer expectations determine which parts of that approach are relevant to your store.

Check the complete journey before launch

• Test an enquiry product and a normal checkout product on mobile and desktop.
• Verify that changing the product or variant carries the correct context into the request.
• Check successful delivery, validation errors, duplicate clicks and a failed submission.
• Confirm that staff can identify and respond to the request from the agreed destination.
• Review product feeds and structured data for misleading prices or availability.
• Confirm how the merchant will add the next enquiry-only product without developer assistance.

Google distinguishes product snippets from merchant listing experiences. Review the requirements that match the actual page rather than adding an invented offer to obtain a rich result. Google’s product structured-data overview explains that distinction.

The Nidhi Halani storefront is relevant evidence for collection browsing and consultation enquiries. Our fashion Shopify service page explains how to discuss this kind of scope without assuming a sales result.

Questions about Shopify product enquiries