This is a pre-existing project continuation.
Total value agreed = 385 usd. Value of this milestone: 75 usd
REQUIREMENTS:
1. PAYMENT OF SALES
a. Generate installments
b. Each installment should default to “not received”
c. You should have the option to “receive all at once”
d. You should open popupview from the Budget or POS views.
e. Delete Parcels
f. Receive Parcels
2. POINT OF SALE (POS)
a. Product search by product name, or bar code
b. Product search will use barcode reader
c. Product Quantity (Default = 1)
d. Total purchase price discount field
e. Receive purchase (RC)
i. Receipt Form (RECEIPT FORMS)
ii. Installment Form (Default = 1 installment)
f. Budget impression as soon as you confirm purchase
g. Change Calculation
h. Cash Closing (Cash Closing is performed at the end of the day or shift and generates a report. Will be done when using POS as a budget) (FC)
i. Cash Entry (Value placed in Cash for change. It is entered at the beginning of Cash / day. Default value = 0) (EC)
j. Report must own
3. RECEIPTS / CASH INPUTS
a. When approving a budget, either from the budget you created earlier or from the POS, the payment RECEIPT should automatically open and you have the option to pay in installments or not. This View will be different from the Point of Sale, but they are Integrated functions.
b. Filter Receipt Report
i. By date
ii. By Type of Receipts (RECEIPT FORMS)
iii. By seller
iv. Inform which customer received the value
v. In case of division into several installments, the amounts must be received in each installment individually.
vi.
4. WAYS OF RECEIPT
a. Dinheiro
b. Cartão de Crédito
c. Cheque
d. Boleto
e. Depósito Bancário
f. Outro
5. SUPPLIERS
a. Use the fields in portuguese
b. CRUD
6. CARRIER
a. CRUD
7. EMPLOYEES
a. CRUD
i. Nome
ii. CPF
iii. Telefone
iv. Data Nascimento
v. Data Admissão
vi. Endereço
vii. Número
viii. Bairro
ix. Cidade
x. Estado
xi. CEP
xii. País
xiii. Salário
xiv. Comissão
(Name,CPF,telephone,Birth date,Admission date,Address,Number,Neighborhood,City,state,Zip code,Parents,Salary,Commission)
8. TAXES
a. CRUD
i. Id
ii. Companyid
iii. TaxName
iv. Tax rate
v. Descripton
vi. created_date
vii. created_by_id
viii. updated_date
ix. updated_by_id
9. ACCOUNTS PAYABLE / ACCOUNTS PAID
a. CRUD
b. Payments to
i. Providers
ii. Employees
iii. Taxes
iv. Carriers
c. Inform Payment Date, Payment Method, Purchase Invoice (If Available)
d. Reports with filters by
i. Suppliers
ii. Employees
iii. Taxes
iv. Carriers
v. Purchases Made
vi. Expiration Date
vii. Payment Date
viii. Purchase Report
ix. Purchase Invoice
10. STOCK CONTROL
a. cm_stock
b. Inventory control must be synchronized with product sales.
c. [login to view URL] = [login to view URL] + [login to view URL]
d. Inventory Report
e. Movements Report
11. GOOGLE SYNC CONTACTS
a. Must not use third party components or api
b. Contacts / clients will be synchronized with each user's account individually. The user will register only his email and password.
c. The synchronization process should occur in 3 situations:
i. When registering a new customer / contact or when updating customer data
ii. Sending the entire contact list data to Google Contacts
iii. Synchronization of the entire contact list: Sending data to Google contacts and receiving data from Google contacts to the application database.
Hi,
Thanks for the Project.
As discussed, we have already started the work as required.
I have more than the required experience and knowledge to execute the task as required.