Problem – POS devices provide you three choices typically for receipts: email, text or print. Over time we loose the email due to retention policies or accidental delete, texts suffer the same and print outs are easily lost
Replace the personal email used with an account to Receipt Tracker and send receipts there for storage, classification and reuse for returns.
Order of operations
User registers for account with app
When prompted at POS system enter your new account name with @recipetstore.net as the email
POS sends Email of receipt to Receipt Store Ingest endpoint (AWS SES )which has S3 backend by topic
Lambda parses data and stores in database with my API built in AWS OR
Parser is written local with C# and pulls raw data from S3 and stores in local database
User logs into account to see stored receipts, date, etc
User can classify each receipt and that classification is stored in database
User can administer account and change user name and email
API
Register ( C#)
Login (C#)
Data Write (C# or Lambda
Data Return (C# or Lambda)
Receipt Return (C# or lambda)
S3 (SDK)
AWS SES – Raw info to S3 bucket
Parser ( lambda or Local C# code)
katerebekah
commented
7 years ago
Problem – POS devices provide you three choices typically for receipts: email, text or print. Over time we loose the email due to retention policies or accidental delete, texts suffer the same and print outs are easily lost
Replace the personal email used with an account to Receipt Tracker and send receipts there for storage, classification and reuse for returns.
Order of operations
User registers for account with app
When prompted at POS system enter your new account name with @recipetstore.net as the email
POS sends Email of receipt to Receipt Store Ingest endpoint (AWS SES )which has S3 backend by topic
Lambda parses data and stores in database with my API built in AWS OR
Parser is written local with C# and pulls raw data from S3 and stores in local database
User logs into account to see stored receipts, date, etc
User can classify each receipt and that classification is stored in database
User can administer account and change user name and email
API Register ( C#) Login (C#) Data Write (C# or Lambda Data Return (C# or Lambda) Receipt Return (C# or lambda) S3 (SDK) AWS SES – Raw info to S3 bucket Parser ( lambda or Local C# code)
Models ReceiptAccount UserID registeredEmail personalEmail password(hash)
ReceiptCaptured UserID RecieptType Reciept Retalier Email Date S3BucketID Purpose
Views Register
Stretch Goals
Ingest photo of paper receipt (Parsing (tesseract) Text message ingest Authentication through Google / FB /GitHub