---
title: "Pricing table"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/PricingTable"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/PricingTable"
source_slug: "PricingTable"
track: "User Interface Design Patterns"
group: "Miscellaneous"
subgroup: "Shopping"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Apply hooks"
  - "Highlight why users should pay for your product"
  - "First one free"
  - "Order plans by descending price"
  - "Add decoys"
  - "The Goldilocks effect: We are aversive toward extremes"
  - "Let people know what they’re missing"
  - "Showcase differences with extremes"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Pricing table

> Catalog pointer for the UI Patterns source page: [Pricing table](https://ui-patterns.com/patterns/PricingTable).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Miscellaneous
- Subgroup: Shopping
- Source breadcrumb: Design Patterns > Miscellaneous > Shopping > Pricing table

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/PricingTable
- Page title: Pricing table design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Apply hooks, Highlight why users should pay for your product, First one free, Order plans by descending price, Add decoys, The Goldilocks effect: We are aversive toward extremes, Let people know what they’re missing, Showcase differences with extremes
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 83 words on source page
- Usage: 82 words on source page
- Solution: 233 words on source page
- Rationale: 33 words on source page
- Discussion: 840 words on source page
- Apply hooks: 308 words on source page
- Highlight why users should pay for your product: 59 words on source page
- First one free: 61 words on source page
- Order plans by descending price: 95 words on source page
- Add decoys: 30 words on source page
- The Goldilocks effect: We are aversive toward extremes: 102 words on source page
- Let people know what they’re missing: 34 words on source page
- Showcase differences with extremes: 42 words on source page

## Source Navigation

- Previous source navigation: Competition
- Next source navigation: Product page
