Automating inspection photo filing for manufacturers
Inspection photos get taken on the floor and then live in someone's phone. How automating inspection photo filing works for a 40-400 person manufacturer: how a photo gets tied to the right job, work order and PO, where it gets filed, what a person still checks, and when a simple folder rule is enough.

In brief
Automating inspection photo filing for manufacturers means every photo taken at receiving, in process, at final inspection or at shipping lands in the right job, work order or PO record without anyone renaming or emailing it. The photo is tied to the job one of three ways: someone scans the traveler's barcode first, the job number is in the frame and gets read, or the photo is taken inside an app already open to that job. Software files it to SharePoint or an ERP attachment, and anything it can't match goes to a quality tech to place by hand. Start with the photos you need fastest: concealed freight damage usually has to be reported within five business days.
- Inspection photos are only useful if you can find them: tie each one to a job, work order or PO.
- Concealed freight damage usually must be reported within 5 business days, per Old Dominion, so receiving photos are the best place to start.
- Three ways to tag a photo: scan the traveler first, read the job number in the frame, or shoot inside the ERP's mobile app.
- Unmatched photos go to a person's review list, never to a best guess.
- If one person handles a few photos a week, a folder rule may be all you need.
Where inspection photos end up today
Walk the floor of most 40-400 person shops and you'll see the same thing. Receiving takes a photo of a crushed pallet. Quality takes a photo of a bad weld. Shipping takes a photo of the packed crate before it goes on the truck. Everyone uses their phone.
Then the photo sits in a camera roll as IMG_4417. Maybe it gets texted to a supervisor. Maybe someone emails it to themselves on Friday and drops it in a folder named after the customer. Maybe not.
Nobody notices until someone needs it. A customer says the parts arrived scratched. A carrier denies a damage claim. An auditor asks for evidence on a nonconformance from March. Now someone spends an afternoon scrolling three phones.
Why the filing matters more than the photo
A photo you can't find is the same as no photo. Three places where that costs real money:
Freight claims. Damage you find after the driver leaves has a short clock. Old Dominion's claims FAQ says concealed damage must be reported to the carrier within 5 business days, and formal claims are due within 9 months of delivery. The industry's freight classification rules (NMFC) use the same five-business-day window. As Parcel Industry explains, report after that and you also have to prove the damage didn't happen after delivery, with evidence like records and photographs. Photos with a date, filed to the right PO, are that proof.
Quality records. ISO 9001 doesn't require photos. But it does require you to keep evidence that product met its acceptance criteria and records of nonconforming product, and DNV's ISO 9001:2015 guidance says that evidence must be maintained. If photos are part of how you show it, they have to be findable. For medical device makers, the FDA's quality management system rule (21 CFR 820) builds on ISO 13485's record requirements.
Cost of poor quality. ASQ says the cost of quality in many companies can run as high as 15 to 20 percent of sales revenue. That's not all photos, of course. But a disputed return you can't prove, or a rework you can't trace to a supplier lot, is part of that number.
A photo you can't find in five minutes is the same as no photo.
What a photo already knows about itself
Every phone photo carries data most people never see. The EXIF tags, documented by ExifTool, include the date and time it was taken. If location is on, the GPS tags include latitude and longitude.
That's useful, but it isn't enough. The timestamp tells you when; it doesn't tell you which job. GPS tells you the building, not the workstation. The job number has to come from somewhere else.
One practical detail: iPhones save photos in HEIF by default. Apple's support page says HEIF and HEVC compress better than JPEG and H.264, and you can switch to JPEG under Settings, Camera, Formats, Most Compatible. Some older ERPs and viewers can't open HEIF files. Either convert on upload or set the shop phones to Most Compatible.
Three ways to tie a photo to the right job
How the photo gets its job number
| Method | How it works | Good for | Weak spot |
|---|---|---|---|
| Scan first | The tech scans the barcode on the traveler or receiving label, then takes the photos. Everything after the scan is tagged to that job. | Shops that already print barcoded travelers | Someone forgets to scan the next job and photos land on the last one |
| Job number in the frame | The first photo shows the traveler, packing slip or tag. Software reads the job, PO or part number and tags the set. | Receiving, where the packing slip is right there | Glare, a smudged tag or a handwritten number the software can't read |
| Take it in the record | The photo is taken inside a mobile app already open to that job or PO. | Companies whose ERP has a mobile app with attachments | Slower on the floor; people go back to the camera app |
Barcoded travelers are common. Cetec ERP, for one, prints a barcode tied to the work order number on each traveler, so scanning it opens the job. If your travelers already have one, "scan first" costs almost nothing to add.
"Take it in the record" works when your ERP supports it well. NetSuite, for example, documents how to attach files to a record from its mobile app. If your people will actually use the app on the floor, that may be all you need.
Where the photos get filed
Most shops pick one of two homes:
- The ERP record. The photo is attached to the PO, job or nonconformance. It's right where people look, but ERP storage can be limited or expensive, and some ERPs make attachments hard to search.
- A shared folder with a fixed structure, like SharePoint, with one folder per customer, job or PO, and a link written back to the ERP record. Storage is cheap and anyone with access can browse it.
Either way, the file gets a name a person can read, like the job number, the stage, the date and a sequence number, not IMG_4417.
If you build on Microsoft 365, know the plumbing. Power Automate's SharePoint trigger fires when a file is created and also each time it's modified, Microsoft's documentation says. It doesn't fire for files added to subfolders, and the older "in a folder" triggers are marked deprecated. Those details decide whether a simple flow works or quietly skips photos. Test with real uploads.
What the automation does, and what a person still checks
A working setup usually looks like this:
- Photos upload from the shop phones to one inbox folder, automatically, over Wi-Fi.
- Software reads the scan or the job number in the frame, and the EXIF time.
- It checks that job or PO against the ERP: does it exist, is it open, is it at the stage the photo says?
- Matched photos get renamed, filed and linked to the record.
- Anything it can't match, or isn't sure about, goes to a short review list.
The person in that last step matters. Usually it's a quality tech or the receiving lead, and the list takes a few minutes a day. They place the photos the software couldn't, and they catch the ones it placed wrong. Never let unmatched photos get filed to a "best guess." A photo filed to the wrong job is worse than one in the inbox, because nobody looks for it there. More on that design in human-in-the-loop automation.
A person also decides what counts as a nonconformance. Software can file a photo of a bad weld. It shouldn't decide the weld is bad.
When you don't need any of this
To be fair, plenty of shops don't need automation here. If you take a dozen inspection photos a week and one person handles all of them, a folder rule and ten minutes on Friday may be enough. If your ERP's mobile app already attaches photos and people use it, use that. And if your customers never ask for photos and you've never lost a freight claim, start somewhere else.
It's worth automating when photos come from several people and several stations, when customers or auditors ask for them, or when you've lost a claim or a dispute because you couldn't find the picture.
How to start
- Pick one stage. Receiving is usually the best first step: the packing slip is in frame and the freight-claim clock makes speed matter.
- Decide where photos live. ERP record or shared folder, and the naming rule.
- Choose how the job number gets captured. Scan first if you have barcodes; otherwise, the slip in the first photo.
- Set up the review list and name the person who clears it daily.
- Run it for a month, then count: how many photos filed themselves, how many went to review, and how long it takes to pull up any photo for a given PO.
Then add the next stage. Shipping photos of packed orders are usually second, because they settle "it arrived damaged" disputes. For the paperwork that arrives with the freight, see our guide on packing lists and bills of lading and reading receiving paperwork.
Common questions
What does automating inspection photo filing mean?
Photos taken at receiving, in process, at final inspection or at shipping are tied to the right job, work order or PO and filed automatically, with a person reviewing anything the software can't match.
How does software know which job a photo belongs to?
Usually one of three ways: the tech scans the traveler's barcode before taking photos, the job or PO number is visible in the first photo and gets read, or the photo is taken inside an app already open to that record.
How fast do we need photos of freight damage?
Fast. Old Dominion says concealed damage must be reported within 5 business days and formal claims are due within 9 months. Report later and you also have to prove the damage didn't happen after delivery.
Does ISO 9001 require inspection photos?
No. It requires you to keep evidence that product met acceptance criteria and records of nonconforming product. Photos can be part of that evidence, so they need to be findable.
Why won't some systems open iPhone photos?
iPhones save in HEIF by default. Some older ERPs and viewers can't open it. Convert on upload, or set the phones to Settings, Camera, Formats, Most Compatible to save JPEG.
Can Power Automate file photos from SharePoint automatically?
Yes, with care. Microsoft says its SharePoint file trigger fires when a file is created or modified, doesn't fire for files in subfolders, and the older folder-specific triggers are deprecated. Test with real uploads.
Do small shops need inspection photo automation?
Not always. If one person handles a dozen photos a week, a folder rule may be enough. It pays off when several people and stations take photos and customers, auditors or carriers ask for them.
Sources
- Old Dominion Freight Line, Claims FAQ
- Parcel Industry, Revisions to the NMFC: what shippers need to know
- DNV, ISO 9001:2015 guidance document (PDF)
- eCFR, 21 CFR Part 820 Subpart C
- ASQ, Cost of quality
- ExifTool, EXIF tags
- ExifTool, GPS tags
- Apple Support, Using HEIF or HEVC media on Apple devices
- Cetec ERP, What is a traveler and why is it barcoded?
- Oracle NetSuite Help, Attaching files to records (NetSuite for Mobile)
- Microsoft Learn, SharePoint connector actions and triggers in Power Automate
Packing lists and bills of lading without retyping
OCR vs. IDP for packing slips: a 20-document test
Human-in-the-loop automation: why a person should approve every step