Wine and spirits
Ask an assistant for a gift bottle and strength, age, origin and price matter. Make those facts available as text and product data, while respecting the age and regional restrictions of each sales channel.
[01] What shoppers ask
See how a buying question connects to the facts in a product record.
Here are two bottles to compare. Check the tasting notes, origin and bottle details against what you have in mind.

Your listing
Single malt A

Comparison listing
Single malt B
Explore another question
[02] What the agent compares
Make the product facts explicit, then review the change in the shared source record.
Example with sample data
Two invented listings, represented as JSON. Restore an omitted fact to see what changes in this scripted comparison.
The source fact behind the fix
Smoky single malt under $80 for a gift
This example follows the first shopper question. The visual shows the existing source facts before the code change below.
wine-and-spirits-comparison.json
Unified diffAdded: +1Removed: −1
11 {22 "shopper_question": "Smoky single malt under $80 for a gift",33 "your_listing": {44 "product": "Single malt A",55 "strength": "46% ABV",66 "age": "12 years",77 "origin": "Islay, Scotland",8−Removed: "style": null,8+Added: "style": "Peated single malt; bourbon cask",99 "size_and_price": "700 ml · $72",1010 "availability": "In stock; eligible delivery areas only"1111 },1212 "comparison_listing": {1313 "product": "Single malt B",1414 "strength": "40% ABV",1515 "age": "10 years",1616 "origin": "Highlands, Scotland",1717 "style": "Smoky single malt; bourbon cask",1818 "size_and_price": "700 ml · $76",1919 "availability": "In stock; eligible delivery areas only"2020 }2121 }Why these fields matter
A rival’s listing states the smoky style and a price under $80. Your listing leaves the style unstated.
Your listing now states the smoky single-malt style. Both fit the question; the lower bottle price breaks the tie in this example.
Illustrative records, not an API submission format. null means the listing leaves a fact unstated.
[03] Sector rules
Make bottle facts explicit, compare the listing, and scope a purchase flow around the channel and market that permit it.
Use verified origin, style, strength, price and delivery information in the comparison. Verify the source facts and permitted claims before choosing Apply, which generates and publishes the title and description. Product and destination restrictions still apply.
What still needs review
Google’s alcohol policy restricts promotion by target country and requires compliance with applicable local laws. Product data or a working checkout does not remove those restrictions.
Do not assume an age check is automated. The merchant must confirm that its chosen sales and payment flow satisfies the applicable requirements.

Simulation scope
Use ChatGPT, Claude and Gemini simulation perspectives to compare supported product facts. Perplexity currently supports Shopify referral tracking; its store simulations are coming soon. A simulation is not channel approval.
Plan an agent-assisted purchase flow with ecentic around your existing controls. Scope comes before implementation; support depends on the product, country, channel and payment provider.
Check the product, destination and chosen channel’s rules before exposing a purchase path.
Integrate the merchant’s existing age-verification process where required. Built-in ecentic age verification is not assumed.
The buyer completes the required checks and confirms payment in the merchant’s permitted checkout flow.
Sources checked 10 November 2026. Requirements can depend on the product, channel and country.
[04] Your business
Start from the way your business sells and manages its catalog.
See your solutionStart from the way your business sells and manages its catalog.
See your solutionStart from the way your business sells and manages its catalog.
See your solutionStart from the way your business sells and manages its catalog.
See your solution