React Laravel Sales System Modifications PDF

Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...

Summary

This document outlines modifications to a React Laravel-based sales system. It details the required characteristics and specifications, including product fields, visible options, and unit selection processes. Clarifications on pricing and additional functionalities are also described.

Full Transcript

React Laravel Sales System Modifications In general, the System must always have the following characteristics: Fast The easiest and most practical to use (the fewer steps to carry out a process, the better) Visually aesthetic (t...

React Laravel Sales System Modifications In general, the System must always have the following characteristics: Fast The easiest and most practical to use (the fewer steps to carry out a process, the better) Visually aesthetic (the graphical environment must be very friendly) Note: If you have a better idea than what I propose, let me know so I can decide. Products module Fields - When a product is created, it must have the following fields: type (product or service, product that is by default), barcode (it must not accept strange characters or spaces), name, brand (selected by default the first of the list), main unit of measure (selected by default the first in the list), cost (0.00 by default), price, category (selected by default the first in the list), warehouse (a list must appear to check the warehouses, the first item on the list must have a check by default) description, model, color (select), presentation (select), warranty, location (select), laboratory (select), lot, size (select), minimum stock, sale according to weight (check), Sunat bag (check), editable price (check), editable name (check), Subject to sale (check), Kardex (check), status (active or inactive, active by default), observations, images. It must go in this order. Visible and More Options - What is in bold in the previous paragraph must be mandatory and must be visible, the rest of the fields are optional, they must be hidden, they must become visible when an option that says “More options” is enabled. This logic must be applied throughout the system, that is, give the user the feeling that it is a simple, simple system with few options; but with the possibility of being able to use more features depending on the user's needs. Selects Fields (Lists) - Select type fields must have a button similar to the following: to be able to add or edit the items in the list, so the user does not have to go to Menu >> Products >> Brands, for example to add or edit a brand. It should be opened in a modal and there you can search, edit, delete or create the item. Fields that have select should have their own view as Marks Prices - A product can have several prices for each unit of measurement Units of measurement - A product can be sold in various units of measurement. The smallest sales unit of measurement will be mandatory, which will be the main one; For example, we can sell pencils by the unit, dozen or box; the unit will be the main one. When the secondary unit of measurement is added to the product, its equivalence must be added, for example, if we add a box, and the box contains 50 units, the 50 must be entered, the price per box will also be entered; In this way, if 2 boxes are sold, 100 units will be discounted. Product containing a set of products - A product can contain other products, for example, if we create the product Christmas basket, we should be able to add that this basket contains, for example: 2 jars of milk, 1 wine, 4 kg of rice, etc. So when a Basket is sold, not only the basket will be discounted but also the products that go inside it. Modify products menu items - It must be visible within products: products, brands, units, categories, then More Options, within this it will go: color, presentation, size, print barcode Warehouses - When a product is created, it must be able to be created in one or more warehouses Disguise - Hide from menu >> products >> Variants (will be used later). Repeated products - There cannot be 2 products with the same code in the same warehouse. - There cannot be 2 products with the same name, brand, model, color, presentation, color and laboratory About prices - To enter the prices of the main unit, the amount can be entered directly, or it must be able to be calculated by entering the profit percentage; For example, if the cost is 100 soles, income as a percentage of 30%, the price will be 130 soles. For secondary unit prices, the same method will be used, only the cost in this case would be = primary unit of measurement cost * equivalence. Menu >> products - Add column cost (before price), status (before created in) - In the unit column (relocate before cost), a select must go, when choosing the unit, the price and cost must change - To the right side of the stock quantity, add the abbreviation of the main unit of measure - In Action, when I click on the eye icon, a modal should open with all the product information. - You should be able to edit all the fields of a certain product - Add “Clone” column, here there will be a button, where it will take you to the creation of a new product. All data for said product will appear except the code; then the user modifies some field and registers it as a new product. - Add filters, so that the filters by Warehouse, type, code, name, brand, category and warehouse are visible. Then a button to display a modal where the model, color, presentation, location, laboratory, size and status filters will appear. - The filter by Warehouse has to be like this: Menu >> Units - “Base unit” will not be used - Add the “order” field, you should be able to sort the units in this section. For example, if a product has several units of measure, when a sale is issued, the system will show you the prices of the units in this order.

Use Quizgecko on...
Browser
Browser