Review before saving: 10 received, 1 damaged, 9 accepted and 2 undelivered. From the recorded demo.
Two deliveries, two receipts: 12 received, 11 accepted, 1 damaged and none undelivered. From the recorded demo.
Real MCP client check: protocol 2025-11-25, 11 tools and matching saved data. From the recorded demo.

Inspiration

Small shops get deliveries in parts. During a busy shift, missing or damaged goods are easy to lose track of.

What it does

Staff say or type what arrived. ReceiveRight checks the order and prepares a receipt draft. A person reviews the numbers and confirms it. Later deliveries get separate receipts. Supplier reports stay as drafts; nothing is sent.

The demo

A café orders 12 cases of oat milk. Ten arrive, including one damaged. Two good cases arrive later. The final record shows 12 received, 11 accepted, 1 damaged and nothing undelivered. The damage stays on record.

How we built it

We used React, TypeScript, Amazon Bedrock and Cloudflare storage. Bedrock prepares drafts through checked receiving actions. A separate MCP server uses the same receiving code. The AI cannot confirm a receipt.

Challenges and lessons

We worked through unclear counts, dictation mistakes and expired Bedrock keys. We learned to keep received, accepted and damaged goods separate, and to require a person to confirm each receipt.

Limits and next steps

This is an independent Alexa+ web simulator, not a connected Alexa device. Photos are evidence only, with no text extraction. Next, we want to read packing slips and support returns.

Run it locally using the setup steps in the repository. The voice assistant needs a Bedrock key; manual entry works without one.