For years, ecommerce businesses have had two common ways to handle pricing.
Publish the price and let customers buy.
Or:
Hide the price and ask customers to request a quote.
Both approaches can make sense depending on the product, customer, sales process, and business model.
A B2B manufacturer selling customised equipment may not be able to publish a single price. A jewellery brand selling a standard product may benefit from showing the exact price. A commercial furniture company may need to understand quantities, specifications, delivery requirements, and customisation before giving a final price.
Traditionally, this decision was mostly about the human buyer experience.
But ecommerce is entering another phase.
The person researching a product may now use Google, ChatGPT, Gemini, Perplexity, shopping assistants, or other AI-powered interfaces before ever visiting a product page.
That changes the question.
It is no longer only:
“Should we show the price to the customer?”
It is also:
“What happens when an AI assistant needs to understand, compare or recommend our product?”
Price is no longer just a conversion element on a product page. It is becoming part of the structured information that helps machines understand products and make decisions.
The Traditional Ecommerce Model
The traditional product discovery journey looks something like this:
Search → Product page → Read information → Check price → Compare → Add to cart → Checkout
The customer is responsible for collecting most of the information.
They visit multiple websites.
They open product pages.
They compare specifications.
They check prices.
They look at shipping policies.
They read reviews.
They contact sales teams when information is missing.
The ecommerce website is primarily designed to communicate with a human.
That model still matters.
But AI-assisted shopping introduces another layer.
The New Shopping Journey
Imagine a customer asks an AI assistant:
“Find me a premium office chair under $800 with adjustable lumbar support, a headrest, a five-year warranty and delivery to New York.”
The AI assistant now has to evaluate multiple products.
It needs to understand:
- What the product is
- Which variant is relevant
- How much it costs
- Whether it is available
- Which specifications it has
- Whether the warranty applies
- Where it can be delivered
- Whether it satisfies the customer's requirements
The assistant is effectively turning an ecommerce catalogue into a decision dataset.
If your product information is incomplete, ambiguous or difficult to access, the assistant has less information with which to work.
This is where pricing becomes particularly interesting.
Price Is Product Information
Ecommerce teams often think about price primarily as a sales or conversion element.
But from a machine perspective, price is also a product attribute.
Consider a product with the following information:
Product: Executive Office Chair
Material: Full-grain leather
Colour: Black
Warranty: 5 years
Availability: In stock
Price: $749
An AI assistant can potentially understand that product as a structured set of attributes.
Now remove the price.
Instead, the product says:
Price: Request a Quote
The machine has learned that a price exists somewhere in the sales process, but it does not have the actual value.
That creates a significant difference when the user asks:
“Which of these products costs less than $800?”
A product with a clearly available price can be evaluated against the requirement.
A product that requires a quote cannot be evaluated in exactly the same way unless the assistant has another mechanism for obtaining the price.
This doesn't automatically mean that hiding prices is wrong.
It means that hidden pricing creates an additional information gap.
What Happens When You Use “Request A Quote”?
The “Request a Quote” model has been around for decades.
It works particularly well when pricing is genuinely variable.
For example:
- Custom manufacturing
- Enterprise software
- Large-volume purchases
- Commercial equipment
- Custom jewellery
- Bespoke furniture
- Industrial products
- Wholesale orders
- Complex implementation services
- Products with location-dependent pricing
In these situations, publishing one number may actually be misleading.
The final price might depend on:
Quantity + configuration + materials + shipping + installation + customisation + customer requirements
A quote process allows the seller to collect this information.
The problem appears when the quote process is used for products where the customer expects a straightforward price.
For a $200 product, forcing a customer to submit a form before discovering the price can introduce unnecessary friction.
And now there is another consideration:
What does the AI assistant do with that friction?
AI Assistants Prefer Understandable Product Information
AI systems need context.
A product name alone is rarely enough.
Consider these two product listings.
Product A
Gold Necklace
No price.
No weight.
No gold purity.
No dimensions.
No gemstone information.
“Contact us for pricing.”
Product B
18K Gold Diamond Necklace
- 18K gold
- Natural diamonds
- 0.50 ct total diamond weight
- Necklace length: 18 inches
- Product weight: 12.4 g
- Price: ₹1,85,000
- Made to order
- Delivery: 10–14 days
The second product provides considerably more information that can be interpreted and compared.
This matters for traditional SEO.
It matters for ecommerce conversion.
And increasingly, it matters for AI search and AI-assisted commerce.
The goal is not simply to make a product page attractive.
The goal is to make the product understandable.
AI Search Changes Product Discovery
Search has traditionally been dominated by keyword matching.
A user searches for:
“18k diamond necklace under ₹2 lakh”
A search engine identifies relevant pages.
AI-powered search can take the query further by interpreting the intent and potentially synthesising information from multiple sources.
The user may instead ask:
“Find a premium 18k gold diamond necklace under ₹2 lakh that would work for a formal evening event.”
Now the system has to understand several concepts:
- Product category
- Material
- Gold purity
- Gemstone
- Price
- Occasion
- Positioning
- Potential suitability
The more accurately an ecommerce site communicates these attributes, the more useful its product information becomes to systems attempting to answer that question.
This is one reason AI Search Optimization is increasingly connected to ecommerce product data.
The Importance of Structured Product Data
A modern ecommerce store should not rely exclusively on visual presentation.
A beautiful product page may communicate information effectively to a human visitor.
But machines also need structured signals.
Depending on the platform and implementation, ecommerce businesses can provide structured information around:
- Product name
- Description
- Brand
- SKU
- GTIN
- Images
- Variants
- Price
- Currency
- Availability
- Product condition
- Reviews
- Ratings
- Shipping
- Returns
- Product attributes
Structured data does not guarantee that an AI assistant will use or recommend a product.
But clear, consistent and machine-readable information reduces ambiguity.
For Shopify merchants, this becomes particularly relevant because product catalogues can contain hundreds, thousands or even millions of product and variant combinations.
The challenge is no longer just:
“Do we have product data?”
It is:
“Is our product data complete, accurate, consistent and understandable?”
Published Pricing Creates Comparability
One of the biggest advantages of publishing prices is comparability.
Suppose someone asks:
“Compare three running shoes under ₹15,000.”
If the products have published prices, an AI assistant or traditional search experience can potentially compare them using that constraint.
It becomes difficult to determine whether it satisfies the customer's budget.
The product may still be excellent.
The brand may still be highly relevant.
But one of the customer's most important decision criteria is unavailable.
But Publishing a Price Is Not Always Better
This distinction is important.
Businesses should not publish an artificial price simply because they want to become more machine-readable.
If the final price genuinely depends on customer requirements, publishing a misleading number creates another problem.
For example:
Industrial machine
Base price: ₹15 lakh
But the customer's final configuration requires:
- Additional equipment
- Installation
- Custom tooling
- International shipping
- Maintenance contract
The actual price could be significantly different.
In this situation, Request a Quote may be the appropriate business model.
The objective should not be:
“Always publish a price.”
The objective should be:
“Provide as much useful pricing information as the business model allows.”
The Hybrid Pricing Model
For many ecommerce businesses, the answer may be a hybrid approach.
Instead of:
Request a Quote
you could provide:
Starting from ₹5,00,000
or:
Base price: ₹5,00,000
or:
Typical project range: ₹5–8 lakh
Then explain what determines the final price.
For example:
Starting from ₹5,00,000
Final pricing depends on configuration, quantity, installation requirements and delivery location.
Request a Custom Quote
This approach gives the customer and potentially machine-readable systems an important reference point while preserving the sales process.
Other useful information can include:
- Starting price
- Price range
- Minimum order quantity
- Unit price
- Volume discounts
- Configuration-based pricing
- Subscription price
- Installation cost
- Shipping cost
- Estimated total
- Currency
- Tax information
The more transparent the model, the easier it becomes to understand.
What AI Assistants Do With Missing Information
Imagine an AI assistant receives information about five products.
Four products have:
- Clear prices
- Product specifications
- Availability
- Shipping information
- Returns information
One product has:
- Product name
- Images
- Long marketing description
- No price
- No availability
- “Contact sales”
The assistant has different levels of information available for each product.
For a query requiring a strict price limit, the fifth product may be difficult to evaluate.
For a query asking:
“Which brands make premium industrial equipment?”
the same company may still be relevant.
This distinction is important.
Missing price does not make a product invisible.
It can simply make the product harder to evaluate for price-dependent queries.
Product Discoverability Is Becoming Multidimensional
Ecommerce businesses have historically focused heavily on ranking.
But visibility increasingly involves multiple layers.
A product can be:
Searchable
Can search engines discover it?
Understandable
Can machines accurately understand what it is?
Comparable
Can its attributes be compared with alternatives?
Recommendable
Does the available information support an AI-generated recommendation?
Actionable
Can the customer or AI assistant actually take the next step?
This creates a broader ecommerce concept:
Discoverability → Understanding → Recommendation → Action
Price can influence several stages of this journey.
The Role of Shopify
Shopify stores already contain a significant amount of structured ecommerce information.
Products have:
- Titles
- Descriptions
- Variants
- Prices
- Inventory
- Images
- Collections
- Product types
- Vendors
- SKUs
But the quality of the information depends on how the store is built and maintained.
For example, a Shopify product might have a highly optimised title:
18K Gold Diamond Tennis Bracelet
But its supporting data could still be incomplete.
Important attributes such as:
- Gold purity
- Diamond carat weight
- Diamond shape
- Bracelet length
- Certification
- Shipping time
- Made-to-order status
may exist only inside an image, PDF or loosely written description.
From an AI perspective, this creates an information-quality problem.
Product Pages Need To Be Written For Humans And Machines
This does not mean turning product pages into robotic databases.
The best product pages still need to persuade people.
They need:
- Strong imagery
- Clear benefits
- Emotional storytelling
- Detailed descriptions
- Reviews
- Social proof
- Pricing
- Calls to action
- Trust signals
But underneath the customer-facing experience, the product should also have a strong information architecture.
Think of the product page as having two audiences:
Human audience
“What makes this product right for me?”
Machine audience
“What exactly is this product, what does it cost, who is it for, and what can I do with it?”
Good ecommerce architecture serves both.
When “Request A Quote” Makes Sense
There are many situations where quote-based pricing remains useful.
1. Custom Products
Products requiring extensive customisation often cannot have one universal price.
2. B2B Commerce
Wholesale buyers may receive different pricing based on:
- Quantity
- Contract
- Customer tier
- Location
- Relationship
- Payment terms
3. Enterprise Purchases
Large organisations may require procurement, implementation and support discussions before a final price is established.
4. Complex Services
Some products are actually combinations of products and services.
The final cost depends on the scope.
5. Variable Logistics
International shipping, installation and taxes can significantly affect final pricing.
6. High-Value Purchases
For certain high-ticket categories, sales-assisted purchasing can be an intentional part of the customer journey.
In these situations, a quote process is not necessarily a weakness.
The key is to make the process informative.
Make The Quote Process Machine-Friendly Too
If you genuinely need a quote, don't stop at:
Request a Quote
Provide additional context.
For example:
Custom Commercial Lighting
Starting from ₹2,50,000
Final pricing depends on:
- Number of units
- Project dimensions
- Finish
- Installation
- Delivery location
Typical lead time: 4–6 weeks
Request a Custom Quote
This provides substantially more context than a blank pricing field.
You can also structure the quote process around product information.
Instead of asking customers to explain everything from scratch, allow them to select:
- Product
- Variant
- Quantity
- Configuration
- Delivery location
- Customisation
- Required timeline
This makes the process easier for both customers and the systems supporting them.
AI Agents Need Actionable Commerce Data
The next stage goes beyond AI search.
Instead of asking:
“What products exist?”
a customer may ask:
“Find me a suitable product and help me buy it.”
This moves from AI discovery toward agentic commerce.
An AI assistant could potentially help with:
- Product discovery
- Product comparison
- Product selection
- Availability checking
- Cart creation
- Checkout initiation
- Order-related actions
For an AI agent to complete these steps reliably, product information alone is not enough.
The commerce system needs to expose useful information and actions.
This can include:
- Product identifiers
- Variant identifiers
- Prices
- Inventory
- Cart actions
- Checkout information
- Shipping options
- Returns
- Order information
This is where ecommerce architecture starts becoming an important part of AI readiness.
The Product Feed Becomes More Important
Many ecommerce businesses already think about product feeds for advertising.
Google Shopping, Meta catalogues and marketplace integrations require structured product information.
The same underlying principle becomes increasingly relevant to AI-powered discovery.
A product feed should ideally communicate consistent information across systems.
For example:
Website
₹49,999
Google Merchant data
₹49,999
Structured product data
₹49,999
Shopping feed
₹49,999
If different systems contain different prices, availability or product attributes, confusion can follow.
Consistency becomes an important part of digital commerce infrastructure.
Pricing Consistency Matters
Imagine a product page says:
₹79,999
but another data source says:
₹69,999
and an outdated page says:
₹59,999
A human customer may notice the discrepancy.
A machine can also encounter conflicting information.
Therefore, ecommerce teams should consider:
- Where price originates
- How price changes are propagated
- Whether feeds update automatically
- Whether structured data reflects the current price
- Whether variant prices are correctly represented
- Whether sale pricing is correctly implemented
- Whether inventory information remains current
AI readiness is not simply about adding an AI chatbot.
It starts with the quality of the underlying commerce data.
What Ecommerce Teams Should Audit
Before thinking about AI agents, ecommerce businesses should audit their product information.
Product Identity
Can a system clearly identify the product?
Product Attributes
Are the important characteristics explicitly defined?
Pricing
Is the price visible, structured and current?
Variants
Are variant-specific prices and attributes clearly represented?
Availability
Can systems determine whether the product is available?
Shipping
Is delivery information available?
Returns
Are return conditions clear?
Reviews
Are reviews and ratings represented consistently?
Product Relationships
Can systems understand related products, accessories, alternatives and complementary products?
Category Structure
Does the website have a logical taxonomy?
These elements contribute to the overall quality of the commerce data layer.
A Practical Framework: Price Transparency Levels
Not every business needs the same pricing model.
You can think about pricing transparency in four levels.
Level 1: Full Price
₹25,000
Best suited to standardised products with relatively fixed pricing.
Level 2: Price + Conditions
₹25,000
Bulk discounts available for orders above 10 units.
Useful for businesses with predictable base pricing and volume variations.
Level 3: Starting Price
Starting from ₹25,000
Final price depends on configuration.
Useful for products with customisation.
Level 4: Quote Required
Request a Quote
Appropriate when pricing genuinely cannot be determined without additional customer information.
The important thing is to communicate why a quote is required.
The Bigger Shift: From Pages To Product Data
The future of ecommerce is not only about building better webpages.
It is about building better commerce data systems.
A product page is one presentation layer.
The same underlying product information may be consumed by:
- Search engines
- Shopping platforms
- Marketplaces
- Advertising platforms
- Recommendation systems
- AI assistants
- Customer service systems
- Commerce agents
This means product information needs to be consistent across channels.
The product catalogue becomes a foundation for discovery.
What Should Shopify Merchants Do Today?
Shopify merchants don't need to completely rebuild their stores to start preparing.
A practical starting point is an ecommerce data audit.
Step 1: Review your catalogue
Identify missing or inconsistent product information.
Step 2: Improve product attributes
Move important information out of images and into text or structured fields wherever appropriate.
Step 3: Review pricing
Determine which products should have:
- Fixed prices
- Starting prices
- Price ranges
- Quote-based pricing
Step 4: Improve structured data
Make sure important product information is represented accurately.
Step 5: Review variants
Ensure variant-specific pricing, availability and attributes are correct.
Step 6: Review feeds
Check whether Google, Meta and other commerce feeds contain accurate information.
Step 7: Improve taxonomy
Build logical categories, collections and product relationships.
Step 8: Review AI discoverability
Test how AI search systems understand your brand and products.
Ask questions such as:
“What does this brand sell?”
“Which products from this brand are suitable for [specific use case]?”
“Which products are available under ₹X?”
“How does this brand compare with alternatives?”
The answers can reveal where product information is strong and where it is incomplete.
The Question Is Not “Price Or Quote?”
The debate between publishing a price and requesting a quote is not going away.
And it shouldn't.
Different ecommerce businesses have different commercial models.
The more useful question is:
“What information can we provide before asking the customer to take another step?”
If you can publish an exact price, publish it.
If you can publish a starting price, publish it.
If you can provide a realistic range, provide it.
If you genuinely need a quote, explain what determines the quote.
And most importantly, make the product information around that pricing model clear and structured.
Because the future customer journey may not begin with someone clicking through ten product pages.
It may begin with someone asking an AI assistant:
“What should I buy?”
At that point, your product needs to be more than visible.
It needs to be understandable, comparable and actionable.
That is the bigger shift happening in ecommerce.
The product page is no longer just a destination for shoppers. It is becoming a source of commerce data for the systems helping shoppers decide what to buy.
Top comments (0)