01 / See
Capture what
is visible.
Kitchen Scan identifies candidate items from the image instead of asking you to type everything manually.
Kitchen Scan / 4DK
POINT.
SCAN.
MOVE ON.
Inventory only works if adding food does not become a second job. Kitchen Scan is for turning what the camera can see into useful kitchen state, then letting you correct the exceptions.
less typing.
more knowing.
more knowing.
Camera → pantry → context
Direct answer / scanning
The scan should
feed the system.
A one-off AI description is not enough. Scan results should become pantry records that freshness, Ask, Plan and Shop can actually use later.
Capture what
02 / Confirm
Fix the
exceptions.
The user corrects ambiguity, quantity or storage details only where the system is uncertain.
03 / Connect
Let the kitchen
remember.
Confirmed items become shared context for recommendations, planning, freshness and shopping.
inventory without
inventory work.
inventory work.
Why scanning matters
The useful part comes
after the scan.
Recognition is impressive once. Context is useful every day. The value is not that 4DK can see a tomato. It is that the tomato can keep affecting future kitchen decisions.
Get 4DK →Quick answers.
Clear enough for humans. Structured enough to become useful search and answer-engine material later.
Do I need to scan every item one by one?
The goal is the opposite: capture groups where possible, then confirm only uncertain items.
What happens after the scan?
Confirmed items enter Pantry so other 4DK systems can use the same kitchen state.
Can I still add items manually?
Yes. Scan is an acquisition path, not the only way to maintain Pantry.
4DK.FOR D KITCHEN.
