Visual Help & Checks

Sign in, register and recover access

1. Confirm DEV versus LIVE.
2. Sign in with the verified account.
3. Check business identity and role.
4. Check pending work separately from internet status.

Check: A wrong password must not create an account. Recovery must retain business history.

Sell / Invoice

1. Select item and customer.
2. Enter quantity and price.
3. Review total, paid and balance.
4. Save once; verify in Documents.

3 packets x Rs.200 = Rs.600. Cash Rs.1,000 means Rs.400 change, not Rs.1,000 in sales.

Check: Invalid values block saving. After interruption, search history before retrying. Confirm one invoice and one stock movement.

Items Master

1. Search before creating a duplicate.
2. Select category and item type.
3. Enter name, unit, price and stock threshold.
4. Save and find the item in billing.

Check: Biscuit 100 g and 200 g remain separate variants. Service lines must not reduce physical stock.

Customers, farmers and suppliers

Name identifies the record. Phone and address are optional contact information. Customers and suppliers have different transaction roles. A customer credit balance is not automatically a loan.

1. Search for an existing contact.
2. Add or select the correct record.
3. Use it on the invoice or supplier note.

Check: Quick customer entry retains the bill. Referenced contacts cannot be removed in a way that breaks saved history.

Farmer Note / Stock In

1. Select supplier and item.
2. Record measured quantities and buying rates.
3. Review the note.
4. Save once and reconcile stock.

New v152 SAMPLE calculation: 25 gross KG minus 1 tare KG = 24 net KG. At Rs.200/KG the amount is Rs.4,800. The redesigned gross/tare layout is not yet integrated into this DEV release.

Check: Quantity increases once; supplier cash payment is not invented. Existing agricultural rules must remain intact during UI integration.

Inventory

Quantity is on-hand stock in the displayed unit. Average cost is not selling price. Stock value uses quantity and cost. Low stock compares quantity with the configured warning level.

1. Filter the category.
2. Read the unit and quantity.
3. Compare stock movements and physical count.

Check: A physical sale reduces stock once; a service does not. Do not compare packet count to KG.

Customer payments

Select the correct unpaid invoice, enter the actual received amount and method, and review the remaining balance. A payment is not another sale.

1. Select invoice and customer.
2. Enter actual money received.
3. Save one payment.
4. Reconcile invoice balance and collection report.

Rs.1,000 invoice minus Rs.400 payment leaves Rs.600 outstanding.

Check: Retry protection prevents duplicate collection. A wrong customer/invoice must not be silently accepted.

Staff and staff payments

1. Owner selects the staff member.
2. Enter actual payment information.
3. Save once and check the report.

Check: Staff-payment access depends on package and role. Attendance, leave and full payroll remain separate planned development.

Saved documents and receipts

Type, date range and search narrow the results. Open the correct saved invoice or supplier note before reprinting or sharing. Editing/correction requires the existing permission and audit rules.

1. Choose type and dates.
2. Search the document number.
3. Open and check saved totals.
4. Print/share only the intended record.

Check: History is not erased by changing a business category. Clearing a new draft is not a refund of a saved invoice.

Reports, preview and export

Choose From / To, transaction type, staff and detail/grouped view. Use Preview, PDF or Excel for that exact scope. Review the recipient before WhatsApp sharing.

1. Set filters.
2. Review detailed rows.
3. Compare sales, collections and expenses separately.
4. Export and verify totals.

Check: A credit sale and its later repayment may appear on different dates. Exported totals and translated names must match the selected report.

Company settings, subscriptions and backup

1. Verify business and owner role.
2. Change only intended settings.
3. Save and review confirmation.
4. Verify new output and preserve old history.

Check: No profile/bank data appears in another business. Never treat an email queue as proof that a recoverable backup arrived. OnePay checkout remains disabled on DEV.

Safe system observations

These checks do not change POS records, clear storage, start a camera, send SMS or take a payment. Connection/API presence is not proof of a completed business workflow.

For support: provide environment, version, time, error and redacted screenshot. Never provide passwords, tokens, full ID images or a full customer dump.