Retail sample tracking for CPG brands: from sample sent to first reorder

The software you find when you search for this is not about your samples

Type "sample tracking software" into a search engine and you get two kinds of product. One is laboratory software, built for specimens moving through a testing facility with chain-of-custody rules. The other is trade-spend and deduction software, built for money moving back out of a retailer after a promotion.

Neither of them tracks the thing a brand actually means by a sample: a box of product, sent to a named human at a retailer, a broker or a distributor, against a date you did not set, followed by a decision you may never be told about directly.

That gap is not evidence of an opportunity. It is only worth knowing because it explains why the search is frustrating, and why so many brands end up running this workflow in a spreadsheet next to their email.

This worksheet is the set of questions we ask before deciding whether a sample workflow is worth building software for, extending an existing system to cover, or leaving exactly where it is. It is useful whether or not you ever talk to us. Several of the questions are ones where "nobody wrote it down" is the honest answer, and writing that down is the finding.

A retail sample is four things at once

Before you can track one, agree on what it is. A sample is:

1. Physical goods that left your inventory and are not a sale.
2. A recipient with a name, because a box addressed to a company gets opened by nobody in particular.
3. A date you do not control, set by someone else's review calendar or buying cycle.
4. An open question, which stays open until somebody closes it, and usually closes itself by being forgotten.

Most systems handle the first one, because it moves inventory. The other three are the ones that get lost, and they are the three that decide whether the sample was worth sending.

The worksheet

Answer these for your own company before you look at any tool. Write the honest answer, not the intended one.

1. Request: how a sample gets asked for

• Who can ask for a sample to go out: a rep, a broker, the buyer themselves, someone in marketing?
• Where does that request arrive: email, a text message, a form, a conversation at a show?
• Does anyone approve it before product leaves, and what does approval depend on: cost, quantity, who is asking, how many samples that account has already had?
• Is the request recorded anywhere that is not a person's inbox?

2. Send: what actually left the building

• Which system, if any, knows that product left as a sample rather than as an order.
• Whether sample stock is drawn from the same inventory as sellable stock, and whether anybody reconciles the difference.
• What was sent, exactly: which items, which sizes, which lot or production run, and whether that matters for what you sell.
• Who at the receiving end is expected to open the box, and whether their name is written down.

3. The date you do not control

This is the stage that separates a tracked sample from a hopeful one.

• Does this recipient work to a review calendar or a buying window? If so, where is that date recorded, and who checks it?
• How far ahead of that date does someone need to act, and who is that someone?
• What happens when the date moves, which it does. Does anybody find out, and does anything downstream update?
• If the sample was sent without a date attached, is that visible to anyone, or does it look the same as a sample with a date?

4. Decision: including the one nobody sends

• How do you find out the answer: an email, a portal, a broker's monthly update, an order appearing?
• Where does that answer get recorded, and does the record distinguish between declined and never answered? Those are different problems and they are usually stored as the same blank.
• When the answer is no, does the reason get captured in a form anybody can count later?
• How long does a sample stay open before somebody decides it is dead, and who decides?

5. After the yes: the part that is actually the point

• When a sample turns into an authorization, does the account record show which sample caused it?
• Who places the first order, through what route, and how long after the decision?
• What has to be true before a reorder happens on its own: a portal login, a standing order, a rep visit, a reminder?
• Can you answer, for last year, which samples led to a reorder and which led to one order and nothing else?

If you can answer that last question without exporting anything, you have a tracked sample workflow already and you do not need to build one. Most brands cannot.

What the answers usually show

Three patterns come up often enough to name.

The workflow is real but invisible. The steps happen reliably, because one experienced person carries them, and nothing is written down. This is not a software problem yet. It becomes one the week that person is on holiday, or leaves.

The record exists in four places. Inventory knows goods left. Email knows who asked. A spreadsheet knows the date. The rep knows the outcome. Nobody can join them, so nobody can answer the reorder question. This is the case where a small amount of building pays for itself, because the work is joining records, not creating new ones.

The portal owns the truth and you re-key it. Where a retailer or distributor runs its own submission portal, the authoritative record of a submission lives there, and you cannot change that. What you can do is hold your own copy of what you sent, to whom, and when, so your side of the story survives outside somebody else's login. Be clear-eyed about which half you actually control.

Where the boundary sits

We do not claim to connect to a retailer's supplier portal or to a distributor's supplier system. Those are somebody else's systems, and what they expose changes without notice. What can sensibly be held on your side is the sample record itself: who asked, what went out, to whom, against what date, what came back, and what it turned into.

That distinction matters more than any feature. A tool that promises to automate the portal side is promising something it does not control. A record that survives on your side is something you own.

Where we have done this

beLoved Health is a distribution company David runs. Samples are part of the system he built for it, alongside accounts with their locations, rep routes, quotes, wholesale ordering and invoicing. The path that system records is the one described here: an account, a sample logged against it, a follow-up that is scheduled rather than remembered, a first order, and a reorder that shows up on the account the same day.

That is one company's system, built and run by one of us. It is not an independent audit, we have not measured rep time or sample-to-order conversion, and it does not show a connector working against a retailer's portal. It shows the workflow in use at one distributor.

If you want the wider version of this, covering leads and orders as well as samples, the rep-to-order workflow worksheet is the longer document. If you are evaluating CRM products against this kind of workflow, the guide to choosing a CRM for wholesale distributors has a scorecard.