Farmer services & equipment Clear rates KYC-verified partners +91 9133471515|kisansahakar@gmail.com

Frequently Asked Questions

Answers to the most common questions

No. You can open equipment grids, produce listings, resale dossiers, help articles, and this FAQ without signing in. You need an account only when you raise a booking, submit a logistics request, use the cooperative cart ledger, manage listings, or access role-specific dashboards (for example FPO or service-provider consoles).

Use Contact Us on the portal, phone +91 9133471515 (Mon–Sat, 09:00–18:00 IST), or email kisansahakar@gmail.com. Programme and business enquiries can also reach info@glansa.com. We aim to reply to written enquiries within one business day.

Kisan Sahakar is a public desk–style portal for farmers and FPOs to discover machinery, trade produce, plan logistics, and complete verified resale—all with quotations, bookings, and handoffs surfaced in one cooperative-friendly workflow.

Open Equipment booking or Machine catalog, filter by machine type or provider, review indicative rates (per hour, day, acre, or seasonal window where shown), then use Book or Raise request. Logged-in members can attach plot or crop hints so coordinators route the job to an available fleet faster.

Published references are indicative: they mirror last-known desk quotes so you can compare before committing. Exact charges depend on season, attachments, mobilisation distance, overtime, diesel/fuel clauses, or district surcharge rules. Confirmation happens after the provider acknowledges the booking and—you where applicable—a coordinator approves programme terms.

Machine Catalog emphasises searchable discovery across fleets and cooperatives—great for benchmarking models. Equipment Booking deep-links curated lanes with filters aligned to cropping windows and FPO onboarding. Both feed the same cooperative booking pipeline; choose whichever view your desk prefers.

Produce marketplace aggregates graded harvest lines with ₹/kg references, packaging notes, and logistics cues. Sellers (farmers/FPO desks) publish lots; buyers shortlist cooperative carts similarly to scheme monitors. Settlement paths follow your cooperative’s approved workflow—cart totals in Cart help reconcile before gateway capture.

Yes. After you list harvest, keep contact numbers accurate and watch desk notifications. FPO coordinators can maintain lots on behalf of members when their role permits. Update availability or grade changes promptly so buyers see trustworthy information.

Use Logistics booking to enter origin, destination, vehicle class, and weight band. Indicative per-km or load-based quotes help members budget; partner allocation depends on fleet availability and district rolling permissions. Combine logistics with produce lots when your desk wants a single visible trail.

Resale focuses on implements and assets with hour-meter or inspection metadata so buyers can shortlist cooperatively. Treat listings as pre-handoff dossiers: physical verification and compliance remain between buyer, seller, and programme rules before funds move.

Cart merges hire lines, kg-based produce totals, resale asks, and logistics estimates into one indicative ledger before payment readiness. Desk teams use it exactly like consolidating paper registers—minus duplicate phone tag—so approvals and gateways see the same totals.

Start from Register and choose the lane that mirrors your onboarding pack (individual farmer/village cadre/FPO/driver/service partner). Each path collects KYC-aligned fields mandated by admins. Incomplete documents pause publishing until validations clear—matching cooperative audit norms.

Verified partners display trust badges sourced from onboarding documents (GST/PAN/Aadhaar patterns, RC, insurance uploads—subject to administrator review). KYC lowers fraud risk on high-value hires and assures FPO auditors that subcontractors meet programme expectations.

No. Kisan Sahakar is a digital desk layer that records enquiries, compares rates, and routes confirmations. Governance, member resolutions, credit committee decisions, and statutory filings remain with your FPO or supporting institution.

Authorised admins use monitoring tools (booking queues, approvals, payouts) mirrored to programme SLAs discussed during roll-outs. Transparency counters on the gateway highlight public visitation where enabled—similar to departmental pilot dashboards that reset during infrastructure recycle windows.

Use the header language affordance—Google Translate is wired for multilingual communities. Automated translation quality varies by term (especially scheme acronyms), so bilingual desks often keep Telugu/Hindi cheatsheets beside their monitors for critical confirmations.

OTP channels exist to reduce password friction for field users. Use them only on official login modals. Never paste OTPs into email or chat. Marketing usage—if any—follows the consent collected at registration; raise objections through support with your member ID for traceability.

Capture the booking or cart reference ID, timestamp, provider name, and plot details, then escalate via desk phone or ticketing. Coordinators reconcile against partner SLAs—weather skips, tractor breakdowns, and mandi arrivals each have playbook notes in the Help Centre depending on rollout phase.

Current versions of Chromium (Chrome/Edge), Firefox, or Safari with JavaScript enabled. Government-issue Windows PCs often lag behind—upgrade when IT policy allows because older browsers break accordions and Web API calls powering dynamic catalogues.

The portal does not guarantee commodity prices or mechanical uptime—it exposes structured information so members negotiate with evidence. Contracts, indemnities, guarantees, insurance pay-outs, and penalty clauses remain between the cooperating parties and applicable law—not the catalogue UI.

Spray-drone or sensorised packages appear inside equipment grids when verified operators onboard. Filters surface licensed operators where metadata exists. Confirm DGCA/geo-fencing prerequisites with your facilitator before deploying over standing crop.

Before calling, gather FPO/account ID, booking or cart IDs, handset screenshots (if UI glitches occur), approximate acreage/km-distance, commodity grade, preferred delivery window, and any programme codes issued by facilitators. The desk resolves most tickets when those five datapoints arrive together.