No receipt? Designing the policy and screening the request

A no-receipt return is a different transaction from a documented one — different evidence, different risk, different fair payout. Stores that treat it as an ordinary return with missing paperwork get it wrong at both extremes: the generous version becomes a free borrowing service for the neighborhood, and the rigid version loses customers who genuinely bought the thing and lost the proof. This article gives you both halves of the fix — the policy defaults worth publishing, and a screening workflow you can run at the counter in under two minutes.

Where no-receipt requests fit among the broader manipulation patterns — wardrobing, serial returners, receipt fraud — is catalogued in the return-abuse detection guide. This article stays inside its own lane: the intake and screening of the single request in front of you.

Why no-receipt is mostly a counter problem

Online, the receipt barely exists as an object. The order confirmation sits in the customer's inbox, and Shopify can look up any order by email, phone, or name in seconds (Shopify Help Center, accessed November 2026). A web customer claiming to have "no receipt" just hasn't checked their email.

Walk-in retail is different. Markets, pop-ups, gift purchases, cash or card without a registered account — the purchase may exist nowhere except the card statement and the customer's memory. That's the case this article designs for: the person at the counter, with merchandise, and no paper trail. Note what that implies for policy: if you sell only online, your no-receipt policy is one paragraph; if you sell at a counter, it's a real workflow.

The policy defaults worth copying

Four defaults that small stores converge on, because each one bounds a specific risk:

• Lookup before exception. No receipt doesn't mean no record. Email, phone, the card's last four digits — most claims resolve in a search. The exception path exists for the residue.
• Credit-only, not cash, without proof. Unverified ownership gets verified-value compensation. Why store credit is usually the cheaper default — and the cases where cash is still right — is priced out in the store credit versus refund comparison.
• Current selling price, not the original one. You can't verify what they paid; you can verify what it sells for today.
• Frequency cap and ID. One no-receipt exchange per customer per period, recorded against a name and phone number. The cap is what turns "policy" from a vibe into a rule.

One legal anchor worth knowing: in New York, if a store hasn't disclosed its refund policy at the point of sale, customers are entitled to a refund within 30 days on presentation of proof of purchase and the item in original condition (N.Y. General Business Law § 527-a, accessed November 2026). Note the phrasing — proof of purchase, not a paper receipt. A card statement or an order lookup generally qualifies. If your policy is stricter than the law's default, disclosure before purchase is what makes it enforceable.

The intake workflow

Run every no-receipt request through these steps, in order. The order matters: each step either resolves the request or escalates it.

1. Ask where and when it was bought. Not an interrogation — a normal question that also tells the customer you have a process. Genuine buyers answer instantly; the answer also tells you which system to search.
2. Search Shopify by email, then phone, then name. Thirty seconds. If the order appears — regardless of what paper the customer has — treat it as a documented return under your standard policy. In practice most requests resolve here — measure your own hit rate by tagging these for a month.
3. Check the card trail if the customer offers it. Last four digits plus date narrows a card-payment search to one transaction. Don't ask for the full number at the counter; the last four is enough for lookup and safe to record.
4. If no record exists: identify the item by SKU. Pull the current selling price. If the item is discontinued, the policy question gets harder — see the price-lookup section below.
5. Inspect the merchandise. Condition, packaging, tags, accessories. You're not just checking wear; you're checking that it's plausibly an item you sell (version, variant, materials). This inspection is intake screening — run it and log what you see, because the pattern-level analysis of what repeat requests mean belongs to the abuse guide linked at the top of this article.
6. Capture identity. Name and phone number, minimum. Photo ID is the stricter option — worth it for high-value goods — but check your state's rules on recording ID information before making it standard; name-plus-phone is the safe default everywhere.
7. Issue store credit at the current price, log it, cap it. Tag the transaction as no-receipt in your notes or the customer record. The cap enforces itself only if the log exists.

If a step fails, the request doesn't get denied automatically — it gets decided by your policy's exception clause, consciously, instead of by whoever is standing nearest the register.

Screening signals, and what they're worth

The request in front of you either clears or it doesn't. These signals are what a two-minute screen can actually see:

Two caveats. First, most no-receipt requests are legitimate — gifts, lost slips, market purchases — so screen lightly and log consistently rather than suspecting everyone. Second, one weird request proves nothing; patterns across requests are what matter, and pattern analysis is exactly what the abuse guide linked at the top of this article owns.

The price-lookup problem

Crediting current price is simple, but it has a leak: customers who bought during a sale get overpaid.

Worked example (illustrative): PIN-EN-056, an enamel pin, currently sells at $12.00. A customer bought it three weeks ago at $9.50 during a promotion, lost the receipt, and requests a no-receipt exchange for store credit.

Credit at current price: $12.00 — a $2.50 overpay against what was actually paid, roughly 26% over (illustrative).

Is that leak worth fixing? Scale it: at 15 no-receipt credits a month, the drift is 15 × $2.50 = $37.50/month (illustrative). Against the cost of asking every customer for a card statement or rejecting requests the lookup should have caught, the overpay is usually the cheap side of the trade. The refinement worth adopting: credit the current price or the lowest recent sale price for that SKU, whichever is lower. One rule, no per-case judgment, leak mostly closed.

If the item is discontinued, there's no current price to look up — decide the fallback in advance (a flat closeout value from your last recorded price, illustrative, or a documented exception for staff to escalate) rather than inventing it at the counter.

Writing the policy line

One paragraph, published alongside your main policy — the full templates it attaches to are in the annotated return policy template set:

No receipt? We'll look up your purchase by email, phone, or card first — found it, and you're covered by our standard policy. If there's no record, we offer an exchange or store credit at the item's current selling price, with a name and phone number, limited to one no-receipt return per customer per 90 days (illustrative default). Cash refunds require a receipt or order confirmation.

Annotate the tradeoffs for your own store: the lookup-first clause is what keeps the credit path rare; credit-only is what bounds the cash risk; the cap is what keeps the whole thing from becoming a lending library. If any part of your catalog is all-sales-final — consumables, personalized goods — decide now whether the defect path still accepts a lookup-matched return with no paper, because those are the requests your script will actually face; the category decisions live in the all-sales-final guide.

Common questions

Can I refuse a return without a receipt? In the US, generally yes for change-of-mind requests if your policy was disclosed before purchase — that's what the disclosure does. Two limits: some states grant an automatic refund window when no policy is disclosed (N.Y. GBL § 527-a, accessed November 2026), and faulty-goods rights can't be signed away in the UK/EU. Lookup-first exists precisely because refusal should be the exception, not the default.

What price do I credit on a no-receipt return? Current selling price, by default — you can't verify what they paid, but you can verify what it costs today. The refinement worth adding: credit the lower of current price or the item's most recent sale price, which closes the overpay gap on promoted goods (illustrative: about 26% on a $9.50 sale price credited at $12).

What ID should I capture? Name and phone number are the safe minimum everywhere, and they make your frequency cap enforceable. Photo ID is defensible for high-value goods, but several jurisdictions restrict recording ID details — check your state's rules before making it standard policy.

Is store credit instead of cash legal here? Yes, with disclosure. Credit-only for unverified purchases is the norm because the customer can't prove ownership of the transaction — disclose the rule at the counter and on the policy page. The cost logic behind credit as the default payout is the comparison worked through in the store credit versus refund guide linked in the defaults section above.

How often is a no-receipt request actually abuse? Most are gifts, lost slips, and market purchases — screen lightly. What matters is the pattern: repeated no-receipt requests from the same name, the same fragile goods without packaging, the same item family. One request proves nothing; the tracking and pattern analysis of repeat cases is covered in the return-abuse detection guide, which is why the intake workflow above logs every case.

Next step

Write the policy line above into your refund policy page today, then add two columns to your counter notebook or spreadsheet: lookup result (found/not found) and credit issued. Tag for one month. The hit rate on step 2 tells you how often the exception path is even needed, and the log makes your frequency cap real instead of theoretical. If the no-receipt queue turns out bigger than expected, the full copy-paste policy templates — including the addendum this article borrows from — are ready to adapt in the return policy template set.