Goods Received

A delivery arrives, someone signs the driver's note, and weeks later the invoice does not match what was ordered or what came off the truck. Without a record made at the door, every shortage, damaged case and price difference is an argument you cannot win, and the supplier who keeps getting it wrong looks the same as the one who does not.

Record each purchase order with its promised date and priced lines. When the delivery arrives, start a goods received note from the order, enter received and rejected quantities with a reason, the invoice price and, if you check it, the temperature, then post it. The app flags shortages, over-delivery, price differences and late delivery against the tolerances you set, works out the claim (rejected units at invoice price plus the overcharge on accepted units), and for partial deliveries deducts what you already accepted so the next GRN expects only the outstanding quantity. The Scorecard ranks suppliers for any date range on on-time, in-full, price accuracy and quality, with weights you choose. Claims lists every rejected or overcharged line, ready to send to the supplier as a credit-note request.

What is inside:

• Suppliers, Orders, Receive (GRN), Scorecard, Claims, Settings and Start here tabs
• Settings for lateness grace days, quantity tolerance, price tolerance, maximum temperature and score weights
• Printable GRN, supplier scorecard and claim request, CSV export, JSON backup
• A worked example: three suppliers, seven orders and seven GRNs

Who it is for: cafes, restaurants, groceries and shops that receive from several suppliers and want evidence for claims.

What it is not: it is a receiving check and a scoreboard, not an accounting or tax system. It does not post to your books, issue tax invoices or credit notes or check VAT. Tolerances and the temperature limit are your own rules; set them to match your supplier agreements and the requirements for your products, which this app does not state. What is payable on a claim is set by your agreement with the supplier.

How it differs: the Restaurant Daily Operations Pack has a simple Excel receiving log. This app matches deliveries to orders, handles partial deliveries and builds a supplier scorecard and claims.

Tested: outstanding quantities, shortages, over-delivery, price differences, claim amounts, on-time and in-full flags, scorecards and order status were compared with a separate Python implementation on randomised orders and GRNs, 12,907 values, with no differences. 74 scripted browser checks cover the example, partial deliveries, validation, posting and reopening, backup restore, print and the 375 and 1280 pixel layouts, with no console errors. Browser tests ran in Chromium and WebKit; Firefox, a real phone, a real printer and a real scanner were not available, so they were not tested.