Product Feedback
What should we build next?
Receipt Maker is built by one person who reads every suggestion personally. If there’s a template, format, feature, or detail that would make this tool more useful — tell us. We require an email address because every suggestion gets a response, and that’s the only way to send one. Below the form, you’ll find our active roadmap so you can see what’s already on the way.
Submit your idea
No account, no signup. Just your email and your idea. Email is required because every submission gets a personal response — there’s no other way to reach you.
What’s on the way
Live snapshot of what we’re working on, considering, and recently shipped. Updated when things move between columns — not on a fixed schedule.
Building now
Actively in progress. Should ship within the next few weeks.
- Walmart receipt templateBrand-specific format with store ID, TC#, savings line
- Target receipt templateT-store format, RedCard discount, transaction barcode
- “How to make a receipt” guideHub article covering format, components, common scenarios
Considering
On the list. Not committed to building yet — depends on demand and complexity.
- Amazon order receiptsMulti-line orders, shipping breakdown, tax
- Starbucks templateStars rewards, mobile order pickup format
- Best Buy templateSerial numbers, Geek Squad add-ons, return window
- CVS Pharmacy brand variantExtraCare points, brand-specific Rx format
- Airbnb booking receiptsMulti-night, cleaning fees, host details
- Multi-page receipt supportFor long itemized lists that overflow one page
Recently shipped
What we’ve built in the last quarter. Click through to use any of these.
-
Templates index pageBrowse all formats in one place, filter by category
-
Legal guidePlain-English breakdown of when receipt generators are legal
-
Pharmacy receipt generatorHSA/FSA-ready format with Rx and NDC codes
-
Hotel folio generatorMulti-night stays, resort fees, city tax
-
Taxi / Uber / Lyft generatorFare breakdown with distance, time, surge
What we won’t build (and why)
An honest list of things people have asked for that we’ve decided against. Saves you a submission if your idea is here, and helps explain how we think about the product.
Receipts with fake credit card numbers
We let you enter the last 4 digits because real receipts only show 4 digits. We won’t generate fictitious full card numbers — that crosses from “tool for legitimate use” to “tool that aids identity fraud.”
Exact replicas of specific bank statements
Receipts document transactions you participated in. Bank statements are issued by your bank — fabricating them moves from “reconstructing a receipt for a real expense” to “fabricating a financial document.” Out of scope.
User accounts and saved templates
The tool runs entirely in your browser with no server-side storage. Adding accounts would mean handling user data we currently never see. We use browser localStorage to remember your last session, which covers 95% of the value of “saving” without the privacy trade-offs.
A premium / paid tier
Receipt Maker is free, watermark-free, and will stay that way. We make ad revenue from page visits, and that’s enough to keep the lights on. Adding a premium tier would require gating useful features — not what we want this tool to be.
“Aged” or distressed receipt effects
Coffee stains, crumpled paper textures, faded ink — these are aesthetic choices that almost always serve one purpose: making fake receipts harder to detect as fake. We’re not going to ship them.
Bulk-generation API or CSV upload
Generating hundreds of receipts at once is a use-case that’s overwhelmingly fraud-adjacent. If you have a legitimate need (POS system testing, training data), reach out and we’ll discuss — but it won’t be a public feature.
How this works
Do you actually read every suggestion?
Yes. Receipt Maker is built by one person, and every submission lands in my inbox. I read all of them and respond to your email directly — usually within a week.
If I suggest something, will it get built?
Maybe. The honest answer is that suggestions feed into a queue alongside our own roadmap and what we observe from analytics. Things that get built tend to be: (a) requested by multiple people independently, (b) within the scope of “tool for legitimate use,” (c) achievable for a solo developer. Things that don’t get built are listed in the “What we won’t build” section above.
How long does it take to ship a new template?
Brand-specific templates (like Walmart or Target) take about a week of focused work each — researching the format, building the dedicated page, writing the SEO content, generating images. Smaller features (a new toggle, a new currency, a UI fix) can ship in a day. Major features (multi-page support, accounts) might never ship — see “What we won’t build.”
Can I follow up on a suggestion I submitted?
Yes. Reply to whatever email you got back from us, or submit again with “follow-up:” at the start so it’s easy to track. Just don’t submit the same suggestion repeatedly hoping to push priority — that doesn’t work and uses up the trust budget for genuine follow-ups.
Why isn’t there public voting on suggestions?
Voting works for big products with thousands of users. Receipt Maker is small enough that 5 thoughtful email submissions tell us more than 200 anonymous upvotes would. If we ever cross the threshold where voting makes sense, we’ll use a real tool like Canny or Featurebase — not a fake counter we type numbers into.
What if I have a bug to report instead of a feature?
Use this form for that too — just write “bug:” at the start of your suggestion so it gets triaged correctly. Include your browser, operating system, and what you were doing when the bug happened. Bugs typically get fixed within a few days because broken features hurt every user.
Can I email instead of using the form?
Sure. Email us directly at [email protected] — the form just routes to the same inbox with a “feature suggestion” tag for sorting. The form is mostly for people who’d rather not open their email client.