Sample tracking log
Keep every sample accounted for before the order rides on one.
A sample sent and forgotten is a stalled qualification: the buyer is waiting on a result nobody logged, the supplier thinks the ball is in your court, and the order timeline slips while both sides assume the other is moving. A sample with no tracked status is a deal quietly going cold.
Add a row per sample, update the status as it moves, and export CSV when you need to share or archive, with the data staying on your machine.
Log
| Date | Supplier | Product | Courier | Tracking | Recipient | Status | Notes | Actions |
|---|
Sample-tracking discipline
Sample tracking is unglamorous but it is the discipline that converts inquiries to orders. The seller side that knows on day 14 that a sample was tested, that the buyer wants a re-test on a different batch, and that the courier delivered Friday wins the next conversation. The seller side that has to ask the buyer "did you receive the sample?" loses credibility on every interaction.
The log captures the eight fields that matter and stores them in browser local storage so the data persists without a login or a backend. Export CSV any time for backup or for transfer into your CRM.
A worked example
The booking. You send free samples to twelve inquirers in a busy month and keep the details in your head and a few scattered emails.
The failure. Three weeks on, a serious buyer emails "we tested the sample, let's talk volume", and you cannot remember which batch you sent, what assay it ran, or which courier carried it. You have to ask the buyer to remind you, and the credibility you built evaporates in one reply. The order that was ready to close stalls while you reconstruct the trail.
The fix. Log each sample as it goes out: SKU, batch, assay, courier, tracking number, date sent, status. When the buyer comes back you answer in one line with the batch and the result, propose the next step, and the conversation moves to volume instead of backtracking. The discipline is what turns the sample into an order.
Setting the inspection plan once the sample-backed order is placed? The AQL sampling plan calculator is at /tools/sales-and-ops/aql-sampling-plan-calculator.
Backing the sample with documented specs? The product spec sheet generator builds them at /tools/image-and-content/product-spec-sheet-generator.
Frequently asked
Why a separate sample tracking log?
Chemical sales lives on samples. A typical sourcing project sends 5 to 15 samples to one buyer over 3 to 6 weeks before the first PO lands. Each sample has its own date, courier, tracking number, supplier batch, buyer QC outcome, and follow-up note. Without a log, the seller loses track and the buyer asks the same question twice. The log lives in the browser; nothing is uploaded.
Where is the data stored?
Local storage on your browser. The log persists across sessions on the same device. Clearing browser storage deletes the log. CSV export lets you transfer to a spreadsheet for backup or sharing.
Related tools
- Email templatesLive
Email template library
6 battle-tested chemical-trade email templates: RFQ response, payment reminders (7-day soft + 21-day firm), QC claim response, lead-time slip apology, CO requirement check. AU English, no em-dashes.
Open tool →
- Audit checklistLive
Supplier audit checklist generator
Generate an audit checklist by product category, ready to print and take to the factory floor.
Open tool →
- AQL · Z1.4Live
AQL sampling plan calculator
ANSI Z1.4 / ISO 2859-1 Level II Normal Inspection. Lot size to code letter, sample size, accept/reject thresholds at AQL 1.0, 2.5, or 4.0.
Open tool →