Why Content Beats a Pattern for PDFs
The reason bulk PDF renaming is frustrating is that the useful data was never in the filename. A scanner writes a counter, a browser writes a download string, a phone writes IMG_, and none of them describe the document. Any tool that works from the filename is working from the wrong source, which is why a pattern rename can make the names consistent but not meaningful.
Content-based renaming goes to the real source, the text on the page, and builds the name from what's demonstrably there. That's what lets a mixed batch of vendors, formats, and scan qualities all come out consistently and descriptively named at once, rather than as a tidier version of the same mystery.
It also matters that the useful data lives inside the PDF rather than in any surrounding folder structure or spreadsheet you might keep alongside it. Those external references drift the moment a file is moved, forwarded, or downloaded again, but the vendor name, the invoice number, and the document date are printed on the page itself and travel with the file wherever it goes. Reading them back out and writing them into the filename means the description can never fall out of sync with the document, because it was taken from the document. A single content-based batch turns that printed information into something your operating system's search and sort can finally act on, without you opening a single file to check what it is.