Application started as an educational project, soon to realize that I need it as an internal tool to issue invoices. It communicates with a Shoper (e-commerce SaaS) via REST API to fetch data about orders, ordered products, clients etc. It allows importing bank statement of incoming transfers as csv and bind these payments to customer orders manually or with a consecutive import of a csv file from payment-processing service provider (BlueMedia). Having information about orders and payments together it can issue an invoice, which then can be downloaded as individual PDF or in bulk (zipped).
At the beginning of this project I've made quite an unfortunate call and decided to use vaadin, which at the time, seemed like a perfect tool to easily build frontend. That being said I'm aware of several flaws in the architecture, which I plan to successfully eliminate. Although, since the application is used only as an internal tool and by me alone - I took 'working is better than perfect' approach.
-orange){kind=icon}
-lightblue){kind=icon}
Coming soon…
Here's some of the project's features:
- Display basic sales statistics
- Import payment details from bank statements
- Import payment details from payment processing platform (BlueMedia)
- Issue invoices for delivery services based on processed payments and orders data
- Send issued invoices by e-mail
- Communicate with Shoper SaaS via REST API
- Listen for webhooks about new orders from Shoper Saas
Coming soon…
Technologies used in the project:
- Java 11
- Spring Boot 2.3.1
- Vaadin 14.8.3
- Liquibase
- Docker