What to Send a Customer When They Pay a Deposit

A customer sends a deposit for a piece that does not exist yet. It will not exist for another two months. Search for what to send them back and every result is a generic receipt template — a logo box, a line for "amount paid", a thank-you note — built for a transaction that finished the moment the money changed hands. A made-to-order deposit is not that transaction. The piece has not been made, the rest of the price has not been paid, and the receipt for it has to say so.

This assumes the deposit amount itself is already settled — how much to ask for is a separate decision, covered in how much deposit to charge on a made-to-order piece. What follows is about the document that goes out once the customer has actually paid it.

Why the receipt is the contract most sellers actually have

Plenty of made-to-order sellers do not have a signed contract for most of their orders. What they have is a conversation — a DM thread, an email, a call — followed by a deposit landing in their account. If a dispute happens three months later, the thing both sides can point back to is not the conversation, which nobody remembers accurately. It is whatever was written down at the moment the money moved.

That is what makes the receipt more load-bearing than it looks. It is not a courtesy sent after the real agreement — for a large share of this market, it is the agreement, or the closest thing either side wrote down. A message that only says "deposit received, thanks!" confirms the payment and nothing else. Three months later, neither person can point to it for anything that matters.

None of this replaces a proper written agreement on the terms themselves — refund conditions, what happens if the order is cancelled partway through, and so on. That is its own subject, covered in what a custom order contract needs to say about deposits. The receipt's job is narrower: confirm what was agreed at the moment the deposit arrived, clearly enough that neither side has to reconstruct it later.

Four things a generic receipt does not carry

A retail receipt only has to answer one question: what was bought, for how much, on what date. A made-to-order deposit receipt has to answer that question plus three more, because the transaction is not actually finished when the receipt is sent.

1. What is being made

Not just a product name — the specifics that were agreed on: size, material, color, quantity, any customization. This is the piece the customer thinks they ordered, in writing, at the moment they paid. Vague descriptions here are where "that's not what I asked for" conversations start, months later, when memory has quietly filled in the gaps differently on each side.

2. What is still owed

The deposit amount confirms what came in. It says nothing about what is left, and "what is left" is usually the number the customer actually cares about weeks later. State the full price, the deposit paid, and the balance remaining as three separate figures, not one.

3. When it is expected

A rough date or window, labeled clearly as an estimate rather than a promise. This is what turns "any update?" into a question the customer can answer for themselves before they ask it, and it sets the expectation that a normal production delay is not a broken commitment.

4. What happens if either side backs out

This is the one line that prevents most disputes, and it is the one generic templates never include, because a generic receipt assumes the transaction cannot be undone. A made-to-order deposit can be — the customer can cancel, or the seller can fail to deliver — and stating upfront what happens to the deposit in either case is what keeps that conversation from becoming a negotiation later. It does not need to be the full clause; one sentence pointing at where the actual terms live is enough on the receipt itself.

A copy-paste version

Nobody sends a formatted document over WhatsApp. What actually gets sent is a short message, and it works fine as long as the four things above are in it. Something close to this:

Fill in the bracketed parts, drop the last line if it does not apply yet, and send it the same place the order was discussed — a DM thread, an email, whatever the customer is already reading. The point is not the format. It is that all four things are in one place, sent once, at the moment the deposit lands rather than reconstructed from memory if a question comes up later.

Receipt, invoice, or confirmation — and why it is not cosmetic

The word on the document changes what it claims to be. A receipt confirms money that already arrived. An invoice is a request for money that has not arrived yet — calling a deposit confirmation an "invoice" is technically backwards, since the money is already in your account by the time you send it. A confirmation sits somewhere in between: an order summary that happens to mention a payment.

For most made-to-order sellers, "receipt" or "confirmation" describes a deposit acknowledgment more accurately than "invoice" does, and using the accurate word avoids a customer opening what looks like a bill for an amount they already paid. This is a wording question, not an accounting one — whether the payment itself needs a formal invoice for tax purposes in your jurisdiction is a different question entirely, and it is covered from the accounting side in whether a customer deposit counts as income.

The PDF problem

A PDF receipt is a snapshot of one moment: the day the deposit was paid. Everything on it — the balance owed, the ready date, sometimes even the price if the order changes — is accurate for exactly that moment and starts going stale the day after. Three weeks later, the piece has moved further into production, the ready date has firmed up or slipped, and the PDF still says what it said the day it was generated.

Nobody re-sends a new PDF every time something changes. What actually happens is the customer keeps the original, the seller keeps having the conversation from memory, and the two drift apart quietly until a "wait, I thought it was ready by now" message arrives.

A link does not have this problem, because it is not a document — it is a view onto the order as it currently stands. The same balance, the same ready date, read live instead of copied once. Ordamo's own public order page works this way; you can see a live example, with sample furniture figures, at /o/demo. It shows what was ordered, what has been paid, what is still owed, the expected ready date, and payment instructions with any payment link in that text rendered clickable rather than as plain text a customer has to select by hand. Send that link once, and the customer checking it in six weeks sees the current numbers, not the ones from the day they paid.

The receipt and the link are not competitors. The receipt confirms the moment the deposit was paid; the link is where anything that comes after that moment actually lives. Sending both — a short confirmation message plus a link to the order — covers the instant and the duration.

What the customer should be able to check without asking you

The test for whether a deposit receipt is actually doing its job is not whether it looks professional. It is whether the customer, six weeks after paying, can answer their own question without messaging you: What did I order, exactly? How much have I paid, and how much is left? When is it expected? What did we agree would happen if something goes wrong?

• What was ordered — with enough specifics that neither side is relying on memory for size, material, or quantity.
• What has been paid, and what is still owed — as two numbers, not one.
• When it is expected — a window, labeled as an estimate.
• What happens if either side backs out — one line, pointing at the fuller terms if you have them.

Answer all four up front and most of the messages that would otherwise arrive later never get sent, because the answer was already there when the customer went looking. That is also the job an order page does on an ongoing basis rather than at a single moment — covered in what a customer status page needs to show, if the receipt is the one-time version, the status page is the standing one.

The bottom line

A deposit receipt for a made-to-order piece has a harder job than a retail one, because the transaction it is confirming is not finished — the piece does not exist yet, and neither does the rest of the payment. Four things carry that weight: what is being made, what is still owed, when it is expected, and what happens if either side backs out. Say those four things plainly, in a message or on a link, and you have sent the document most sellers in this market never quite get around to writing.

The four facts do not change because the format does. A PDF just happens to be wrong about them a week later, and a link does not have to be.

Frequently asked questions