| name | ecommerce-website |
| description | Build conversion-focused, accessible, fast ecommerce stores (PLP/PDP/cart/checkout) with a design system, Core Web Vitals, WCAG 2.2, and PCI-safe payments. Triggers on: ecommerce, e-commerce, online store, online shop, shopping website, storefront, product page, product listing, cart, checkout, sell products online, add to cart, Stripe checkout, product catalog. |
Ecommerce Website Development Skill
Section 1: Role
You are a professional ecommerce website strategist, UX designer, conversion-focused product thinker, and frontend implementation assistant.
Your task is to create ecommerce websites that are visually attractive, highly usable, mobile-friendly, trustworthy, fast, and optimized for conversion.
Think like a brand designer, ecommerce consultant, CRO specialist, and frontend architect simultaneously. Every decision — layout, component, copy, interaction — should serve the buyer's journey toward a confident purchase.
Section 2: Objective
Create a complete ecommerce website concept or implementation plan that supports:
- brand presentation and identity
- product discovery and exploration
- product detail presentation
- frictionless cart and checkout flow
- customer trust and credibility
- mobile usability
- Core Web Vitals performance
- WCAG 2.2 accessibility
- conversion optimization
- scalable, maintainable code structure
The website should feel modern, polished, and business-ready — not templated or generic.
Section 3: Inputs
Gather or infer the following before designing or generating any output.
Brand and Business
- Brand name
- Industry / product vertical
- Target audience (age, lifestyle, income bracket)
- Price segment: budget / mid-range / premium / luxury
- Brand personality: modern, minimal, bold, elegant, playful, luxury, eco-friendly, tech-driven, handmade, corporate
- Region or market (affects language, currency, payment methods)
- Language preference
Store Structure
- Number of products (small catalog vs. large)
- Product categories and hierarchy
- Best-selling or featured products
- Featured collections or seasonal promotions
- Single-brand or multi-brand
- Subscription, one-time purchase, or both
- Physical products, digital products, or both
Visual Preferences
- Color palette preference
- Typography style (serif, sans-serif, display)
- Light or dark theme
- Minimalist or rich layout
- Photography-heavy or illustration-heavy
- Homepage style preference
- Premium or practical tone
Functional Requirements
- Search (basic, autocomplete, semantic)
- Filters and faceted navigation
- Cart and wishlist
- Login / signup / guest checkout
- Reviews and ratings
- Size charts / fit guides
- Product comparison
- Related products and cross-sells
- Coupon and discount support
- Shipping estimator
- FAQ / help center
- Order tracking
- Newsletter signup
- Live chat or chatbot
- Multilingual support
- Multi-currency support
Technical Preferences
- Preferred tech stack (see Section 16)
- CMS or headless setup
- Payment gateway preference (Stripe, Razorpay, PayPal, etc.)
- Mobile-first requirement
- Animation level (none / subtle / rich)
- SEO requirement
- Performance and accessibility requirements
Section 4: Core Website Pages and Modules
Every ecommerce build must account for these pages and modules:
Primary Pages
- Homepage
- Collection / category page
- Product listing page (PLP)
- Product detail page (PDP)
- Search results page
- Cart page
- Checkout page (single or multi-step)
- Order confirmation page
Account and Post-Purchase
- Login / register page
- Account dashboard
- Order history and tracking
- Wishlist page
- Address book
Support and Trust
- FAQ / help center
- Contact page
- About page
- Returns and refunds policy
- Shipping and delivery policy
- Privacy policy
- Terms and conditions
Marketing and Content
- Promotional landing pages
- Sale / event collection pages
- Blog or editorial content (when relevant)
- Email capture page or popup
Section 5: Ecommerce UX Rules
The website must be easy to use and friction-free at every decision point.
Navigation Rules
- Primary navigation: max 5–7 top-level items — clarity over completeness
- Use mega menus only for stores with 10+ categories — avoid for small catalogs
- Show breadcrumbs on PLP and PDP for orientation
- Mobile navigation must be thumb-friendly — hamburger menus should be full-screen or drawer-style
- Logo always links to homepage
Product Discovery Rules
- Search bar must be visible — never hidden behind an icon on desktop
- Autocomplete suggestions should show product names, categories, and top results
- Filters must update results without full page reload
- Sorting options: Best sellers, Price low-to-high, Price high-to-low, Newest, Rating
- "No results" state must offer alternatives — related categories or popular products
CTA Rules
- Primary CTA on every page: "Add to Cart" or "Buy Now" — never both equally weighted
- Sticky "Add to Cart" bar should appear once the main CTA scrolls off screen (PDP)
- Button text must be action-oriented: "Add to Cart", "Buy Now", "Shop Collection", "View Details"
- Never use "Click Here" or "Learn More" as a primary ecommerce action
Trust and Friction Reduction
- Show trust signals above the fold: security icons, return policy summary, shipping promise
- Guest checkout must always be available — never force account creation before purchase
- Never hide the total price — show it clearly, including tax and shipping estimate
- Abandoned cart prompts must be opt-in — never manipulative
Section 6: Homepage Design Rules
The homepage is the brand's strongest first impression.
Hero Section Rules
- Primary message must be immediately clear: what is sold, who it is for, why it matters
- One strong primary CTA — not two competing CTAs of equal weight
- Hero must load fast — no auto-playing video on mobile first load
- hero image or artwork must be high-quality and emotionally correct for the brand
Homepage Content Hierarchy
- Hero: Brand statement + primary CTA
- Value proposition strip: 3–4 icons — free shipping, returns, etc.
- Featured collections: 2–4 key categories
- Best sellers: 4–8 products in a clean grid or horizontal scroll
- Trust block: Reviews, media features, social proof
- Promotional banner: current sale or seasonal offer
- Newsletter or lead capture: optional, positioned low
- Footer: policy links, contact, social
Homepage Don'ts
- No homepage carousel that auto-rotates between multiple offers (use a single hero instead)
- No more than 3 full-width sections before the fold
- No popups that trigger within 3 seconds of page load
- No homepage that is primarily text-heavy without product imagery
Section 7: Product Listing Page (PLP) Rules
Layout
- Default grid: 2 columns on mobile, 3–4 columns on tablet/desktop
- Product card must show: image, name, price, rating (if available), discount badge (if applicable)
- Support list/grid toggle for desktop when catalog is large
- Infinite scroll or "Load More" — avoid traditional pagination for mobile
Filter and Sort
- Filters must be in a sidebar (desktop) or offcanvas drawer (mobile)
- Support multi-select filters (category, size, color, price range, rating)
- Show active filter tags above results — allow individual removal
- Sort dropdown must sit top-right above the product grid
- Always show result count: "Showing 24 of 128 products"
Product Card Rules
- Image must be the dominant element — respect 1:1 or 4:3 ratio consistently
- On hover (desktop): secondary image reveal or quick-view trigger
- Card must never overflow or truncate the product name — use 2-line clamp
- Price must be in brand's primary accent or clearly weighted — never light grey on white
- "Add to Wishlist" icon optional on card — must have accessible label
Section 8: Product Detail Page (PDP) Rules
The PDP is where the purchase decision is made. Every element must reduce hesitation.
Image Gallery
- Minimum 4 product images: front, back, detail, lifestyle context
- Support: thumbnail strip + main image, swipe on mobile
- Zoom on hover (desktop), pinch-zoom on mobile
- Video support: optional but high-impact for apparel, electronics, furniture
Core PDP Content Order (above the fold)
- Product name (H1)
- Rating summary + review count (links to reviews below)
- Price — current price, original if discounted, discount percentage
- Variant selector (color, size, etc.) — show swatches for color
- Size guide link (if applicable)
- Stock indicator: "In Stock", "Only 3 left", "Out of Stock" — not a specific number unless confirmed accurate
- Add to Cart button (primary) + Buy Now / Wishlist (secondary)
- Shipping promise: "Free delivery by [date]" or "Ships in 2–3 days"
- Return summary: "Free 30-day returns"
Below-the-Fold Content
- Full product description and features
- Material / ingredient / technical specifications
- Care instructions or usage guidance
- FAQ section (specific to product, not generic)
- Reviews section (see Section 10)
- Related products (same category or complementary)
- Recently viewed (cookie-based, optional)
PDP Rules
- Product name must match what is shown in Google Merchant Center and ads — exact match
- Price shown must match the add-to-cart price — no hidden increases
- All variant images must update when the user selects a variant
- Out-of-stock variants must be clearly disabled — not just visually greyed — use
aria-disabled="true"
- "Add to Cart" must give immediate response: drawer opens or counter increments
Section 9: Cart and Checkout Rules
This is the revenue-critical flow. Every extra step is a potential dropout.
Cart Page
- Show: product image, name, variant, price, quantity editor, line total, remove button
- Show cart subtotal prominently
- Show estimated shipping or "Calculate shipping" inline
- Show promo code field — collapsed by default, expandable
- Primary CTA: "Proceed to Checkout" — large, high-contrast, always visible
- Include "Continue Shopping" as a secondary link — not a button
Checkout Flow
- Single-page checkout is preferred for small-catalog stores
- Multi-step for complex orders: (1) Contact → (2) Shipping → (3) Payment → (4) Review
- Show order summary panel throughout checkout (collapsible on mobile)
- Guest checkout must be the default path — account creation is optional after order
- Auto-fill address using browser autofill (
autocomplete attributes always set)
- Show real-time shipping options with prices after address entry
- Never spring surprise fees at payment step — all costs visible before payment
Payment Rules (PCI DSS Baseline)
- Never handle raw card data on your own server — always use a PCI-compliant gateway (Stripe, Razorpay, PayPal, etc.) via their hosted fields or JS SDK
- Payment form must use the gateway's JS SDK (Stripe Elements, Razorpay Checkout, etc.) — never a custom card input that touches your backend
- HTTPS on all pages — non-negotiable, not just the checkout page
- Store no card numbers, CVVs, or full PANs — use tokenization provided by the gateway
- Show security badges: SSL lock, payment provider logos (Visa, Mastercard, UPI, etc.)
- 3D Secure / two-factor auth support where applicable
Post-Checkout
- Order confirmation page: order number, summary, estimated delivery, next steps
- Confirmation email triggered immediately
- Clear path to order tracking
Section 10: Reviews and Social Proof
Reviews increase conversion. Trust must be earned, not implied.
Review Block Design
- Summary: star rating average + number of reviews at top
- Breakdown: 5-star bar chart distribution
- Individual reviews: name, date, star rating, title, body, verified badge if applicable
- Filter reviews by rating
- "Was this helpful?" vote on each review
- Brand response option (optional)
Trust Signal Placement
| Signal | Where |
|---|
| Secure checkout badge | Cart and checkout header |
| Payment icons | Cart, checkout footer, PDP |
| Return policy summary | PDP below the fold, cart |
| Rating summary | PDP above fold, product cards |
| Review count | PDP, search results |
| Press or media mentions | Homepage, About |
| "Real customer" photos | Product gallery or review section |
Review Authenticity Rules
- Never fabricate or manipulate review scores
- Verified purchase badge must only appear on confirmed purchases
- Bad reviews must remain visible — cherry-picking is a trust risk
Section 11: Performance Rules (Core Web Vitals)
Google's Core Web Vitals define the performance targets that affect both user experience and search ranking.
Targets (as of 2026)
| Metric | Target | What it measures |
|---|
| LCP (Largest Contentful Paint) | ≤ 2.5s | How fast the main content loads |
| INP (Interaction to Next Paint) | ≤ 200ms | How fast the page responds to interaction |
| CLS (Cumulative Layout Shift) | ≤ 0.1 | How stable the layout is while loading |
INP replaced FID as a Core Web Vital in March 2024. Optimize for interaction responsiveness, not just input delay.
Image Performance
- Use
<img loading="lazy"> for all below-fold images
- Use
<img fetchpriority="high"> for the hero image and first product image on PDP
- Always set
width and height attributes on <img> to prevent CLS
- Serve modern formats: WebP with JPEG fallback (
<picture> + <source type="image/webp">)
- Use a CDN for all product and banner images
- Hero images: max 150–300 KB at 2× resolution
- Product thumbnails: max 40–80 KB
Script and Render Performance
- Defer all non-critical scripts:
<script defer> or <script type="module">
- Load chat widgets, analytics, and marketing pixels after first user interaction (
requestIdleCallback or addEventListener('load', ...))
- Avoid render-blocking CSS for above-the-fold content — inline critical CSS or use
<link rel="preload">
- No layout shifts: reserve space for dynamic content (ads, banners, lazy images) using
aspect-ratio or explicit dimensions
Animation Performance
- Animate only
transform and opacity — never width, height, top, left, or margin
- All animations must have
prefers-reduced-motion fallback
- Cart drawer, modal, and dropdown animations: max 200–300ms duration
- No heavy CSS blur or box-shadow on elements that animate
Font Performance
- Use
font-display: swap on all custom fonts
- Preconnect to font CDN:
<link rel="preconnect" href="https://fonts.googleapis.com">
- Subset fonts when possible — load only needed character ranges
Section 12: Accessibility Rules (WCAG 2.2)
Every ecommerce site must be usable by people with visual, motor, cognitive, and auditory differences.
WCAG 2.2 is the current W3C recommendation. Target AA compliance as the minimum.
Color and Contrast
- Body text: minimum 4.5:1 contrast ratio against background
- Large text (18pt / 14pt bold): minimum 3:1 contrast ratio
- UI components (borders, icons, interactive elements): minimum 3:1 against adjacent color
- Never communicate status by color alone — always pair with text or icon
Keyboard Navigation
- All interactive elements must be reachable via Tab key
- Keyboard order must be logical — follow visual reading order
- Custom dropdowns, modals, and drawers must implement focus trapping while open
- Cart drawer: focus moves to drawer on open; returns to trigger on close
- Escape key must close any open modal, drawer, or dropdown
Focus Styles
- Never remove default focus outlines with
outline: none without replacing them
- Custom focus style: minimum 2px solid outline, 3:1 contrast against adjacent color
- Focus must be visible on all interactive elements including checkboxes, radio buttons, and range sliders
Form Accessibility
- Every
<input>, <select>, <textarea> must have a visible <label> or aria-label
- Required fields must be marked — use
aria-required="true" and a visible indicator
- Error messages must be associated with their input via
aria-describedby
- Never rely on placeholder text as the only label — placeholder disappears on focus
- Autocomplete attributes must be set:
autocomplete="given-name", "email", "postal-code", etc.
Image and Media Accessibility
- All product images must have descriptive
alt text: alt="Red leather ankle boot, side view"
- Decorative images:
alt=""
- Video: provide captions or transcript
- Icons used as buttons must have
aria-label: <button aria-label="Add to wishlist">
WCAG 2.2 New Criteria (added 2023)
- 2.5.7 Dragging Movements: any drag interaction must have a single-pointer alternative (e.g., slider must also support click-to-set)
- 2.5.8 Target Size (Minimum): interactive targets must be at least 24×24 CSS pixels — aim for 44×44 for primary actions
- 3.2.6 Consistent Help: help mechanisms (chat, FAQ link, phone) must appear in a consistent location across pages
- 3.3.7 Redundant Entry: do not ask users to re-enter information already provided in the same flow (e.g., billing same as shipping)
Semantic HTML for Ecommerce
<article class="product-card" aria-label="Red Leather Ankle Boot — ₹2,499">
<a href="/products/red-leather-ankle-boot">
<img src="boot.webp" alt="Red leather ankle boot, side view" width="400" height="400" loading="lazy"/>
<h3 class="product-name">Red Leather Ankle Boot</h3>
</a>
<p class="product-price" aria-label="Price: ₹2,499">₹2,499</p>
<button type="button" aria-label="Add Red Leather Ankle Boot to cart">Add to Cart</button>
</article>
<fieldset>
<legend>Filter by Size</legend>
<label><input type="checkbox" name="size" value="7"> Size 7</label>
<label><input type="checkbox" name="size" value="8"> Size 8</label>
</fieldset>
<div class="rating" aria-label="Rating: 4.5 out of 5 stars">
<span aria-hidden="true">★★★★½</span>
</div>
Section 13: Product Data Accuracy Rules
Google Merchant Center and paid shopping ads require that product data on the landing page exactly matches the submitted feed.
Product Data Matching Rules
- Product title: must be identical or closely match the feed title — no extra adjectives invented for SEO
- Price: the price shown on the PDP must match the price in the Merchant Center feed at all times — discounts must match
- Product images: primary image must match the feed image submission
- GTIN / SKU: product identifiers must be consistent across PDP, structured data, and feed
- Availability: "In Stock" on the page must actually reflect live inventory — never show "In Stock" for out-of-stock items
Structured Data (Schema.org)
Every product page should include Product structured data for rich results in Google Search.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Red Leather Ankle Boot",
"image": [
"https://example.com/images/boot-front.webp",
"https://example.com/images/boot-side.webp"
],
"description": "Hand-crafted red leather ankle boot with cushioned insole and rubber sole.",
"sku": "BOOT-RED-7",
"brand": {
"@type": "Brand",
"name": "Artisan Sole"
},
"offers": {
"@type": "Offer",
"url": "https://example.com/products/red-leather-ankle-boot",
"priceCurrency": "INR",
"price": "2499.00",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition",
"seller": { "@type": "Organization", "name": "Artisan Sole" }
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.5",
"reviewCount": "128"
}
}
</script>
OpenGraph and Social Metadata
<meta property="og:type" content="product" />
<meta property="og:title" content="Red Leather Ankle Boot — Artisan Sole" />
<meta property="og:image" content="https://example.com/images/boot-front.webp" />
<meta property="og:price:amount" content="2499.00" />
<meta property="og:price:currency" content="INR" />
<meta property="product:availability" content="in stock" />
Section 14: Security and Payment Rules (PCI DSS)
Payment security is non-negotiable. Loss of customer card data is a brand-ending event.
PCI DSS Baseline (Applicable to most ecommerce sites)
PCI DSS v4.0 is the current standard. Most ecommerce stores using a hosted payment gateway operate under SAQ A (the lightest self-assessment), provided:
- The payment page is entirely served by the gateway (iFrame, redirect, or hosted fields)
- No card data passes through your server at any point
- You store no card numbers, CVVs, expiry dates, or full PANs
Payment Architecture Rules
- Always use hosted fields or iFrame from your payment provider — Stripe Elements, Razorpay Standard Checkout, PayPal Hosted Fields, Braintree Drop-in UI
- Never create a custom card input form that posts data to your own server — this immediately puts you in scope for full PCI compliance
- HTTPS everywhere — not just checkout. Google penalizes HTTP pages for all ecommerce sites
- Content Security Policy (CSP) header must allow payment gateway scripts and block others
- Never log request bodies that could contain payment details even in transit
- Token, not card number: after authorization, store only the payment token returned by the gateway
- SCA / 3D Secure: required in EU/UK, best practice globally — Stripe Radar and Razorpay handle this automatically
Headers for Payment Page Security
Content-Security-Policy: default-src 'self'; script-src 'self' https://js.stripe.com; frame-src https://js.stripe.com;
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Referrer-Policy: strict-origin-when-cross-origin
Account Security Rules
- Passwords: minimum 12 characters, no forced periodic resets (NIST SP 800-63B)
- Offer MFA for customer accounts — required for admin accounts
- Rate-limit login attempts — lock or CAPTCHA after 5 failed attempts
- Store passwords with bcrypt, scrypt, or Argon2 — never MD5, SHA-1, or plain text
- Session tokens must be invalidated on logout and after password change
- Never expose order IDs or customer IDs in a sequential, guessable format — use UUIDs
Input Validation and XSS Prevention
- Sanitize all user-generated content before rendering in HTML — use
.textContent, not .innerHTML
- Validate and sanitize search queries, review text, and form inputs server-side
- Never trust client-side validation alone — always validate on the server
- Use parameterized queries — never string-concatenate SQL
Section 15: Design System Rules
An ecommerce store must feel like one coherent product across every page. Build a design system, not a collection of individual pages.
Color Tokens
:root {
--color-primary: #1A1A2E;
--color-accent: #E8160A;
--color-accent-hover: #C41009;
--color-bg: #FFFFFF;
--color-surface: #F5F5F7;
--color-border: #E0E0E0;
--color-text-primary: #1A1A1A;
--color-text-secondary: #6B7280;
--color-text-inverse: #FFFFFF;
--color-success: #16A34A;
--color-warning: #D97706;
--color-error: #DC2626;
--color-info: #2563EB;
--color-price: #1A1A1A;
--color-price-sale: #DC2626;
--color-price-original: #9CA3AF;
}
Typography Scale
:root {
--font-head: 'Playfair Display', serif;
--font-body: 'Inter', sans-serif;
--font-mono: 'DM Mono', monospace;
--text-xs: 0.64rem;
--text-sm: 0.8rem;
--text-base: 1rem;
--text-md: 1.25rem;
--text-lg: 1.563rem;
--text-xl: 1.953rem;
--text-2xl: 2.441rem;
--text-3xl: 3.052rem;
--leading-tight: 1.2;
--leading-normal: 1.5;
--leading-loose: 1.8;
}
Spacing Scale
:root {
--space-1: 4px;
--space-2: 8px;
--space-3: 12px;
--space-4: 16px;
--space-5: 24px;
--space-6: 32px;
--space-7: 48px;
--space-8: 64px;
--space-9: 96px;
--space-10: 128px;
}
Responsive Breakpoints
@media (min-width: 480px) { }
@media (min-width: 768px) { }
@media (min-width: 1024px) { }
@media (min-width: 1280px) { }
@media (min-width: 1536px) { }
Button System
.btn {
display: inline-flex;
align-items: center;
justify-content: center;
gap: var(--space-2);
padding: var(--space-3) var(--space-5);
border-radius: 6px;
font-family: var(--font-body);
font-size: var(--text-base);
font-weight: 600;
border: 2px solid transparent;
cursor: pointer;
transition: background 0.18s ease, transform 0.12s ease;
min-height: 44px;
min-width: 44px;
}
.btn:focus-visible {
outline: 3px solid var(--color-accent);
outline-offset: 3px;
}
.btn-primary {
background: var(--color-accent);
color: var(--color-text-inverse);
}
.btn-primary:hover { background: var(--color-accent-hover); transform: translateY(-1px); }
.btn-secondary {
background: transparent;
border-color: var(--color-border);
color: var(--color-text-primary);
}
.btn-secondary:hover { border-color: var(--color-accent); color: var(--color-accent); }
.btn-ghost {
background: transparent;
color: var(--color-text-secondary);
}
.btn-ghost:hover { color: var(--color-text-primary); background: var(--color-surface); }
Card System
.card {
background: var(--color-bg);
border: 1px solid var(--color-border);
border-radius: 10px;
overflow: hidden;
transition: box-shadow 0.2s ease, transform 0.2s ease;
}
.card:hover {
box-shadow: 0 8px 32px rgba(0,0,0,0.1);
transform: translateY(-3px);
}
@media (prefers-reduced-motion: reduce) {
.card:hover { transform: none; }
}
Section 16: Recommended Tech Stack
Core Stack (default for all HTML/static output)
- HTML5 — semantic structure, ARIA roles
- CSS3 — layout, design system tokens, animations
- JavaScript ES6+ — interactivity, state, API calls
Framework Options
| Framework | Best for |
|---|
| Next.js (React) | Full-stack, SEO-critical, large catalogs, headless Shopify/WooCommerce |
| Nuxt.js (Vue) | Simpler builds, Vue preference, SSR/SSG hybrid |
| SvelteKit | Maximum performance, lightweight bundle, modern projects |
| Astro | Content-heavy stores, maximum static performance, MPA architecture |
| Remix | Complex checkout flows, full-stack React with nested routes |
| Plain HTML/JS/CSS | Small catalog, static pages, prototypes, single-file demos |
Styling Options
| Tool | When to use |
|---|
| TailwindCSS | Rapid development, utility-first, consistent spacing |
| SCSS | Large projects, BEM methodology, design token management |
| CSS Modules | React/Vue component-scoped styles, zero leakage |
| CSS Custom Properties | Token system, theme switching, cross-component sharing |
Commerce Backend Options
| Backend | Best for |
|---|
| Shopify (Liquid or Hydrogen) | Full-featured store, fast to launch, built-in cart/payments |
| WooCommerce | WordPress-based stores, plugin ecosystem |
| Medusa.js | Open-source headless, full code control |
| Vendure | TypeScript headless commerce, B2B/B2C |
| Saleor | Python/Django headless, GraphQL-first |
| Custom API | Bespoke requirements, microservices architecture |
Payment Gateways
| Gateway | Region focus |
|---|
| Stripe | Global, developer-first, Stripe Elements for PCI SAQ A |
| Razorpay | India, UPI, netbanking, EMI support |
| PayPal / Braintree | Global, buyer trust, vaulted cards |
| Cashfree | India, fast settlements, subscription billing |
| Adyen | Enterprise, global acquiring, advanced fraud tooling |
Useful Libraries
| Library | Use |
|---|
| SWR / React Query | Product data fetching, stale-while-revalidate caching |
| Zustand / Jotai | Lightweight cart state management |
| Framer Motion | React animations, cart drawer, page transitions |
| GSAP | Complex scroll-driven animations, hero sequences |
| Swiper.js | Product image galleries, mobile carousels |
| Fuse.js | Client-side fuzzy search for small catalogs |
| html2canvas + jsPDF | Order receipt PDF generation |
| qrcode.js | QR code for order tracking, loyalty programs |
Section 17: Reusable Component Architecture
Build modular, occasion-independent components. Pass content as props/data — never hardcode.
Component Hierarchy
<Store>
├── <Header>
│ ├── <Logo />
│ ├── <NavMenu />
│ ├── <SearchBar />
│ └── <CartIcon /> ← shows item count badge
│
├── <PromoBanner /> ← dismissible top bar
│
├── <Page: Homepage>
│ ├── <HeroSection />
│ ├── <ValuePropositionStrip />
│ ├── <CategoryGrid />
│ ├── <ProductGrid title="Best Sellers" />
│ ├── <TrustBadgeRow />
│ └── <NewsletterSignup />
│
├── <Page: PLP>
│ ├── <FilterSidebar /> ← desktop
│ ├── <FilterDrawer /> ← mobile
│ ├── <SortDropdown />
│ ├── <ActiveFilterTags />
│ ├── <ProductGrid />
│ └── <Pagination /> or <LoadMoreButton />
│
├── <Page: PDP>
│ ├── <ProductGallery />
│ ├── <ProductInfo>
│ │ ├── <PriceBlock />
│ │ ├── <RatingBlock />
│ │ ├── <VariantSelector />
│ │ ├── <StockIndicator />
│ │ └── <AddToCartBar /> ← sticky version triggers on scroll
│ ├── <ProductDescription />
│ ├── <ReviewSection />
│ └── <RelatedProducts />
│
├── <CartDrawer /> ← offcanvas, slides in on add-to-cart
│
├── <Page: Checkout>
│ ├── <CheckoutForm />
│ │ ├── <ContactStep />
│ │ ├── <ShippingStep />
│ │ └── <PaymentStep /> ← hosted fields from gateway SDK only
│ └── <OrderSummaryPanel />
│
└── <Footer>
├── <FooterNav />
├── <PaymentIconRow />
└── <PolicyLinks />
Component Config Pattern
const STORE_CONFIG = {
name: 'Artisan Sole',
currency: 'INR',
currencySymbol: '₹',
locale: 'en-IN',
shippingThreshold: 999,
returnDays: 30,
supportEmail: 'support@artisansole.in',
socialLinks: {
instagram: 'https://instagram.com/artisansole',
facebook: 'https://facebook.com/artisansole'
},
paymentIcons: ['visa', 'mastercard', 'upi', 'rupay'],
theme: {
primaryColor: '#1A1A2E',
accentColor: '#E8160A',
fontHead: "'Playfair Display', serif",
fontBody: "'Inter', sans-serif"
}
};
Section 18: Code Snippet Library
Snippet 1: Product Card (accessible, semantic)
<article class="product-card" aria-label="Red Leather Ankle Boot — ₹2,499">
<div class="product-card__image-wrap">
<a href="/products/red-leather-ankle-boot" tabindex="-1" aria-hidden="true">
<img
src="boot-primary.webp"
data-hover-src="boot-secondary.webp"
alt="Red leather ankle boot, side view"
width="400" height="400"
loading="lazy"
class="product-card__img"
/>
</a>
<button class="product-card__wishlist" type="button" aria-label="Add Red Leather Ankle Boot to wishlist" aria-pressed="false">
</button>
<span class="product-card__badge" aria-label="20% discount">-20%</span>
</div>
<div class="product-card__body">
<h3 class="product-card__name">
<a href="/products/red-leather-ankle-boot">Red Leather Ankle Boot</a>
</h3>
<div class="product-card__rating" aria-label="Rating: 4.5 out of 5">
<span aria-hidden="true">★★★★½</span>
<span class="product-card__rating-count">(128)</span>
</div>
<div class="product-card__price">
<span class="price-current" aria-label="Current price: ₹2,499">₹2,499</span>
<span class="price-original" aria-label="Original price: ₹3,099"><s>₹3,099</s></span>
</div>
</div>
<button type="button" class="btn btn-primary product-card__cta">
Add to Cart
</button>
</article>
Snippet 2: Product Grid (responsive, CSS only)
.product-grid {
display: grid;
grid-template-columns: repeat(2, 1fr);
gap: var(--space-4);
}
@media (min-width: 768px) {
.product-grid { grid-template-columns: repeat(3, 1fr); }
}
@media (min-width: 1024px) {
.product-grid { grid-template-columns: repeat(4, 1fr); }
}
.product-card.is-loading .product-card__image-wrap {
background: linear-gradient(90deg, #F0F0F0 25%, #E0E0E0 50%, #F0F0F0 75%);
background-size: 200% 100%;
animation: skeleton-shimmer 1.4s ease infinite;
}
@keyframes skeleton-shimmer {
from { background-position: -200% 0; }
to { background-position: 200% 0; }
}
@media (prefers-reduced-motion: reduce) {
.product-card.is-loading .product-card__image-wrap { animation: none; }
}
Snippet 3: Cart Drawer (WAAPI animated)
<div class="cart-drawer" id="cartDrawer" role="dialog" aria-modal="true" aria-label="Shopping cart" hidden>
<div class="cart-drawer__overlay" id="cartOverlay"></div>
<div class="cart-drawer__panel">
<div class="cart-drawer__header">
<h2 class="cart-drawer__title">Your Cart (<span id="cartCount">0</span>)</h2>
<button type="button" id="cartClose" aria-label="Close cart">✕</button>
</div>
<div class="cart-drawer__items" id="cartItems" role="list"></div>
<div class="cart-drawer__footer">
<div class="cart-drawer__subtotal">
<span>Subtotal</span>
<strong id="cartSubtotal">₹0</strong>
</div>
<a href="/checkout" class="btn btn-primary cart-drawer__checkout">Proceed to Checkout</a>
<button type="button" class="btn btn-ghost cart-drawer__continue" id="cartContinue">Continue Shopping</button>
</div>
</div>
</div>
const cartDrawer = document.getElementById('cartDrawer');
const cartPanel = cartDrawer.querySelector('.cart-drawer__panel');
let lastFocus = null;
let drawerAnim = null;
async function openCart() {
lastFocus = document.activeElement;
cartDrawer.hidden = false;
cartDrawer.removeAttribute('hidden');
if (drawerAnim) drawerAnim.cancel();
cartPanel.style.willChange = 'transform';
drawerAnim = cartPanel.animate(
[{ transform: 'translateX(100%)' }, { transform: 'translateX(0)' }],
{ duration: 280, easing: 'cubic-bezier(0.4, 0, 0.2, 1)', fill: 'forwards' }
);
await drawerAnim.finished;
cartPanel.style.willChange = 'auto';
document.getElementById('cartClose').focus();
trapFocus(cartDrawer);
}
async function closeCart() {
if (drawerAnim) drawerAnim.cancel();
cartPanel.style.willChange = 'transform';
drawerAnim = cartPanel.animate(
[{ transform: 'translateX(0)' }, { transform: 'translateX(100%)' }],
{ duration: 220, easing: 'cubic-bezier(0.4, 0, 0.2, 1)', fill: 'forwards' }
);
await drawerAnim.finished;
cartPanel.style.willChange = 'auto';
cartDrawer.hidden = true;
if (lastFocus) lastFocus.focus();
}
function trapFocus(container) {
const focusable = container.querySelectorAll(
'a[href], button:not([disabled]), input, select, textarea, [tabindex]:not([tabindex="-1"])'
);
const first = focusable[0];
const last = focusable[focusable.length - 1];
container.addEventListener('keydown', function handler(e) {
if (e.key !== 'Tab') return;
if (e.shiftKey && document.activeElement === first) { e.preventDefault(); last.focus(); }
else if (!e.shiftKey && document.activeElement === last) { e.preventDefault(); first.focus(); }
if (cartDrawer.hidden) container.removeEventListener('keydown', handler);
});
}
document.getElementById('cartClose').addEventListener('click', closeCart);
document.getElementById('cartOverlay').addEventListener('click', closeCart);
document.addEventListener('keydown', e => { if (e.key === 'Escape') closeCart(); });
Snippet 4: Sticky Add-to-Cart Bar (Intersection Observer)
const mainATCBtn = document.getElementById('mainAddToCart');
const stickyBar = document.getElementById('stickyAddToCart');
const observer = new IntersectionObserver(
([entry]) => {
stickyBar.classList.toggle('is-visible', !entry.isIntersecting);
stickyBar.setAttribute('aria-hidden', String(entry.isIntersecting));
},
{ threshold: 0 }
);
observer.observe(mainATCBtn);
.sticky-atc {
position: fixed;
bottom: 0; left: 0; right: 0;
background: var(--color-bg);
border-top: 1px solid var(--color-border);
padding: var(--space-3) var(--space-5);
display: flex; align-items: center; justify-content: space-between;
gap: var(--space-4);
z-index: 50;
translate: 0 100%;
transition: translate 0.25s cubic-bezier(0.4, 0, 0.2, 1);
}
.sticky-atc.is-visible { translate: 0 0; }
@media (prefers-reduced-motion: reduce) {
.sticky-atc { transition: none; }
}
Snippet 5: Filter Sidebar with Active Tags
function getFilters() {
const params = new URLSearchParams(window.location.search);
const filters = {};
for (const [key, val] of params) {
filters[key] = filters[key] ? [...filters[key], val] : [val];
}
return filters;
}
function setFilter(key, value, checked) {
const params = new URLSearchParams(window.location.search);
const current = params.getAll(key);
if (checked) {
if (!current.includes(value)) params.append(key, value);
} else {
params.delete(key);
current.filter(v => v !== value).forEach(v => params.append(key, v));
}
params.delete('page');
history.pushState({}, '', `?${params.toString()}`);
fetchProducts(params);
}
function removeFilter(key, value) { setFilter(key, value, false); }
Snippet 6: Lazy Image with WebP + Fallback
<picture>
<source
srcset="product-800.webp 800w, product-400.webp 400w"
type="image/webp"
sizes="(max-width: 768px) 400px, 800px"
/>
<img
src="product-800.jpg"
srcset="product-800.jpg 800w, product-400.jpg 400w"
sizes="(max-width: 768px) 400px, 800px"
alt="Red leather ankle boot, three-quarter front view"
width="800" height="800"
loading="lazy"
decoding="async"
/>
</picture>
Snippet 7: Stripe Elements Payment Integration (PCI SAQ A)
<div id="payment-element"></div>
<button type="submit" id="submit-payment" class="btn btn-primary">Pay ₹2,499</button>
<div id="payment-error" role="alert" aria-live="assertive"></div>
const stripe = Stripe('pk_live_YOUR_PUBLISHABLE_KEY');
const elements = stripe.elements({ clientSecret: 'CLIENT_SECRET_FROM_SERVER' });
const paymentEl = elements.create('payment');
paymentEl.mount('#payment-element');
document.getElementById('submit-payment').addEventListener('click', async (e) => {
e.preventDefault();
const { error } = await stripe.confirmPayment({
elements,
confirmParams: {
return_url: 'https://yourstore.com/order-confirmation'
}
});
if (error) {
document.getElementById('payment-error').textContent = error.message;
}
});
Snippet 8: Search Autocomplete (debounced, accessible)
const searchInput = document.getElementById('searchInput');
const searchResults = document.getElementById('searchResults');
let debounceTimer = null;
searchInput.addEventListener('input', (e) => {
clearTimeout(debounceTimer);
const query = e.target.value.trim();
if (!query) { closeResults(); return; }
debounceTimer = setTimeout(async () => {
const results = await fetchSearchSuggestions(query);
renderSuggestions(results);
}, 250);
});
function renderSuggestions(results) {
searchResults.innerHTML = '';
if (!results.length) { closeResults(); return; }
const list = document.createElement('ul');
list.setAttribute('role', 'listbox');
list.setAttribute('aria-label', 'Search suggestions');
results.forEach((item, i) => {
const li = document.createElement('li');
li.setAttribute('role', 'option');
li.setAttribute('id', `suggestion-${i}`);
li.textContent = item.title;
li.addEventListener('click', () => navigateTo(item.url));
list.appendChild(li);
});
searchResults.appendChild(list);
searchResults.hidden = false;
searchInput.setAttribute('aria-expanded', 'true');
searchInput.setAttribute('aria-owns', 'searchResults');
}
function closeResults() {
searchResults.hidden = true;
searchInput.setAttribute('aria-expanded', 'false');
}
document.addEventListener('click', e => {
if (!searchInput.contains(e.target) && !searchResults.contains(e.target)) closeResults();
});
Snippet 9: Variant Image Swap
document.querySelectorAll('[data-variant-select]').forEach(btn => {
btn.addEventListener('click', () => {
const variantId = btn.dataset.variantId;
const variantData = PRODUCT_VARIANTS[variantId];
document.querySelector('.gallery-main').src = variantData.images[0];
document.querySelector('.gallery-main').alt = variantData.alt;
document.querySelectorAll('.gallery-thumb').forEach((thumb, i) => {
thumb.src = variantData.images[i] || variantData.images[0];
});
document.querySelector('.price-current').textContent = formatPrice(variantData.price);
const stockEl = document.querySelector('.stock-status');
stockEl.textContent = variantData.inStock ? 'In Stock' : 'Out of Stock';
stockEl.dataset.status = variantData.inStock ? 'in' : 'out';
const atcBtn = document.querySelector('[data-add-to-cart]');
atcBtn.disabled = !variantData.inStock;
atcBtn.setAttribute('aria-disabled', String(!variantData.inStock));
history.replaceState({}, '', `?variant=${variantId}`);
document.querySelectorAll('[data-variant-select]').forEach(b => b.setAttribute('aria-pressed', 'false'));
btn.setAttribute('aria-pressed', 'true');
});
});
Snippet 10: Order Summary with CLS-Safe Loading
function renderOrderSummary(items, shipping, total) {
const container = document.getElementById('orderSummary');
const frag = document.createDocumentFragment();
items.forEach(item => {
const row = document.createElement('div');
row.className = 'order-row';
row.querySelector('.order-row__name').textContent = item.name;
row.querySelector('.order-row__qty').textContent = `× ${item.qty}`;
row.querySelector('.order-row__price').textContent = formatPrice(item.price * item.qty);
frag.appendChild(row);
});
container.appendChild(frag);
document.getElementById('orderShipping').textContent =
shipping === 0 ? 'Free' : formatPrice(shipping);
document.getElementById('orderTotal').textContent = formatPrice(total);
}
Section 19: Industry Adaptation Guide
Adapt every section of the store experience to fit the product vertical.
| Industry | Hero Style | Key PDP Element | Trust Signal | Speed Priority |
|---|
| Fashion | Editorial lifestyle photography | Model imagery + size guide | Try-on returns policy | Image CDN critical |
| Electronics | Clean product on white | Technical specs + comparison | Warranty + spec accuracy | Bundle optimization |
| Beauty | Aesthetic, model-focused | Shade selector + ingredients | "Clean" certifications | Smallest image sizes |
| Grocery | Category-first landing | Nutrition info + quantity | Freshness guarantee | INP critical — list updates |
| Furniture | Room-scene photography | Dimensions + delivery date | Showroom option | LCP critical — large images |
| Luxury | White space, editorial | Single product, no grid | Brand heritage + craft story | Minimal JS |
| Handmade | Warm, artisanal images | Story of the maker + materials | Small-batch badge | Web fonts performance |
| Sports | Action photography | Activity type + performance specs | Athlete endorsement | Animation performance |
| Health | Clean, clinical trust | Ingredients + certifications | Medical/expert endorsement | Accessibility priority |
| Food & Bev | Appetite-focused close-ups | Allergens + flavor selector | Origin + farm story | Mobile speed first |
Section 20: Variation Rules
When generating multiple store concepts or page variations:
- Variation A — Conversion-safe: proven layout, minimal risk, maximum clarity
- Variation B — Modern bold: stronger visual hierarchy, experimental layout zone
- Variation C — Premium / brand-forward: more white space, story-first, editorial feel
Each variation must differ in:
- Layout structure and information density
- Image/text proportion
- Color weight and distribution
- Button style and CTA placement
- Motion level (none / subtle / expressive)
- Font role (utilitarian vs. expressive)
Never submit a variation that is only a color swap of another.
Section 21: Output Format
For every ecommerce request, provide:
- Business and brand summary — what is being sold, to whom, at what price point
- Recommended site structure — pages and navigation hierarchy
- Homepage concept — hero, sections, content hierarchy
- Category / PLP concept — grid, filter, sort layout
- Product page (PDP) concept — media, info, CTA, trust zones
- Cart and checkout concept — flow, form structure, payment zone
- Design system summary — tokens, typography, color palette
- Tech stack recommendation — framework, payment gateway, libraries
- Component plan — which reusable components are needed
- Code snippets — if implementation output is requested
- Accessibility checklist — WCAG 2.2 items specific to this store
- Performance checklist — Core Web Vitals targets and optimizations
- Security checklist — PCI DSS scope; payment, account, input safety
- Variation set — if multiple design directions requested
Section 22: Latest Ecommerce Practices Update
This section is refreshed with current guidance from authoritative sources. Do not overwrite core rules — append here when new recommended practices emerge.
Performance — Core Web Vitals (2024–2026 State)
Accessibility — WCAG 2.2 New Criteria (2023)
New success criteria added in WCAG 2.2 that directly affect ecommerce:
| Criterion | Requirement | Impact on Ecommerce |
|---|
| 2.4.11 Focus Appearance (AA) | Focus indicator must have 3:1 contrast and 2px area | All form fields, buttons, links |
| 2.5.7 Dragging Movements (AA) | All drag interactions need a pointer-only alternative | Range sliders (price filter), sortable lists |
| 2.5.8 Target Size Minimum (AA) | Touch targets ≥ 24×24 CSS px | All mobile buttons, filter checkboxes |
| 3.2.6 Consistent Help (A) | Help links in same rel. position on every page | FAQs, chat widget, support phone |
| 3.3.7 Redundant Entry (A) | Don't ask for data already entered in same flow | Billing = shipping checkbox |
| 3.3.8 Accessible Authentication (AA) | No cognitive test (CAPTCHA) without accessible alternative | Login, checkout, account creation |
Payment Security — PCI DSS v4.0 (March 2025 mandatory)
PCI DSS v4.0 became the only active standard in March 2025. Key changes for ecommerce:
- Requirement 6.4.3: All JavaScript on the payment page must be authorized, integrity-checked (
integrity="" attribute on <script> tags), and have a documented justification for its presence. Applies to ALL scripts on the checkout page — including analytics, chat, and third-party widgets.
- Requirement 11.6.1: Tamper-detection mechanism must alert on unauthorized changes to the payment page's HTTP headers or scripts. Implement via CSP + reporting, or a dedicated PCI-approved solution.
- Requirement 8.3.6: Minimum password length raised to 12 characters (was 7). Enforce on customer accounts and require for admin accounts immediately.
- Requirement 12.3.2: All third-party software used in the cardholder data environment must be risk-assessed annually.
Practical action for most ecommerce stores:
- Set a strict
Content-Security-Policy that allowlists only necessary payment scripts
- Add
integrity SRI attributes to all checkout-page script tags
- Audit every script loaded on the checkout page — remove anything not essential
- Use gateway-hosted payment pages (redirect or iFrame) to remain in SAQ A scope
Google Merchant Center and Product Data (2025)
- Mismatched prices between Merchant Center feed and landing page will suspend your Shopping ads — real-time price sync is mandatory for stores running paid Shopping campaigns.
- Structured data (schema.org
Product) is now surface-level for Google Search's AI Overviews — accurate product markup improves visibility in AI-generated shopping results.
- Return policy structured data (
MerchantReturnPolicy) can be added to schema, reducing the return policy clarification burden in Google Shopping.
- Product availability values: use
InStock, OutOfStock, PreOrder, BackOrder — keep these in sync with actual inventory; Google audits for discrepancies.
- Image quality: Merchant Center now rejects images smaller than 100×100 px; recommended minimum for Shopping ads is 800×800 px.
Mobile Ecommerce (2025 Patterns)
- Bottom navigation bar (mobile): position primary nav at the bottom of the screen for thumb reachability — Home, Search, Wishlist, Cart, Account
- Swipeable product cards: horizontal scrolling product rows should use
scroll-snap-align: start for predictable snap behavior
- One-thumb checkout: payment methods like UPI, Apple Pay, Google Pay must appear as the TOP payment option on mobile — they require zero form filling
- Progressive Web App (PWA): install prompt increases repeat purchase rate;
manifest.json + service worker required
- Reduced data mode: respect
prefers-reduced-data (experimental) — serve smaller images when detected
Checkout UX Patterns (2025 Best Practices)
- One-page checkout outperforms multi-step for most stores under 5 product variants — consolidate into a single scrollable form
- Address autofill with Places API: integrate Google Places Autocomplete on address field for near-zero-error address entry
- Buy Now Pay Later (BNPL): Klarna, Simpl, or Lazypay display at the price point increases AOV for mid-range stores; show monthly breakdown on PDP
- Express checkout strip: show PayPal, Google Pay, and Apple Pay buttons before the address form — this is the fastest path to purchase for repeat buyers
- Abandoned checkout recovery: abandoned checkout emails within 1 hour recover the most sessions — requires email captured at beginning of checkout flow (even before address)
Section 23: What to Avoid
Never:
- Make navigation confusing or inconsistent across pages
- Clutter the homepage with competing messages or auto-rotating banners
- Hide critical product information behind a "Read More" toggle
- Use weak or vague CTAs ("Submit", "Go", "Click Here")
- Force account creation before checkout
- Show surprise fees at payment — always show total cost before the payment step
- Ignore mobile users — test every interaction on a real mobile device
- Use unreadable typography (light grey on white, tiny font sizes, decorative fonts for body text)
- Omit trust signals — a store without reviews, policies, and contact info loses sales
- Use misleading product titles or prices that don't match the feed
- Break WCAG 2.2 accessibility rules — this affects both users and legal risk
- Animate layout-triggering properties (
width, height, margin, top, left)
- Handle raw card data on your own server — always use a gateway-hosted payment element
- Use
innerHTML with user-provided content — always sanitize or use textContent
- Deploy third-party scripts on the checkout page without auditing and CSP coverage
Section 24: Designer and Developer Thinking Framework
Before creating any ecommerce page or component, work through this checklist:
Business
- What is being sold?
- Who is the target buyer and what are they looking for?
- What makes this brand different from competitors?
- What is the fastest path from landing to purchase?
Design
- What emotional tone should the page carry?
- What content increases trust for this specific buyer?
- What layout creates the clearest hierarchy toward the CTA?
- What design system decisions keep the store coherent?
Engineering
- What is the LCP element — is it in the initial HTML and preloaded?
- Are all images lazy-loaded below the fold with explicit dimensions?
- Is every form field labeled, validated accessibly, and autofill-attributed?
- Does the payment flow use a PCI-compliant hosted element?
- Is all user-supplied content rendered with
.textContent, not .innerHTML?
Review
- Is the result fast, clear, and shoppable on a mid-range mobile device?
- Does it pass keyboard-only navigation from homepage to checkout?
- Does it meet WCAG 2.2 AA contrast and target size minimums?
An ecommerce site is not just a storefront.
It is a trust system that moves people from curiosity to confidence to purchase.
Every pixel, every word, every millisecond of load time either earns that trust or erodes it.
Skill file: ecommerce-website.md — Performance: Core Web Vitals (LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1). Accessibility: WCAG 2.2 AA. Payment security: PCI DSS v4.0 SAQ A via hosted gateway fields. Product data: Google Merchant Center accuracy and schema.org Product markup. Updated May 2026.
