How do I delete a food entry in Base?

Long-press the entry on the Food Log. That enters multi-select mode and selects it. Select anything else you want to remove, then press Remove on the action bar that appears at the bottom of the screen.

Can I copy yesterday's food into today?

Yes. Scrub back to the day using the date arrows at the top of the Food Log, long-press to select the entries you want, and press Copy. They are written into today at the same hours. This is the fastest way to repeat a day you have not saved as a template.

How do I change the portion of something already logged?

Remove it and log it again at the right amount. Entries store the macros they were logged with rather than a live link to the food, which is what stops a later edit to a saved meal from rewriting your history — the trade-off is that correcting a portion is a remove-and-relog.

Will deleting an entry change my maintenance calculation?

Yes, and that is correct. Adaptive maintenance is back-calculated from your average logged intake, so removing an entry that never happened makes the estimate more accurate. Removing one that did happen makes it worse.

Why do identical foods in the same hour collapse into one row?

Three identical entries in one hour display as a single row with a count, because the alternative is a timeline where one repeated item pushes everything else off the screen. Selecting the row selects all of them.

Edit, Copy or Delete Food You Already Logged

Multi-select

Long-press is the entry point. Once in select mode, tapping any other entry toggles it, and the bar shows how many are selected.

The Food Log timeline. Long-pressing an entry opens multi-select; identical items logged in the same hour collapse into one row with a count, and selecting that row selects all of them.

The bar has a cancel control on the left, the count in the middle, and Copy and Remove on the right. Nothing happens until you press one of those two.

Grouped rows

Entries with the same name in the same hour display as a single row with a count. Selecting that row selects every entry behind it, and removing it removes all of them.

This exists because a timeline where three coffees each take a full row pushes the actual meals off the screen.

Copy

Copy writes the selected entries into today, at the hours they were logged at.

The obvious use is repeating a day. Scrub back to Tuesday, select the four meals, press Copy, and Tuesday's food is today's food. That is faster than rebuilding it and does not require having saved anything in advance.

It is also the recovery path for a day you forgot to log. If Thursday looked like Wednesday, copy Wednesday and correct the difference.

For a day you repeat often, a day template is the better tool — it is one tap and it shows you how the day compares to today's target before you commit.

Remove

Remove deletes the selected entries outright.

There is no undo, which is a deliberate asymmetry: re-logging a removed meal takes seconds, whereas a soft-delete that quietly kept counting would be a number you could not check.

Why editing a portion means remove-and-relog

A logged entry carries its own copy of the macros it was logged with. It is not a live reference to the food or meal it came from.

That design decision buys something important:

Editing a saved meal in March cannot rewrite what your log said in January.

If entries were live links, tidying your meal library would silently restate months of history — and every trend, every maintenance estimate and every weekly average computed from it. Historical records that change retroactively are not records.

The cost is that changing a portion after the fact is two actions rather than one. That is the right side of the trade.

What removing an entry does downstream

Deleting food is not cosmetic. It moves real numbers:

maintenance ≈ average logged intake − (trend weight change × 3500 ÷ days)

Remove 600 calories from a day inside the estimation window and your measured maintenance drops by roughly 600 ÷ days-in-window.

The rule that follows is simple and worth stating plainly: remove entries that did not happen, and keep entries that did. A log tidied for how it looks is a log that lies to the arithmetic downstream of it.

Situation	Action
Logged something you did not eat	Remove it
Logged the wrong portion	Remove and re-log correctly
Ate badly and would rather not see it	Keep it
Logged the same meal twice by accident	Remove one
Forgot to log yesterday entirely	Copy from a similar day and correct

The third row is the one that matters. A day you would rather forget is still data, and removing it does not make it not have happened — it just makes your maintenance estimate wrong in a direction that will later confuse you.

Common mistakes

Deleting a bad day. It biases every average that reads the window. The scale already knows.

Correcting a portion by editing the saved meal. That changes the meal for next time and does nothing to the entry already logged. Remove and re-log instead.

Using Copy to fabricate days you did not log. A copied day is a claim that you ate that food. Copy is for repeating a day you actually repeated.

Forgetting that copy targets today. It always writes into today, not into the day you are viewing.

Long-pressing and then tapping elsewhere. Tapping another entry in select mode toggles it rather than opening it. Cancel first.

Removing a whole day rather than the one wrong entry. Select precisely; the bar shows the count for exactly this reason.

What to do next

Check yesterday for anything logged twice — double-tapping the plus is the most common way it happens. Remove the duplicate, and leave everything else exactly as it is.