Operational retrieval
Search Shipping Records by Extracted Data
Find private workspace records by B/L number, invoice number, container, vessel, party or port—even when that reference appears only inside the original PDF.
Shipping records are difficult to retrieve when the useful reference exists only inside a PDF. GainingDocx indexes the structured values already extracted from documents so operators can search the shipment context instead of filenames.
Results connect documents to their shipment, review status and related records, shortening the path from a customer or carrier question to the supporting evidence.
Short answer
How search works here
Search runs against the structured values extracted from your documents, not against filenames. Type a container number, a B/L reference, an invoice number, a vessel or a party name and you get the documents and shipments that actually contain it — including references that appear only inside a PDF and nowhere in its filename.
- Searches extracted field values, not filenames
- Results link to the document and its shipment
- Private to the signed-in account
- Works across every document type
How Shipping Record Search Works
- 01
Parse and save a document.
- 02
Search a known reference or party.
- 03
Open the matching document or shipment.
The retrieval problem in freight operations
A carrier calls about container MSCU1234567. A customer asks about invoice 44821. A broker needs the packing list for a B/L nobody can name. In most operations, answering means opening a shared drive, guessing at folder conventions and opening PDFs until one of them contains the reference.
The reference exists — it is printed on the document. It is simply not in the filename, and filenames are the only thing a file system can search. Extraction solves this incidentally: once values are structured, the reference becomes searchable, and the path from a question to the supporting evidence collapses from minutes to seconds.
What you can search by
| Category | Examples |
|---|---|
| Transport references | B/L number, sea waybill number, master and house air waybill numbers, booking number |
| Commercial references | Invoice number, purchase order number, contract reference, customer reference |
| Equipment | Container number, seal number |
| Parties | Shipper, consignee, notify party, buyer, seller, carrier, agent |
| Movement | Vessel name, voyage, flight number, port of loading, port of discharge, airport codes |
| Cargo | Goods description text, SKU and part numbers, HS codes, marks |
Results that carry context
A search result that is only a filename is barely better than the folder you started in. Results here connect the matched document to the shipment it belongs to, its review status and the other documents in the same group — so the answer to 'where is the packing list for this container' is one click rather than a second search.
- The matching document, with the field the term was found in
- The shipment record it belongs to, and every other document in that group
- Review status, so you can tell a confirmed record from one still under review
- Any outstanding discrepancies on that shipment
- Direct links to export the record or open the source page
Legacy and non-standard references
Real reference data is messy. Container numbers appear with and without spaces, port codes appear in superseded forms, and party names are abbreviated differently on every document. Search that only matches exactly will fail on all of it.
References are normalised for matching while the printed form is preserved on the record, so a container searched without spaces finds the document that printed it with them. Where legacy codes are known to alias to a current one, the alias is followed rather than returning nothing.
Search is private to your account
Workspace search covers your own documents only. It is not an internet index, documents are not shared between accounts, and nothing you upload becomes publicly discoverable. Deleting a document removes it from search along with its extracted data.
Shipping Document Search FAQ
What teams ask before relying on shipping document search in a live operation.
What can I search for?
Any extracted value: B/L and invoice numbers, booking and purchase order references, container and seal numbers, master and house air waybill numbers, shipper, consignee and notify party names, vessels, voyages, flights, ports and airports, goods descriptions, SKUs and HS codes.
Does search require exact filenames?
No. Search runs against structured document values, so the original filename is irrelevant. A reference printed inside a PDF but absent from its filename — which is the normal case — is found exactly as easily as one in the title.
Are my documents publicly searchable?
No. Workspace search is private to the signed-in account and is not an internet search index. Documents are not shared between accounts, and deleting a document removes it from search along with its extracted data.
Can I find a container across several documents?
Yes, and this is one of the more useful cases. A container number typically appears on the packing list, the Bill of Lading, the arrival notice and the freight invoice. Searching it returns every document that carries it, grouped by shipment, so the full paper trail for one box is visible at once.
Does search handle formatting differences?
Yes. References are normalised for matching while the printed form is preserved on the record, so a container number searched without spaces matches a document that printed it with them, and a code entered in lower case matches an upper-case original.
What about legacy or superseded codes?
Where a legacy code is known to correspond to a current one, the alias is followed rather than returning an empty result. This matters most for port codes, where superseded forms circulate in carrier and customer master data for years after the standard has moved on.
Can I search inside goods descriptions?
Yes. Description text from invoices, packing lists and transport documents is searchable, which is how you find a shipment when the only thing anyone remembers is what was in it. Partial terms work — you do not need the exact wording used on the document.
Do search results show whether a shipment has problems?
Yes. Results carry the review status and any outstanding discrepancies on the shipment, so a search that was really a question about whether something is clear to proceed is answered in the result rather than requiring the record to be opened.
How current are search results?
Documents become searchable once they have been extracted, which is normally within the same session as upload or email intake. Corrections made during review are reflected, so searching a corrected reference finds the document rather than only the original misreading.
Can I search across shipments as well as documents?
Yes. Results connect documents to their shipment record, and shipment-level attributes such as parties, routing and status are searchable in their own right — so you can find every shipment for a consignee as easily as a single document by reference.
Is there an API for search?
Reviewed data can be exported and pushed to a downstream system through connectors, where your own systems can index it alongside their existing records. For teams that want retrieval to happen in their TMS rather than here, that is generally the better pattern.
What happens to search when I delete a document?
It is removed from search immediately along with its extracted data. Deletion is genuine removal rather than hiding, which is also why an export taken before deletion is the right way to retain a record you may need later.
Related tools, templates and guides
- Document extractionThe structured values that make search possible in the first place.
- Shipment matchingGroup documents so a search result carries its whole shipment.
- Email-in intakeGet documents into the workspace without downloading and re-uploading.
- Security and data handlingHow workspace data is isolated and what deletion removes.