Invoices that issue themselves the moment an order qualifies
Auto-invoicing in easySales is an automation-flow action, not a fixed rule bolted to a status. You choose the trigger, add the conditions that matter to your business, and the document is generated without anybody opening the order.
- Trigger on order creation, status change, payment or your own conditions
- Different rules for prepaid and cash-on-delivery orders
- Failures are retried rather than silently skipped
HOW IT WORKS
Three choices and you are done
The same builder that powers every other flow.
Choose the moment
Order created, status changed, payment confirmed, order finalized, or any other order trigger the flow engine exposes.
Add your conditions
Filter on payment method, channel, order value, customer type, country or any other order property before the invoice is created.
Pick the document
Fiscal invoice or proforma, from the series you nominate, in the language your buyer expects.
Invoicing by hand vs by rule
The work does not change. Who does it does.
Doing it by hand
- Open each order and click generate
- Remember which orders should wait for payment
- Batch-generate at the end of the day and hope nothing was missed
- Discover an unissued invoice during month-end close
- Re-do the batch when the provider was rate-limited
With easySales
- Invoices exist before your team logs in
- Prepaid and COD orders follow different rules automatically
- Conditions decide, so nothing is forgotten
- Month-end close finds nothing missing
- Failed generations are retried on their own
FLOW-DRIVEN INVOICING
One rule per business case, not one click per order
Different rules for different payment methods
Prepaid orders can be invoiced on arrival because the money is already in. Cash-on-delivery orders usually should not be, because a refused parcel means storno work. Two flows, two conditions, and the distinction stops depending on somebody remembering it.
Chain the whole document set
An invoice is rarely the only thing an order needs. The same flow can generate the shipping label, produce the warranty certificate, print everything to the bench printer and notify the customer — in order, from one trigger.
Submission handled in the same pass
Where your market requires electronic submission, the flow can generate the document and submit it. Generation and submission are separate layers, so a problem at the authority never leaves you without an invoice.
Run it on demand when you need to
A flow does not only fire on its trigger. You can run it manually against a selection of orders, which is how you backfill the batch that slipped through while a provider was down.
"Invoices before we arrive"
"COD handled correctly"
"Nothing missed at close"
What else a flow can do at the same time
Ready to stop clicking generate?
Build one invoicing flow and let every qualifying order produce its own document.
Start free trialFrequently Asked Questions
Have a question? Contact us and we'll be happy to help.