Skip to main content

Plum vs Pear: shared flavor compounds

283 of 464 flavor compounds are shared (Jaccard 0.61) — the molecular basis for whether Plum and Pear pair well or work as substitutes. Full side-by-side breakdown below.

1
2

Two ingredients gives the full side-by-side breakdown; add a third to see a similarity matrix across all of them (up to 6).

283
Shared
384
Plum reported
363
Pear reported
0.61
Jaccard

“Reported” counts reflect the compounds characterized for each ingredient across the studies and databases we aggregate — a measure of coverage, not an exhaustive census. Different analyses target different compound classes and methods, so read these as what has been characterized, not the total number of molecules present. Jaccard measures shared coverage, so it rewards overlap rather than highlighting the ratio differences that distinguish two ingredients.

Why they pair: shared-compound network

12 of 283 shared shown

Each molecule in the middle is shared by both ingredients — the chemistry bridging Plum and Pear. Node color is chemical class and node size is perceptual potency (bigger = lower odor threshold, so it drives aroma at smaller amounts); a copper ring marks compounds flagged as key aromas in published GC-O studies. Zoom with the +/− buttons or a pinch, drag the background to pan, drag a node to pin it, click any molecule for its full profile.

Showing the 12 highest-impact of 283 shared compounds (key aromas first). Sign in for the full network, including the compounds unique to each ingredient.

Where they differ: aroma character

Profile distance 0.04

The Jaccard above measures overlap; this compares each ingredient’s aroma-family mix side by side — the wider the gap between the two bars, the more that family sets the ingredients apart. Plum reads left, Pear reads right.

8.9%
Green
7.5%
14.7%
Sour
16.0%
3.2%
Spicy
4.2%
4.3%
Woody
3.3%
12.6%
Floral
11.7%
5.2%
Herbal
6.0%
24.7%
Fruity
25.3%
5.2%
Roasted
4.8%
2.0%
Sulfurous
2.4%
12.9%
Other
12.7%
Plum ◀ ▶ Pear

Shares are fractions of each ingredient’s labeled compounds (347 of 384 for Plum, 331 of 363 for Pear) — compositional lean, not concentration. Aroma labels come from our compound enrichment and cover most, but not all, characterized molecules.

Pro names the molecules behind each difference — the specific compounds in each aroma family that one ingredient has and the other doesn’t. Sign in to see them.

Published recipes using both

1 found

Real dishes from our 610K+ curated recipe corpus that combine plum and pear — proof the pairing works in practice.

Shared compounds

283 of 464 total

These are the molecules both ingredients have in common — the chemistry behind why they pair. Grouped by chemical class; ★ marks compounds flagged as key aromas in published GC-O studies. Click any molecule for its identifiers (CAS, formula, PubChem CID), odor data, and every ingredient it’s found in.

Most perceptually potent shared compounds

196 of 283 shared are aroma compounds with a measured threshold

Odor threshold is the concentration at which a molecule becomes smellable — lower = more potent. These clear their threshold most easily, so they drive the shared aroma out of proportion to the raw shared count.

Showing the 6 most potent of 196 with measured thresholds. Sign in for the full ranked list.

Showing the 5 highest-impact of 283 shared compounds (key aromas first) — sign in for the full list, grouped by chemical class with key-aroma markers.

See 101 plum-only and 80 pear-only compounds with Pro

Side-by-side ingredient comparison — including the unique compounds in each ingredient — is a Pro feature.

Try the pairing tools for full recipe-aware scoring, or explore plum's profile.

Cite this analysis
Plain text
Compound Kitchen (2026). Compound similarity analysis: Plum vs Pear. https://compkitchen.com/compare?a=plum&b=pear. Accessed 2026-09-28.
BibTeX
@misc{compkitchen_compare_compound_similarity_analysis_plum_vs_pear_2026,
  title  = {Compound similarity analysis: Plum vs Pear},
  author = {{Compound Kitchen}},
  year   = {2026},
  url    = {https://compkitchen.com/compare?a=plum&b=pear},
  note   = {Accessed: 2026-09-28}
}

Methodology DOI: 10.5281/zenodo.19719459 · CC BY 4.0 · Citations are a request, not a requirement.