Veltadoc
Bulk generate hundreds of invoices, payslips & certificates
1 follower
Bulk generate hundreds of invoices, payslips & certificates
1 follower
Veltadoc turns a spreadsheet into hundreds of branded PDF documents in one batch. Upload a CSV or Excel file, map your columns to a template once, and generate invoices, payslips, certificates, purchase orders, and more, all downloadable as a single ZIP. Saved mappings and custom branding available on Pro. Free plan available, no card required.
Free Options
Launch Team / Built With
Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free
Promoted
Hey Product Hunt,
I'm the only person behind Veltadoc, built it alone with basically no budget. It's a tool that turns a spreadsheet into a batch of branded PDF documents. You upload a CSV or Excel file, match your columns to a template once, and it generates every document in one go. Invoices, payslips, certificates, purchase orders, and a bunch of other document types.
A few things that make it different from just using a regular template. The column mapping gets saved, so the next time you run a batch it takes seconds instead of redoing everything. Rows with the same invoice number automatically group into one document with multiple line items, instead of turning into separate files. And your logo, colors, and signature get applied across every document without touching each one individually.
On the infra side, since I'm running this solo with zero budget, the PDF rendering actually happens on my own PC at home, connected through a Cloudflare Tunnel so it stays online all the time. I know that sounds risky, but it's held up fine even under load testing with hundreds of documents at once, and it's been more reliable than the serverless setup I started with.
Free plan is ten documents a month with a watermark, no card needed. Pro removes the watermark and the cap for twelve dollars a month.
This is very much still early days for Veltadoc, and I'm planning to keep working on it full time. If people find it useful here, that's what tells me where to put the effort next, whether that's making the render pipeline even more solid or building out new document types and features people actually ask for.
Would love to hear what you think, especially if you deal with repetitive document work yourself. I'll be around all day :)