Every order your shop takes becomes a branded invoice — issued, delivered and chased until it's paid. No spreadsheets, no copy-paste, no awkward reminder emails written by hand at midnight.
InvoiceAuto handles the paperwork in the background, so you can keep selling.
Line items, tax rules and numbering configured once, then applied to every order without being asked.
Each invoice is emailed with a personal download link the moment an order is confirmed.
Follow-ups at 7, 14 and 30 days. They stop the instant payment lands, so nobody gets chased twice.
Sent, viewed, overdue or paid — one dashboard, no reconciling against a bank feed at month end.
Documents are served from separate delivery endpoints. Links expire and are tied to the recipient.
Connect your platform directly, or hand your accountant a clean CSV for any date range.
Most businesses send their first invoice within ten minutes of signing up.
Add your business details, tax rate and numbering once — or connect a supported platform in a single click.
Every confirmed order becomes an invoice with the right lines, currency and due date. Nothing to type.
Invoices are delivered by email with a secure link, and reminders go out until the balance clears.
Every invoice carries its own history. Scroll to walk it.
The moment an order lands, a number is assigned from your sequence and never reused. Tax is computed per line, the PDF is rendered, and the document is frozen — a delivered invoice can only be corrected by credit note.
The email carries a personal link that expires in seven days; the file itself sits behind it in encrypted storage. Bounces are recorded per address, so a typo in a customer record surfaces the same day instead of at day thirty.
Opening the link stamps the invoice with a time and a device class — nothing that identifies the reader beyond what the mail server already logged. That timestamp is what settles the argument about whether a reminder was ever seen.
Scheduled at 7, 14 and 30 days past due, each one re-reads the live invoice before it is sent. A payment that clears at 06:00 cancels the 09:00 reminder, which is the difference between a system that helps and one that embarrasses you.
The payment provider confirms, the invoice closes, the link stops resolving, and the ledger entry is written with the settled amount and the fee. Nothing is left for month-end except reading the summary.
Every invoice, reminder and receipt leaves through sending infrastructure we run — on a domain you verify, or one that is already warmed up for you.
We generate four records per domain and poll DNS until they resolve. Mail leaves from send.yourshop.com, isolated from the mailbox your customers reply to, so a bad batch never touches your reply-to reputation.
No DNS, no propagation, no warm-up. Your invoices go out from [email protected] on infrastructure that has been delivering invoices since launch, with the same events and logs.
Every campaign is sampled against the major mailbox providers, so a reputation slide shows up as a number before it shows up as a support ticket.
Delivered, opened, deferred, bounced — each event moves the invoice state, so “sent” and “seen” stop meaning the same thing.
Hard bounces are suppressed on the first failure. Above 5% bounce or 0.1% complaints the queue pauses itself and pings you, instead of burning the domain.
New domains ramp on a schedule tied to your actual send curve. Dedicated IPs warm in parallel and switch over only when placement holds.
No setup fee, no card required, cancel whenever. All prices in USD.
Priced apart from invoicing, because volume is the variable. Every tier includes invoice templates, delivery events, retries and the same logging.
send. subdomain so your everyday inbox is untouched. If you would rather not touch DNS at all, send from the address we already run: [email protected], live in about a minute.Fifteen minutes with someone who runs the product, not a sales script. We'll map your current invoicing flow and show what would be automated.