Sample Tracking System: From Request to Approval

A sample tracking system is a single, structured record of every product sample you request, from the day you ask a factory for it to the day someone signs off on it. Each sample gets one line: what it is, who made it, what it cost, when it shipped, what changed since the last version, and the verdict. Approved, rejected, or revise and resend.

Importers who run samples from memory or chat history usually discover the gap at the worst possible moment. Mass production starts against a version nobody approved. Two factories quote against two different sample versions. Or an inspector arrives at the factory with no reference sample to compare against.

That is why sample management sits at the core of product sourcing at CN Ally. Requests, consolidated shipments, evaluation notes, and the approved reference sample are all logged before any factory receives a production order.

Why do samples go wrong without a tracking system?

They rarely get physically lost. What goes missing is the context around them. You have the sample on your desk, but not the message where the factory said the color was adjusted. You have the courier receipt, but not the note about who agreed to pay for the third revision.

This gets worse with scale. An importer working with five factories on three products easily has fifteen or more samples in motion, each at a different stage: one being made, two in transit, four waiting for evaluation. Without a log, nobody can say which version a quoted price refers to, or whether the sample on the shelf is the one the factory is actually set up to produce.

The expensive failure mode is a disputed approval. The factory insists version B was approved; your team remembers approving version C with changes. With no written record, the argument is settled by whoever shouts longest, usually after the production run has already started.

What should your sample tracking system record?

One row per sample version, not per product. Version B and version C of the same product are effectively different commitments. These are the fields that earn their place:

Field · What to log · Why it matters

• Sample ID: Unique code per version, e.g. SMP-2026-014-B · Ties chats, photos, and payments to one thing
• Product: SKU or project name · Keeps multi-product importers sane
• Factory: Name and contact · You will forget which factory sent what
• Date requested: When the request went out · Starts the lead-time clock
• Sample cost: Fee amount and who paid · Settles "who pays" disputes later
• Courier and tracking no.: Carrier plus tracking number · No more digging through chat history
• Date received: When it actually arrived · Ends the lead-time clock
• Version: Letter per revision: A, B, C · Prevents version confusion
• Changes vs. last version: One-line diff · Shows what this round was supposed to fix
• Evaluation notes: Verdict per criterion · Turns opinions into a record
• Status: Requested / in transit / received / evaluating / revision requested / approved / rejected · Tells everyone where things stand
• Golden sample: Yes or no · Marks the sealed reference for production

The naming convention matters more than the tool. Decide the format once (year, running number, version letter) and never deviate. A sample ID that appears in your tracker, photo filenames, and email subject lines is worth more than any software feature.

How do you request samples properly?

A sample request is a specification sheet in miniature. The factories that produce the best samples are the ones that received the clearest requests. Vague asks ("make it like the photo") produce vague samples, and every vague round costs you two to four weeks.

A proper request covers the product description, materials, dimensions, colors with Pantone codes where color matters, packaging, sample quantity, and the date you need them. It also settles money up front: the sample fee, the courier cost, who pays each, and whether the sample fee is credited against the mass order. Many factories credit some or all of the sample fee once you confirm the order — ask before you pay, not after.

Put the request in writing, in one message or document, and reference the sample ID you already created in your tracker. If the request lives in five chat messages, the factory will build from whichever three it remembers.

How do you track sample costs and lead times?

Costs are where sample budgets quietly die. One sample looks cheap. Six rounds across four factories, each with its own courier bill, does not. Log every cost line in the tracker so the all-in number per product is visible before you approve anything.

Cost item · What to expect · Notes

• Stock sample fee: Often free from the factory · Buyer usually pays the courier
• Custom sample fee: Frequently quoted in the tens of dollars for simple items; more for tooling or complex builds · Ask whether it is credited against the order
• Express courier, China to US/EU: Typically 3–6 days door to door · DHL, FedEx, and UPS all run this lane daily
• Revision rounds: Same again, each round · This is why the "changes vs. last version" field exists
• Consolidated samples: One courier bill instead of several · Ask your agent to bundle samples from nearby factories

For a fuller picture of how express courier fits into the overall shipping mix, this import-from-China shipping guide lays out door-to-door times by mode.

Lead times follow a similar pattern. Stock samples often ship within a few days. Custom samples commonly take one to three weeks depending on complexity, and holiday shutdowns or peak-season backlogs can stretch that. Courier adds roughly a week. Internal evaluation — the part importers forget to schedule — takes another few days if anyone is actually testing the product.

Plan on two to four weeks per full sample round, door to door, and build your product calendar around that. The importers who miss launch dates are usually the ones who assumed each round would take one week.

How should you evaluate samples when they arrive?

Evaluate against a written checklist, not against your gut. The point of evaluation is to produce a verdict the factory can act on: approved, rejected, or revise these three points. That starts with criteria you defined before the sample existed.

A workable checklist covers dimensions and measurements, materials and weight, color match, functional testing, packaging, labeling, and general workmanship. Score each one. A sample that fails on one criterion but passes six is a revision request with a specific fix list, not a vague "not quite right."

Photograph every defect the day the sample arrives, with the sample ID in the frame or the filename. Photos taken weeks later, after the sample has been handled and passed around the office, prove nothing. Log the verdict per criterion in your tracker the same day — evaluation notes written from memory a week later are where disputes are born.

Use the same criteria your inspection team will use later. If your quality control checks stitching density and colorfastness at pre-shipment inspection, check them at the sample stage too. A sample approved on looks but rejected on measurements is a wasted round.

What does a working approval workflow look like?

A workflow is just statuses with owners and rules. The statuses:

Status · Owner · Meaning

• Requested: Buyer · Spec sent, factory confirmed, clock running
• In production: Factory · Factory making the sample
• In transit: Courier · Tracking number active
• Received: Buyer · Logged into the tracker, evaluation starts
• Evaluating: Buyer or product team · Against the checklist
• Revision requested: Buyer · Feedback with photos sent back to the factory
• Approved: Named approver · Signed off with date — production may proceed
• Rejected: Named approver · Dead, with a recorded reason
• Archived: Buyer · Golden sample stored, record closed

Three rules keep this honest. First, one person owns the verdict. Samples evaluated by committee sit in "evaluating" forever. Second, the approval is recorded with a name and a date, e.g. "approved by Li Wei, 2026-09-14", not a thumbs-up emoji in a chat. Third, no production order moves until the status reads "approved." A factory that starts tooling on a verbal "looks good" is a factory you cannot hold to a standard later.

Note the loop: "revision requested" sends the sample back to "in production" as a new version with a new ID and a new row. The old version keeps its rejection reason. That history is what stops the same defect from coming back in round three.

How do you keep revisions and versions under control?

Every revision gets a new version letter, a new row in the tracker, and a one-line change log. Never overwrite the old row, and never let the factory ship "the updated one" without confirming which version it is.

The change log is the whole discipline in one field: "Version C: zipper changed to YKK 5VS per 2026-08-30 feedback; color adjusted to Pantone 19-4052." That single line tells anyone, months later, exactly what this round was supposed to fix, and whether it did.

Get the factory to confirm in writing which version it is quoting and which version it will produce. Quote against version C but produce version B, and you have a pricing dispute layered on top of a quality dispute. Store photos of each version under its sample ID. When a disagreement starts, the photo set with versioned filenames ends it.

Why keep a physical sample library after approval?

The approved sample is the contract in physical form. Factories work from what they can hold, and inspectors compare production against something tangible. A photo in a chat thread is not a reference standard.

The industry term is the golden sample: the final approved unit that the factory is expected to replicate in mass production. A sealed or "red seal" sample is the same idea made tamper-evident. The unit is physically sealed so nobody can quietly swap it. The practical setup is three identical approved samples: one stays with the factory, one with your office, and one with your inspection team, so every party is judging production against the same reference. The Inspection Company's guide to golden samples walks through why this matters and who typically pays for the samples.

Keep rejected samples too, at least through the production run. They are the fastest way to show a factory what "not this" means when a defect reappears. Label everything with the sample ID and approval date, store away from sunlight and moisture, and retire samples only when the product is discontinued, not when the shelf gets crowded.

Spreadsheet or software: what should run the system?

Start with a spreadsheet and move to something structured when the volume breaks it. The honest comparison:

Option · Cost · Fits · Breaks when

• Spreadsheet: Free · Solo importers, under ~30 active samples · Files get shared, versions fork, photos live elsewhere
• Database tool (Airtable, Notion, or similar): Low monthly fee · Small teams, 30–100 active samples · You need purchasing or ERP integration
• PLM or ERP module: Significant · Established operations with formal NPD · You are not there yet — and that is fine

The trigger to upgrade is not sample count alone. It is the moment two people edit the tracker at once, or the moment you cannot find the photos for sample SMP-2026-014-B. Until then, a disciplined spreadsheet with a strict naming convention beats an expensive system nobody updates.

Whatever you choose, the system must do four things: one row per version, a status everyone trusts, costs visible per product, and photos attached to the record instead of scattered across chat apps.

Frequently asked questions

Who pays for samples from Chinese factories?

Usually the buyer. Stock samples are often free from the factory, with the buyer covering courier. Custom samples typically carry a fee, and courier costs for revision rounds are almost always the buyer's responsibility. Many factories credit the sample fee against your mass order — negotiate this before paying, and log who paid what in your tracker so the credit is not forgotten.

How long does it take to get a sample from China?

A full round typically takes two to four weeks door to door: sample production (days for stock, one to three weeks for custom), express courier (roughly a week), and your own evaluation time. Plan product calendars around two-to-four-week rounds, not one-week rounds.

What is a golden sample?

The final approved sample that sets the quality standard for mass production — the physical benchmark the factory must replicate. Keep at least three identical copies: one with the factory, one with your office, one with your inspection team. Some importers seal theirs ("red seal" samples) so the reference cannot be quietly altered.

How many sample revision rounds are normal before approval?

Two to three rounds is common for standard products; complex or custom items can take more. If you are past round four with no convergence, the problem is usually the specification or the factory's capability — not the sample process. That is the point where a new factory, or a rewritten spec, saves more money than another round.

Should I keep old rejected samples?

Yes, at least until the production run is complete and accepted. Rejected samples are the clearest possible way to show a factory what "not this" looks like if a defect reappears. Label each with its sample ID and the reason it failed, and store them with the approved reference.

What should a sample request include?

Product description, materials, dimensions, colors (Pantone codes where color matters), packaging requirements, quantity of sample units, deadline, and the cost arrangement — sample fee, courier cost, who pays, and whether the fee is credited against the order. One written document, one sample ID, no scattered chat messages.

Run this 5-minute check before your next production order

A sample tracking system earns its keep at exactly one moment: the day you are about to commit to mass production. Before you do, open your tracker and answer five questions. Which version is approved? Who approved it, and when? What did the samples cost all-in? Which factory holds the golden sample? What changed between the last two versions?

If you can answer all five in five minutes, your system works. Place the order. If you cannot, the order can wait a day while you close the gaps. Every production dispute described in this industry traces back to one of those five questions having no written answer.

If samples are currently scattered across chat threads and courier receipts, that is a fixable problem. Write to hi@cnally.com or reach out through the contact page — setting up sample tracking is part of how a sourcing agent keeps a production run honest from the first request to the final approval.