A warehouse receiving and returns inspection app

The dock is where inventory accuracy is won or lost. A carton short on a pallet, a damaged case signed for as clean, a return put back on the shelf without anyone checking whether it works: each one becomes a stock count that does not match, a vendor credit nobody claims, or a customer who receives a used item as new. In many warehouses the tools for this moment are a printed packing slip, a pen, and a receiver's memory.

A receiving and returns inspection app gives the dock and the returns bench a simple, phone-first workflow that captures what really arrived and what really came back, with proof. This guide explains the problems it solves, what it should contain, an example request you can hand to FORGE, a rollout plan and how to measure the results.

What the current way costs you

• Signing for what you did not count. Drivers are in a hurry and the receiver signs the delivery receipt before the pallet is broken down. Damage found later is harder to claim.
• Shortages that never become credits. The receiver notes "2 short" on the packing slip. The slip goes in a tray. Accounts payable pays the full invoice.
• Damage without photos. A claim with no picture taken at the dock is a claim you will likely lose.
• Returns that skip inspection. A busy week means returned items go straight back to stock. The next customer gets the item with the missing part.
• No vendor history. Everyone knows one supplier is always short, but nobody can show it.
• Spreadsheets nobody trusts. A receiving log in a spreadsheet is filled in at the end of the day from memory, if at all.
• Heavy warehouse systems that do not fit. Full warehouse management systems are powerful, but for smaller operations they can be expensive and slow to set up, and they rarely bend to how your dock actually works.

What the app should contain

Roles

• Receiver: checks in shipments, counts, photographs, records discrepancies.
• Returns inspector: inspects and grades returned items.
• Warehouse lead: assigns work, reviews discrepancies, approves dispositions over a set value.
• Purchasing or buyer: sees and resolves vendor discrepancies, manages vendor scorecards.
• Customer service: sees the result of each return inspection to issue refunds, replacements or denials.
• Manager or owner: reports and settings.

Receiving records

• Inbound shipment: purchase order number, vendor, carrier, tracking or bill of lading number, expected date, actual arrival date and time, dock door, number of pallets or cartons.
• Condition at arrival: a quick check of the outside of the load (seal intact, pallets wrapped, visible damage) with photos, completed before signing the carrier's paperwork.
• Line items: item number, description, expected quantity, counted quantity, unit of measure, lot or serial number if you track them, expiration date if relevant, condition, and a putaway location.
• Discrepancies: short, over, damaged, wrong item, wrong unit, missing paperwork, with photos and a note.
• Statuses: Expected, Arrived, Counting, Discrepancy review, Received, Put away, Closed.

Returns records

• Return authorization: return number, customer, original order, items, reason given by the customer, date received.
• Inspection: checks for each item type (packaging, all parts present, powers on, cosmetic condition), photos, serial number match, and the grade.
• Grades and dispositions: for example, A: restock as new; B: restock as open box; C: send to repair; D: return to vendor; E: scrap or recycle. Each grade has one disposition.
• Outcome: refund approved, replacement sent, refund reduced with reason, or return denied with photos.
• Statuses: Expected, Received, Inspecting, Graded, Waiting on approval, Disposition done, Closed.

Rules worth building in

• Blind count option: hide expected quantities from the receiver until the count is entered.
• Tolerance: a difference within a small amount you set is accepted automatically; anything larger goes to review.
• Value threshold: dispositions over a dollar amount you set need lead approval.
• Required photos: for any damage, any return graded below new, and any denial.
• Serial match: flag a return whose serial number does not match the one sold.

Screens

1. Dock today: expected shipments, what has arrived, what is being counted.
2. Receive: scan or choose the purchase order, then count each line on a phone with large number buttons and a camera button.
3. Discrepancy queue: for leads and purchasing, every open shortage, overage and damage with photos.
4. Returns bench: returns waiting for inspection, oldest first.
5. Inspect: one item at a time, check list, photos, grade.
6. Vendor scorecard: on-time rate, fill accuracy and damage rate by vendor.
7. Returns report: reasons, grades and dispositions by product and month.

Notifications

• Purchasing is told immediately about any discrepancy over the tolerance.
• Customer service is told when an inspection is finished, with the grade and photos.
• The lead is told when a high-value disposition needs approval.
• A daily summary goes to the manager with yesterday's receipts, open discrepancies and returns waiting.

Example request

Example request: "Build a receiving and returns app for our warehouse. Purchasing enters purchase orders with vendor, expected date and line items, or uploads them from a spreadsheet. When a truck arrives, the receiver picks the purchase order on a phone, records the carrier and number of pallets, and takes photos of the load before signing. Then they count each line without seeing the expected quantity, and the app compares the count to the order after. Differences of more than two units or any damage go to a discrepancy list with photos for purchasing to resolve with the vendor. For returns, customer service enters a return number with the customer, the original order and the reason. When it arrives, an inspector checks packaging, parts and function, takes photos, records the serial number and grades it A to E. A goes back to stock, B to open box, C to repair, D back to vendor, E to scrap. Anything worth more than $300 graded C or lower needs the warehouse lead to approve. Customer service gets a notification with the grade so they can issue the refund. Show a monthly vendor scorecard with on-time rate, accuracy and damage rate, and a returns report by reason and product."

Comparing the options

Getting freight damage and shortage claims right

Most of the money in receiving comes back through claims, and claims depend on what you recorded at the moment of delivery. Build the app so the right evidence is captured every time, without the receiver having to remember.

• Note it on the carrier's paperwork. When the load arrives damaged or short, the exception should be written on the delivery receipt before signing. Add a step in the app that asks "Did you note the exception on the driver's paperwork?" and requires a photo of the signed receipt.
• Photograph in order. The outside of the trailer or load, the labels, the damaged cartons before opening, then the contents. The app can prompt each photo in sequence.
• Keep the packaging. Add a field for where the damaged packaging is held, because carriers and vendors often ask to see it.
• Track the deadline. Carriers and vendors set their own time limits for reporting concealed damage and filing claims. Store each vendor's and carrier's deadline in the app and alert purchasing well before it passes. Confirm the actual limits in your carrier and vendor agreements.

Rollout plan

1. Map today's process. Walk a shipment from the truck to the shelf and a return from the door to its final place. Note every handoff and every place paper sits.
2. Agree on discrepancy rules. Tolerances, who resolves what, and how fast.
3. Agree on return grades. Write each grade in one sentence with a photo example.
4. Load open purchase orders. Start with what is due in the next two weeks.
5. Train receivers at the dock, not in a meeting room. Receive one real shipment together.
6. Run receiving only for two weeks. Then add returns once receiving feels routine.
7. Hold a weekly ten-minute review of discrepancies and returns with purchasing and customer service.
8. Share the first vendor scorecard with your buyer after the first full month.

Mistakes to avoid

• Signing before inspecting the load. Build the outside condition check and photos as the first step, before the receiver signs anything.
• Letting the receiver see expected quantities by default. Counts drift toward the number on the paper.
• Grades with fuzzy meanings. If two inspectors would grade the same item differently, rewrite the grade descriptions.
• Discrepancies with no owner. Every discrepancy is assigned to a person in purchasing, with a due date.
• Skipping returns during busy weeks. Busy weeks are when inspection matters most. If you must, quarantine returns rather than restocking them unchecked.
• Collecting data nobody reviews. The vendor scorecard only pays off if someone brings it to the vendor.

How to measure that it works

• Vendor credits recovered for shortages and damage, compared with the months before.
• Receiving accuracy: how often cycle counts match what receiving recorded.
• Dock to stock time: from truck arrival to items available on the shelf.
• Returns cycle time: from arrival to refund decision.
• Restock errors: customer complaints about used or incomplete items sold as new.
• Share of discrepancies with photos. Aim for all of them.

Checklist before you build

1. Walk one shipment and one return from start to finish.
2. List every field your receivers and inspectors need.
3. Set your count tolerance and value thresholds.
4. Write your return grades and their dispositions.
5. Decide who resolves discrepancies and approves dispositions.
6. Gather open purchase orders and your item list.
7. Choose the devices for the dock and the bench and test camera scanning in your lighting.
8. Pick the start date and retire the paper log on that date.

How FORGE handles it

With FORGE, your warehouse lead or operations manager describes the app in plain words, like the example request above. A panel of top AI models plans it, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Most teams have their first real tool the same day, and it runs on the phones, tablets and desktops your team already uses.

Every app lives inside your company, and only the people you invite can get in. Receivers, inspectors and customer service reps who only use the app are free, so every person on the dock can have it. Roles decide who builds and who uses, and FORGE keeps a complete record of who did what. When your grades or tolerances change, describe the change; a change costs a small fraction of a build and only counts when something actually changes.

It is $49 a seat a month for each person who builds, with 3 builds included, and packs of 10 builds for $150 when you need more. Our team starts every company with a workflow workshop. If the dock is where your money leaks, talk to us.

Questions people ask