Dunkin' Fluffernutter Coffee Chiller Nutrition Facts

Which Fluffernutter product does this page cover?

This page covers the Fluffernutter Coffee Chiller, a single product family with exact Small, Medium, and Large records in the frozen dataset. It does not use a brand-level or flavor-only total, and it does not merge another Fluffernutter preparation into the three-row comparison. Keeping the sizes together lets a reader answer the named-product question first, compare cups second, and avoid a separate thin page for every exact source serving.

The page does not broaden the phrase to every Fluffernutter-named drink. The JSON also contains Fluffernutter Cloud Latte rows, but “Cloud Latte” is a different source item name and therefore a different preparation. Keeping it out of the Coffee Chiller table is a data-quality decision: a similar flavor label does not authorize one recipe's calories, sugar, fat, or serving size to stand in for another.

Small is a complete source row

Fluffernutter Coffee Chiller - Small (Small) lists 600 calories, 6g protein, 84g carbohydrate, 26g fat, 160mg sodium, 72g total sugar, and 66g added sugar. The record id is dunkin-0005, and every nutrient shown for Small is read from that object. The page does not describe Small as a fraction of another cup because no proportional recipe statement appears in the JSON.

A focused result should preserve the scale of the printed serving without editorial euphemisms. Calories are displayed beside carbohydrate, fat, sodium, total sugar, added sugar, and protein so the Small label does not conceal the rest of the source profile. The table is descriptive rather than a claim that the drink fits a particular diet or daily target.

Medium answers the most common unqualified comparison

Fluffernutter Coffee Chiller - Medium (Medium) lists 860 calories, 8g protein, 123g carbohydrate, 37g fat, 240mg sodium, 105g total sugar, and 97g added sugar. This Medium row maps to dunkin-0004. The page does not silently choose Medium as the universal answer; it marks Medium explicitly and keeps Small and Large within the same comparison.

That distinction matters because a search result snippet can otherwise present one calorie or sugar value without the serving that gives it meaning. Here the product name, size label, and record id appear before the nutrition fields. A reader can use Medium when it matches the order and reject it immediately when another cup was purchased.

Large remains separate from the other Chiller sizes

Fluffernutter Coffee Chiller - Large (Large) lists 1140 calories, 11g protein, 163g carbohydrate, 49g fat, 320mg sodium, 140g total sugar, and 128g added sugar. The source pointer for this row is dunkin-0003. Large is not extrapolated from Medium, and Medium is not back-calculated from Large; all three objects were extracted independently from the source table.

Presenting the three rows together reveals the practical cost of dropping the size qualifier from a query. The product family alone does not select a unique nutrition total. The correct answer needs both “Fluffernutter Coffee Chiller” and one of the published serving labels, which is why the page title promises nutrition facts by product while the table carries the actual size decision.

Coffee Chiller and Cloud Latte must not be merged

The word “Fluffernutter” is not a nutritional identifier by itself. In the frozen file it appears in both Coffee Chiller and Cloud Latte names, and each family has its own Small, Medium, and Large objects. Combining them would create a six-row set that answers two preparations and could send a searcher to the wrong recipe.

This page therefore requires the “Coffee Chiller” portion of the query to match. If an order receipt or current menu says “Fluffernutter Cloud Latte,” the reader should return to the full table and use that exact name instead. The site does not infer that “chiller” is an informal synonym for “latte,” and it does not average the two product families.

Total sugar and added sugar are different source fields

The Dunkin' dataset retains total sugar and added sugar separately for each Chiller size. Both appear in the table because they answer different label questions. The page does not subtract one to invent a naturally occurring sugar amount, and it does not describe total sugar as though the entire value were necessarily added.

Carbohydrate, fat, protein, and sodium remain visible for the same reason. A searcher may begin with nutrition facts or calories, but the source row contains more than one headline. Showing the full group guards against a snippet-like reading in which a single value is remembered while the serving and preparation disappear.

No customization arithmetic is hidden in the page

The selected records describe named source preparations. Removing a topping, changing milk, reducing a flavor component, adding espresso, or ordering a different frozen drink may change the result, but the JSON does not provide a reliable subtraction rule for those actions. The page makes no such adjustment and does not present a custom total as restaurant-published data.

The same caution applies to sharing a cup or consuming only part of it. A reader can perform personal arithmetic, yet a fraction would be a derived estimate rather than a new official serving. ChainMenu keeps the source serving intact and avoids relabeling a calculated fraction as a product nutrition fact.

Visible record ids provide the audit trail

The three identifiers dunkin-0005, dunkin-0004, and dunkin-0003 connect the HTML back to data/dunkin.json. Generation reads those objects directly for the comparison table, the JSON-LD nutrition fields, and the numeric facts in this prose. No nutrition value is typed into a separate page-specific data file.

To verify a row, locate its id in the JSON and compare the name, serving size, source page, source table row, and nutrient fields. That workflow catches a preparation mismatch before it becomes an SEO claim. It also makes later updates safer because a changed source record can be traced without guessing which visually similar drink a number once represented.

How to use the result responsibly

Match the full product name first, then select the cup size. If the current menu uses another name, if the drink was customized, or if the location does not offer the archived preparation, do not borrow the closest-looking row. The broad Dunkin' table remains the fallback for finding another exact record, and the restaurant remains the authority for current recipe and availability information.

The frozen PDF was retrieved on August 17, 2026. It can document the values used for this page but cannot guarantee later formulations or local execution. Ingredient, allergen, and caffeine questions extend beyond the displayed nutrition fields, while personal dietary advice extends beyond the role of an independent reference page.

Frequently asked questions