Every Wearable Now Tracks Your Food — None of Them Build Your Race-Day Plan

2026: The Year Your Watch Learned to Count Calories

Garmin kicked things off at CES in January. Connect+ subscribers can now scan barcodes, snap photos of their meals, and track calories and macros alongside training data. A few weeks later, Apple leaked plans for camera-based food logging in iOS 26.4, letting Apple Watch and iPhone users do the same thing without leaving the Health app.

For the first time, both major wearable platforms want to own nutrition. And if you're training for a fall marathon right now, that sounds like it should solve your fueling problem.

It doesn't.

What Food Tracking Actually Gives You

Here's what Garmin Connect+ nutrition tracking does well. It logs your daily calorie intake. It breaks down protein, fat, and carbohydrates. It compares what you consumed against what you burned. It gives you AI-generated insights about how your diet might be affecting recovery.

That's useful information. If you're trying to lose weight, maintain energy balance, or understand whether you're eating enough protein, food tracking is a genuine step forward.

But none of that helps you on race morning.

The Gap Nobody's Filling

When you're standing at the start line of the Chicago Marathon on October 11, you need answers to very specific questions:

• How much fluid should you drink per hour, given the forecasted temperature and your personal sweat rate?
• When should you take your first gel — at 30 minutes? 45? Based on what?
• How many grams of carbohydrate per hour can your gut actually absorb without sending you to the portaloos?
• If conditions are cooler than your summer training, should you reduce your fluid intake — and by how much?
• What happens at mile 18 when you're behind pace and your original plan no longer fits?

Garmin can't answer any of these. Neither can Apple Health. Neither can TrainingPeaks, even after integrating hDrop's sweat-loss data earlier this year. They all collect data. None of them turn it into a plan.

Your Watch Already Has the Data — It Just Doesn't Use It

This is the frustrating part. Your Garmin or Apple Watch already tracks the inputs a fueling plan needs:

Heart rate and training load tell you how hard you're working and how much glycogen you're burning. A higher heart rate means more carbohydrate oxidation, which means you need more fuel per hour.

Sweat loss estimates (Garmin added these with the Forerunner 965 and fēnix 8) tell you roughly how much fluid you're losing per session. That's the starting point for a hydration schedule.

Pace and duration data from Strava and your watch tell you how long you'll be out there and at what intensity. A 3:15 marathon and a 4:45 marathon have radically different fueling needs — but most generic advice treats them the same.

Environmental data like temperature and humidity affect sweat rate, gel absorption, and stomach tolerance. Your watch logs the conditions of every training run, building a picture of how you respond in different environments.

All of this data exists. It's sitting in your Garmin Connect dashboard or Apple Health right now. But the platforms treat nutrition and performance as separate categories. Your food log lives in one tab. Your training data lives in another. Nobody connects them.

Why a Food Diary Is Not a Fueling Plan

Think of it this way. A food diary is backward-looking: it records what you ate. A fueling plan is forward-looking: it tells you what to eat, how much, and when — based on your body, your pace, your race, and the conditions.

Logging that you had porridge and a banana at 6am on race morning is food tracking. Knowing that at your sweat rate and target pace, you need 650ml of fluid and 70g of carbohydrate per hour, starting your first gel at the 8km mark and switching to a higher-sodium drink after the halfway point because temperature is forecast to rise — that's a fueling plan.

One is a record. The other is a decision engine.

The TrainingPeaks Problem

TrainingPeaks deserves a mention here because it's the platform most serious endurance athletes already use for training load management. In January 2026, TrainingPeaks integrated with hDrop to sync sweat loss, sodium loss, and hydration behaviour directly into workout notes.

That's a step in the right direction. But the data lands in your post-workout analysis. It tells you what happened. It doesn't project forward to tell you what should happen on race day. And TrainingPeaks' own nutrition content — articles like "Summer Hydration Tips" and "Nutrition 101" — remains generic. It's education, not personalisation.

The same gap applies to Nix, which announced a partnership with Baylor University in April 2026 to use its biosensor patches for collegiate athletic programmes. Nix produces excellent real-time sweat data. But you need a $200+ starter kit, single-use patches for every session, and the output is still data, not a plan. For most recreational athletes training for their next half or full marathon, it's overkill.

What "Personalised" Actually Means

When the Garmin press release says "personalised calorie and macronutrient recommendations based on height, weight, gender, activity level, and average active calories," that's a nutrition calculator. It gives you daily targets. That's a start.

But personalised race-day fueling means something different entirely. It means:

Your sweat rate, not an average. Two runners of the same weight can have sweat rates that differ by 50%. A plan built on population averages will over-hydrate one and under-hydrate the other.

Your gut tolerance, not the pro standard. The 90g-per-hour carbohydrate target that dominates endurance nutrition advice right now is designed for elite athletes who've spent months training their gut. If you're running a 4:30 marathon and you've never gut-trained, 90g/hr will likely wreck your stomach. Your plan should start from your tested ceiling, not the theoretical maximum.

Your race, not a template. A flat, cool-morning half marathon and a hilly, hot-afternoon Ironman bike leg need fundamentally different fueling approaches. A generic "take a gel every 45 minutes" rule ignores the variables that actually determine whether you bonk or finish strong.

Your training data, not a questionnaire. Every long run you've logged is a data point. Your pace, heart rate, perceived effort, and conditions together paint a picture of how your body responds to sustained exercise. A fueling plan should learn from those sessions, not from a five-question onboarding quiz.

The Missing Layer

The wearable platforms have the data layer covered. Garmin, Apple, and Strava between them capture heart rate, pace, distance, elevation, training load, recovery metrics, and now food intake. That's more data than any athlete has ever had access to.

What's missing is the intelligence layer — the thing that sits between your data and your race-day decisions. The layer that takes your Garmin sweat estimate, your average long-run heart rate, your planned race pace, and the weather forecast, and turns them into: drink 550ml per hour, take your first gel at 7km, switch to a high-sodium option at halfway, and carry one emergency gel for the final 10km.

That's not a dashboard. It's not a food diary. It's a decision engine.

Sweatr was built to be that layer. It connects to your Apple Watch, Garmin, and Strava, pulls your training data, and builds a personalised hydration and fueling plan for your specific race. Not based on averages. Based on your numbers.

When the temperature drops for your October race and your sweat rate shifts, your plan adjusts. When your training load changes in the final taper weeks, your carbohydrate targets recalibrate. When you enter your goal pace, the plan accounts for the intensity-specific fuel demands.

Your watch collects the data. Sweatr tells you what to do with it.

What to Do This Week

If you're racing in the next two weeks, here's how to bridge the gap right now:

Step 1: Know your sweat rate. Weigh yourself before and after a 60-minute run in conditions similar to race day. The difference (in grams) plus whatever you drank equals your hourly sweat loss. Divide by 60 for your per-minute rate.

Step 2: Set a carbohydrate target based on YOUR gut, not the internet. If you haven't gut-trained, start at 40-50g per hour for a half marathon and 50-60g per hour for a full marathon. Only push toward 90g if you've tested it successfully on at least three long runs.

Step 3: Map your fueling to the course. Identify the aid stations. Plan your gel timing around them so you can take gels with water. If there's a climb between km 25 and 30, plan to have fueled well before it — your gut absorbs less when you're working hard uphill.

Step 4: Adjust for conditions. If race morning is 10°C cooler than your training, reduce your planned fluid intake by roughly 15-20%. If it's warmer, increase by the same margin and add sodium.

Or let Sweatr do the maths. Connect your Garmin or Apple Watch, enter your race details, and get a plan built from your actual data — not a generic template and not a food diary.

Your wearable finally learned to count your calories. Now it's time to make those numbers work on race day.