FULFILLMENT
Service for marketplaces
INTRODUCTION
FULFILLMENT
Service to simplify work with marketplaces such
as OZON, WB, etc. Seller (individual entrepreneur) transfers part of the operational tasks to the fulfillment service.
Service to simplify work with marketplaces such
as OZON, WB, etc. Seller (individual entrepreneur) transfers part of the operational tasks to the fulfillment service.
Purchasing products from a specific supplier
Collection of products from the supplier to our own warehouse, temporary storage
Packaging of products according to the requirements of a specific marketplace
Marking (bar coding)
Collection of products in the delivery box
Shipment of products to the distribution warehouse of the marketplace
Invoicing to the seller
The main problem of existing fulfillment services is the lack of control, consistency and digitization of business.
Most of the services work with clients trough Telegram chats, Google Sheets and verbal requests.
Therefore, the human factor often affects: they did not purchase some products, did not have time to pack, or forgot to ship the batch.
And for most sellers, such errors and downtime are critical to their business, this is described by such a term as 'lost profits'
RELEVANCE
The goal of the project is to implement the backend part of a full-fledged REST application fulfillment service with the following features:
Goals
Planning places of purchase (markets, suppliers) dates of purchase and shipment
Creation of terms (tasks) to the relevant departments of the fulfillment service
Creating a purchase, packaging and shipment appointment
Registration of clients, authorization
Analysis, editing of goods
Placement of goods for the client
Tracking the implementation of appointment, payment on applications
Notification of customers and service employees by email
DATABASE
7 tables
OneToMany and ManyToOne dependencies (Bidirectional)
Uniqueness Constraints
The "Packaging" entity is an Enumeration type
ARCHITECURE
- Interacting with PostgreSQL database using JPA Repository
Basic business logic in Service classes
Controllers operate on Dto entity classes
- Mapping (conversion) Dto to Entity and vice versa is implemented in Mapper classes
Authorization and authentication are implemented using JWT tokens, separation by roles is implemented using Sequrity FilterChain
- The main sections of the project are implemented using Generic classes and interfaces to support the principles of OOP
ROLES
- CLIENT
- Registration on the site
- Change profile
- Adding products
- View your items
- Viewing Your Confirmed Items
- View all markets
- View all purchase dates and locations
- View all shipping dates
- Creating an application for FF services
- View all your applications
- MANAGER
- All functionality of the Client
- Changing profiles
- Soft-deleting a client profile
- View All Clients
- Adding new products
- Adding an Existing Product to a Customer
- Product confirmation
- Deleting a product
- View all products
- Deleting, changing purchase and shipment
- Change in the procurement market
- View all applications
- Transfer of the application to the status of "completed" and "paid"
- View all outstanding and unpaid tickets
- Data export to purchasing, packaging and shipping departments
- ADMIN
- All functionality of the Client and Manager
- Registration of a new manager
- Import of data tables into the database (markets, purchases, shipments)
- Single data addition (markets, purchases, shipments)
MAIN BISINESS LOGIC
Main funcionality of ADMIN_ROLE
- Purchasing market planning
- Drawing up a procurement schedule for the next period (month)
- Drawing up a schedule of shipments for the next period (monthly)
- Adding new managers
Main functions of the Administrator
Working with the functionality of the "Administrator" role is shown through Swagger-ui
Main funcionality of CLIENT_ROLE
- Registration (login and mail are unique)
- View, edit profile (only your own)
- Adding a new product
- View all / confirmed products (only your own)
- View the schedule of purchases and shipments
- Creation of applications for the full cycle of work
- Viewing and editing created requests (only your own)
- Deletion of the application (no later than one day before the purchase)
Main functions of the Client
Working with the functionality of the "Client" role is shown through Swagger-ui
Main funcionality of MANAGER_ROLE
- Work with products (confirmation, editing)
- Adding a new product to a user
- Work with applications (view all, unfulfilled, unpaid)
- Transition of the application to the status "Completed", "Paid", email notification of the client about the event
- Issuance of work orders for the purchase, packaging, shipment of products to the relevant departments (output to a .csv table or sending by mail to the responsible person)
- Soft client removal
Main functions of the Manager
Working with the functionality of the "Manager" role is shown through Swagger-ui
TECHOLOGIES
Logging
Logging implemented using AOP (Aspect Oriented Programming) and saving logs to files
Spring Security
Authorization and authentication are implemented using JWT tokens.
Import and export data to .csv tables
Working with .csv tables is implemented using OpenCSV technology. An auxiliary class was written with Generic methods for converting from a table to an entity and vice versa.
Error processing
Error handling for the client is done through a helper method, the @ControllerAdvice controller. Implemented a package of custom exceptions for error typing
Docker
Implemented deploy applications and databases in Docker
Documentation
Application code is fully documented with JavaDoc
Testing
Implemented integration testing of all controller methods
CONCLUSION
Implemented a full-fledged REST application with the business logic of the fulfillment service
The project reflects and implements all stages of the seller's work with the fulfillment service, the functions of the manager and administrator are programmed
The actual technologies for developing the backend part of web services were used, namely:
Java 17, Spring boot, Spring web, REST Api, Spring Security, Spring AOP, ORM Hibernate, PostgreSQL, Docker, Tests, etc.
Implemented additional functionality for importing / exporting information for fulfillment service employees (OpenCSV technology)
Implemented email notification of users, sending work orders to fulfillment service employees by departments (Spring Mail technology)
The project reflects and implements all stages of the seller's work with the fulfillment service, the functions of the manager and administrator are programmed
The actual technologies for developing the backend part of web services were used, namely:
Java 17, Spring boot, Spring web, REST Api, Spring Security, Spring AOP, ORM Hibernate, PostgreSQL, Docker, Tests, etc.
Implemented additional functionality for importing / exporting information for fulfillment service employees (OpenCSV technology)
Implemented email notification of users, sending work orders to fulfillment service employees by departments (Spring Mail technology)
