Have a spreadsheet of filenames or product IDs and need to gather the matching files from several Windows folders? Start with the list of requested items, identify where the source files are stored, and review the matches before copying anything.
For a handful of known files, File Explorer may be enough. For a long list scattered across directories, a list-driven collector such as FilePull can reduce repetitive searches and make missing or ambiguous matches easier to review.
When a file list is more useful than searching folder by folder
Suppose a client asks for 80 product images. Your list contains product IDs, but the files live in different folders for seasons, projects, or photographers. Searching for each ID separately is slow, and copying the first match you see can produce the wrong delivery.
The important distinction is between finding a filename match and confirming that the file belongs in the delivery. A product ID might appear in a front image, a back image, and a specification document. You still need to decide which results are relevant.
Step 1: Prepare the list of files to collect
Start with the filenames, SKUs, product codes, or IDs you have been given. If the source is a spreadsheet, identify the column that contains the values to match. Remove obvious empty rows and check for typing errors before collecting files.
A simple filename list might look like this:
PRD-18421-front.jpg
PRD-18422-front.jpg
PRD-18423-spec.pdf
These are illustrative filenames, not files from a verified dataset. If your list contains product IDs rather than complete filenames, check how your chosen matching method handles partial names and multiple results. Do not assume every file containing an ID is automatically the right file.
Step 2: Choose the source folders
Identify the folders or drives that contain the original files. If you're collecting from several locations, make sure all relevant sources are included.
Use a separate output folder, ideally outside the folders being searched. This reduces the chance of collecting an earlier output as if it were a new source file.
If the originals must remain in place, choose a copy workflow rather than a move workflow. Keep a backup when the source collection cannot easily be replaced.
Step 3: Match the list against your folders in FilePull
FilePull is a Windows app designed for collecting files from a list of filenames, SKUs, or IDs. Its published description includes batch file collection and review of matched and missing files.
Open the app's list-import workflow, select the identifiers you want to match, and choose your source locations. The exact options may differ by installed version, so review the visible controls before starting a large job.
Check whether the results show a clear match, more than one possible match, or a requested item that could not be found. A high match count is not proof that every result is correct.
Step 4: Review missing and duplicate matches
Before collecting, investigate anything that needs review:
- Missing files: Recheck the list entry, extension, naming conventions, and selected folders.
- Multiple matches: Compare filenames, file types, and source locations. Several files may share one product ID.
- Duplicate filenames: Files from different directories can share a name even when their contents are different.
- Unexpected file types: An ID may also appear in a PDF or document when you only need images.
For example, a request for PRD-18421 could correspond to multiple assets. Confirm which of them the recipient actually expects before including them.
Step 5: Collect files into a separate destination
Once you've reviewed the matches, choose the destination and check any available conflict-handling options. Prefer copying when originals should remain untouched.
Be particularly careful if a destination already contains a file with the same name. Don't allow an overwrite without confirming that the replacement is intentional.
Start the collection only after reviewing the selection. If the process stops or reports an error, check the partial output before repeating the operation.
Step 6: Verify the collected files
Open the destination and compare the contents with your original request list. Look for missing items, duplicates, incorrect file types, or files that cannot be opened.
For a client delivery, spot-check representative files rather than relying exclusively on a successful collection message. File matching is a way to locate candidates, not proof that a document or image contains the correct content.
Common problems
Why wasn't a requested filename found?
The name may be spelled differently, the extension may have changed, or the file may be outside the selected folders. Check the source list and search locations before changing the originals.
What if several files match the same SKU?
Review their extensions and folder locations. A product can legitimately have several assets, but the delivery may require only a subset.
Should I copy or move the files?
Use Copy when you need to preserve the source collection. Moving files changes where the originals live and should be reserved for a workflow that explicitly requires it.
What if I only need three or four files?
File Explorer may be simpler for a short, known list. A list-driven collector becomes more useful when there are many requested items spread across folders.
A repeatable workflow for future file collections
Keep the requested list, record how you resolved missing or ambiguous items, and verify the output before delivery. For repeated projects, review the source folders and destination again even if you reuse a saved workflow.
If you regularly receive spreadsheets of filenames, SKUs, or product IDs, explore FilePull for Windows to see whether its list-driven collection workflow fits your process.