Ship the Scanner

assembling the full pipeline

Part of: Receipt Scanner

Every piece is built. You send the photo, pull JSON out of the reply, validate the line items, check the totals, normalize the messy fields, retry on failure, and watch the cost. Shipping is wiring those pieces into one function that takes a photo and returns a result you can trust, plus a thin script around it that a person can actually run. One function, start to finish Every function called here (build image message, extract json, process receipt) is something you already wrote in an earlier lesson. Shipping isn't new logic. It's assembly. The final validation pass process receipt is where extraction, normalization, and the totals check meet and settle into one verdict: The output stays small and deliberate: enough to act on with merchant, total, and status, while the full itemized receipt is still sitting on data if you want to store or display more. A script someone else can run The last mile of "shipped" is a command a stranger could run without opening your source: That's the whole thing: one command in, a JSON file out, and a status you can trust because it survived a retry loop and an arithmetic check instead of a single hopeful API call. It lands in your Portfolio Finish

Challenge: Full Pipeline Check