1
00:00:00,000 --> 00:00:04,962
PantryLoop helps a home cook plan meals around
the food already in

2
00:00:04,962 --> 00:00:09,925
the kitchen. It connects manually maintained
pantry quantities, editable recipes, and a

3
00:00:09,925 --> 00:00:14,887
meal plan in one browser workspace. The opening
kitchen is labelled as

4
00:00:14,887 --> 00:00:19,849
a sample. Its seasonal produce artwork is a
generated illustration, not a

5
00:00:19,849 --> 00:00:24,812
photograph of actual inventory. This narrated
interface walkthrough uses real app screenshots

6
00:00:24,812 --> 00:00:28,120
and synthetic narration to explain the planning
loop.

7
00:00:29,333 --> 00:00:35,001
Each pantry lot has a name, quantity, unit,
storage location, and personal

8
00:00:35,001 --> 00:00:40,668
use before target. Separate lots can represent
food purchased at different times.

9
00:00:40,668 --> 00:00:46,336
These targets help organize attention, but they
do not establish food safety.

10
00:00:46,336 --> 00:00:52,003
The user remains responsible for checking the
actual ingredient. Quantities can use

11
00:00:52,003 --> 00:00:57,670
grams, kilograms, milliliters, liters, pieces,
or cups. Matching units stay explicit, so

12
00:00:57,670 --> 00:01:02,393
a pantry entry is more useful than a simple
checkbox.

13
00:01:03,625 --> 00:01:08,192
A meal combines a recipe, a date, and a serving
count. Its

14
00:01:08,192 --> 00:01:12,759
ingredient requirements scale with the selected
servings. The allocation engine processes
uncooked

15
00:01:12,759 --> 00:01:17,325
meals in date order, and draws from matching
pantry lots in target

16
00:01:17,325 --> 00:01:21,892
date order. That means the same ingredient
quantity is not promised to

17
00:01:21,892 --> 00:01:26,459
two meals at once. A recipe that was possible in
isolation can

18
00:01:26,459 --> 00:01:30,645
correctly show a shortfall after another meal
reserves the available stock.

19
00:01:31,875 --> 00:01:36,966
The shopping list collects shortfalls across the
plan. In this captured example,

20
00:01:36,966 --> 00:01:42,056
it lists one hundred sixty grams of carrot and
ten grams of

21
00:01:42,056 --> 00:01:47,147
ginger, matching the meal editor. Compatible
units convert automatically, including grams and

22
00:01:47,147 --> 00:01:52,238
kilograms, or milliliters and liters. Cups and
pieces remain separate. Checking an

23
00:01:52,238 --> 00:01:57,329
item marks the list only. The plus action opens
an entry for

24
00:01:57,329 --> 00:02:01,995
the actual purchased quantity. CSV export makes
this calculated list portable.

25
00:02:03,208 --> 00:02:07,381
The captured meal plan now marks the sample
chickpea bowl as cooked.

26
00:02:07,381 --> 00:02:11,554
Its ingredients have been deducted from the
pantry, while the second meal

27
00:02:11,554 --> 00:02:15,727
still shows its missing ingredients. This is a
saved planning record, not

28
00:02:15,727 --> 00:02:18,508
evidence that a real person cooked the meal.

29
00:02:19,708 --> 00:02:24,178
When a fully supplied meal is marked cooked,
PantryLoop deducts its reserved

30
00:02:24,178 --> 00:02:28,648
ingredients and records the quantities used. A
meal with missing ingredients cannot

31
00:02:28,648 --> 00:02:33,118
be logged as if it were ready. The cooking
journal shows the

32
00:02:33,118 --> 00:02:37,588
resulting record, with an undo action that
restores the exact quantities. Repeating

33
00:02:37,588 --> 00:02:42,058
the cooked action does not deduct them a second
time. This completes

34
00:02:42,058 --> 00:02:46,528
the connection between planning a meal and
maintaining an honest inventory afterward.

35
00:02:47,750 --> 00:02:52,929
The recipe view compares ingredient needs with
inventory that has not already

36
00:02:52,929 --> 00:02:58,107
been reserved by planned meals. Recipes with
ingredients near their personal targets

37
00:02:58,107 --> 00:03:03,286
are surfaced first, followed by ingredient
coverage. A servings selector changes the

38
00:03:03,286 --> 00:03:08,464
quantities being considered. Search and an
everything available filter help narrow the

39
00:03:08,464 --> 00:03:13,643
list. This matching is deterministic, using the
saved recipes and quantities; it

40
00:03:13,643 --> 00:03:18,390
is not presented as an artificial intelligence
recommendation or dietary advice.

41
00:03:19,625 --> 00:03:24,153
The kitchen lives in local browser storage.
Settings provide a JSON export

42
00:03:24,153 --> 00:03:28,681
for backup or moving to another device. An
imported kitchen is validated

43
00:03:28,681 --> 00:03:33,209
and previewed before replacement, with a
reminder to preserve the current kitchen

44
00:03:33,209 --> 00:03:37,737
first. A clean start is also available for
people who prefer to

45
00:03:37,737 --> 00:03:42,264
enter their own inventory and recipes. There is
no cloud synchronization, so

46
00:03:42,264 --> 00:03:46,415
exporting a backup is the practical way to
protect the work.

47
00:03:47,625 --> 00:03:52,823
PantryLoop follows the practical idea of
checking existing food and planning meals

48
00:03:52,823 --> 00:03:58,022
before shopping. Its records describe quantities
entered, reserved, and logged; they do

49
00:03:58,022 --> 00:04:03,220
not prove money saved, emissions avoided, or
food waste prevented. The app

50
00:04:03,220 --> 00:04:08,418
was developed with AI assistance, while its
planning logic is deterministic. The

51
00:04:08,418 --> 00:04:13,617
finished loop is straightforward: maintain the
pantry, choose a recipe, plan servings,

52
00:04:13,617 --> 00:04:18,815
buy only the shortfall, and update the kitchen
when cooking is done.