# Custom WordPress Plugin Development in Nepal

> WebApp Nepal writes custom WordPress plugins for needs off-the-shelf plugins can't meet, such as eSewa/Khalti payments, school or cooperative portals, BS calendar and Nepali SMS.

Source: https://webappnepal.com/service/wordpress-plugin
Provider: WebApp Nepal, Kathmandu, Nepal
Updated: 2026-08-07T21:07:55.000000Z

A Pokhara resort owner approached WebApp Nepal after three separate plugin purchases failed to solve the same problem: guests arriving at checkout could not pay through eSewa because none of the WooCommerce payment plugins on the market handled eSewa's HMAC-SHA256 merchant credential signing in the way eSewa's production API actually required. The fourth plugin he found was an open-source project abandoned in 2021 with no support thread responses since before eSewa changed its endpoint structure. He had spent NPR 45,000 across those four purchases, the problem was still unsolved, and he was routing every booking through a manual WhatsApp confirmation flow that his front desk staff spent three hours a day managing. The conversation with WebApp Nepal lasted forty minutes. A custom eSewa payment plugin was built, tested in sandbox, validated in production, and deployed on his site within ten days. Checkout abandonment dropped immediately. Front desk time on payment chasing dropped to near zero. The plugin has run without modification for fourteen months.



That situation is not unusual in Nepal's WordPress ecosystem. The global plugin marketplace is built for global markets - for Stripe and PayPal, for US state tax structures, for English-language SMS gateways, for postal code formats that bear no relation to how Nepal addresses work. Nepal businesses trying to use off-the-shelf plugins for Nepal-specific requirements - eSewa and Khalti payment flows, Sparrow SMS OTP delivery, Bikram Sambat date handling, NRB-format financial reporting, IRD VAT-compliant invoicing, Devanagari text in PDF generation - find themselves either using plugins that require significant workaround hacks to function or that simply do not work in Nepal's specific API environment at all. A custom WordPress plugin built for Nepal's actual technical conditions is not a luxury for larger projects. It is the only solution that actually works.



WebApp Nepal builds custom WordPress plugins for Nepal businesses and organisations across every sector: eSewa and Khalti payment gateways for WooCommerce and custom checkout flows, school and college management plugins with BS-calendar academic year handling and NEB-format result generation, cooperative member portal plugins with savings passbook and loan statement access, hotel and trekking booking inquiry management plugins with automated WhatsApp and email follow-up, real estate listing plugins with Nepal land measurement units and Kathmandu Valley locality filtering, hospital appointment and OPD scheduling plugins, cooperative and microfinance plugins with NRB-format report generation, and HR payroll plugins with EPF, CIT, and Nepal income tax slab calculations. The Nepal-specific depth in each of these is not something that can be retrofitted from a generic international plugin. It has to be built from the start by developers who understand how Nepal's systems and regulations actually operate.




#### What a Custom WordPress Plugin Is and Why Nepal Businesses Need One



A WordPress plugin is a software module that extends what WordPress does beyond its core content management function. A contact form is a plugin. A payment gateway is a plugin. A booking system is a plugin. The difference between a custom plugin and a downloaded plugin is the same as the difference between a custom website and a template: a downloaded plugin is built for a generic global market and a custom plugin is built for the specific business, the specific audience, and the specific technical environment in which it will operate. For most Nepal businesses, that difference is decisive. Nepal's payment gateways authenticate through merchant-specific HMAC signatures that differ from the signature methods used by Stripe or Razorpay. Nepal's SMS gateways - Sparrow, Aakash, Prabhu - use their own API structures. Nepal's financial regulations impose specific reporting formats that international accounting plugins do not generate. A custom plugin built for a Nepal business handles these requirements correctly from the first day of operation because they were engineered in as requirements, not discovered as incompatibilities after deployment.



Beyond Nepal-specific integrations, custom plugins solve the performance and security problem created by installing multiple off-the-shelf plugins to approximate a capability. A WordPress site with twenty plugins installed is a site with twenty separate code bases, each maintained by a different developer on a different update schedule, each introducing its own database queries, its own JavaScript and CSS assets, and its own potential conflict points with other plugins and the theme. The Sucuri Security team's research consistently finds that outdated or poorly coded plugins are the primary vector for WordPress site compromise. A custom plugin delivers exactly the functionality the business needs - nothing more - in a single, internally consistent code base that the development team fully controls and can maintain without dependency on a third-party vendor's update decisions. For Nepal businesses operating sites that process payments, manage member data, or handle sensitive client information, the security argument for a custom plugin is as strong as the functional argument.




#### Custom Plugins WebApp Nepal Builds for Nepal




##### eSewa and Khalti Payment Plugins



eSewa and Khalti are Nepal's two dominant digital payment platforms, accounting for the majority of non-cash transactions on Nepal e-commerce, booking, and fee collection websites. Building a correctly functioning integration with either platform is more technically demanding than it appears from the API documentation. eSewa's merchant payment flow requires HMAC-SHA256 signature generation using merchant-specific secret keys, signed request parameters in the exact format eSewa's server expects, and a post-payment webhook verification call to confirm the transaction reference against eSewa's payment verification endpoint before any order is marked complete. Skipping the webhook verification - the step most plugin developers skip because it is not obvious in the basic documentation - means that a spoofed payment notification can mark an order as paid without the payment having occurred. WebApp Nepal builds eSewa plugins with the full verification chain: HMAC signature generation, redirect handling, webhook capture, payment verification API call, and conditional order status update. Khalti's OAuth2-based payment flow and webhook structure are implemented at the same standard. Both integrations are tested end-to-end in sandbox before production deployment and validated again with live test transactions before the plugin is considered ready for client handover.




##### WooCommerce Nepal Extension Plugins



WooCommerce is the most widely used e-commerce platform for WordPress, but its core does not handle the requirements of Nepal's e-commerce market correctly. Shipping zone configuration by Nepal's seven provinces and 77 districts is not supported out of the box. Nepal's dominant land measurement units for real estate - ropani, aana, paisa, dam in the hills; bigha, kattha, dhur in the Terai - have no equivalent in WooCommerce's measurement system. VAT at Nepal's 13% rate with IRD-compliant invoice formatting in PDF is not generated by WooCommerce's default tax invoicing. COD with advance payment options and delivery day routing for Kathmandu Valley's area-based delivery networks are not built into the standard checkout. WebApp Nepal builds WooCommerce Nepal extension plugins that address these gaps specifically: Nepal province and district shipping zones with delivery day calculation, NPR currency configuration with NRS symbol display, eSewa and Khalti checkout integration as described above, IRD VAT invoice generation with taxpayer number fields, Nepal address format with tole, ward number, and municipality fields, and festival-season pricing plugins for Dashain, Tihar, and other high-purchase periods.




##### School and College Management Plugins



Nepal schools and colleges using WordPress as their content management system need a layer of functional software on top of the CMS: student admission intake forms feeding into a student database, examination result publication with NEB-format grade display, fee payment tracking with eSewa and Khalti receipt generation, teacher and staff directory management, academic notice and circular publication, library book record management, and BS-calendar academic scheduling. These are not features that any publicly available WordPress plugin delivers for Nepal's specific academic structure. The NEB's SLC and SEE grading systems, the BS academic year starting in Shrawan and ending in Ashadh, and the specific fee structures of Nepal's educational institutions require plugins built from the ground up for Nepal's educational context. WebApp Nepal builds school management WordPress plugins as modular components - each functional area as a separate sub-module - so schools can start with the components they need immediately and add additional modules as their requirements grow.




##### Cooperative and Microfinance Member Portal Plugins



Nepal's savings and credit cooperatives are legally required to maintain member records and financial reporting in formats that the NRB's cooperative supervision division specifies. A cooperative operating a WordPress website that wants to offer member-facing portal access - savings passbook viewing, loan statement access, dividend announcement, meeting notice, share certificate download - needs a plugin built to the cooperative's actual account structure and reporting requirements. WebApp Nepal builds cooperative member portal plugins that authenticate members against the cooperative's existing member database, display transaction history in passbook format with BS dates, show loan outstanding and instalment schedule, publish meeting and AGM notices to member-specific notification, generate share certificate documents, and export NRB-format reports for the cooperative's management committee. These plugins operate as an interface layer over the cooperative's existing data - they do not replace the core cooperative accounting software but surface the data that members need access to through a web portal.




##### Hotel and Trekking Inquiry Management Plugins



Hotels and trekking agencies using WordPress need more than a contact form. They need a structured inquiry management system: a form that captures the specific information needed to respond to a travel inquiry (travel dates, party size, room type preferences, trek route, fitness level, dietary requirements), an admin inbox that shows all open inquiries with follow-up status tracking, automated acknowledgement emails to the guest with the inquiry details and a WhatsApp contact link for immediate communication, and notification to the relevant staff member by email or SMS when a new inquiry arrives. WebApp Nepal builds custom inquiry management plugins for Nepal's hospitality and trekking sector with these requirements as the functional baseline. Trek route selection dropdowns are populated with the agency's actual trek portfolio. Room and package selection matches the property's actual inventory. Follow-up status workflow (new, acknowledged, quoted, confirmed, rejected) gives the reservations team a clear view of the inquiry pipeline without a separate CRM. For agencies managing high inquiry volumes, bulk inquiry export to CSV for offline management is included.




##### HR and Payroll Plugins



Nepal businesses using WordPress as their internal operations platform - often smaller businesses that want to keep their tools consolidated rather than subscribing to separate HR software - need payroll calculation that follows Nepal's actual deduction rules. Employee provident fund (EPF) at 10% employee and 10% employer contribution on basic salary. Citizens Investment Trust (CIT) contribution where applicable. Income tax calculation on the Nepal Government's tiered tax slabs, with the Inland Revenue Department's tax exemption thresholds for individuals and couples. Gratuity calculation after five years of continuous service under the Labour Act. Festival allowance provisions. These calculations cannot be handled by any international payroll plugin because Nepal's tax and labour structure is entirely specific. WebApp Nepal builds Nepal HR and payroll WordPress plugins for businesses managing payroll internally: employee record management, monthly salary slip generation with EPF, CIT, income tax, and advance deductions calculated correctly, annual tax statement generation (for employee Form 16 equivalent), and leave management with Nepal public holiday calendars in both BS and AD.




##### Real Estate Listing Plugins



Nepal's real estate websites need property listing functionality built for how Nepal land and property is described and searched. Land area in Nepal is measured in ropani-aana-paisa-dam in the hilly districts and bigha-kattha-dhur in the Terai - not square metres or square feet, which are used only for built-up area measurement. Property location in Nepal is described by district, municipality or VDC, ward number, and tole - not by a postal code. Kathmandu Valley buyers search by specific localities (Lazimpat, Nakkhu, Khumaltar, Bhaisepati, Budhanilkantha) that are not mapped by any international real estate plugin's location taxonomy. WebApp Nepal builds custom real estate listing plugins for Nepal property websites: property listing custom post types with Nepal-format land area inputs, province and district taxonomy, Kathmandu Valley locality taxonomy, NPR price display with price per ropani or per square feet as appropriate, filterable property search by location, property type, and price range, map integration with Nepali location pinning, and direct WhatsApp inquiry links with pre-filled property reference in the message.




##### Nepali Calendar and Date Handling Plugins



Bikram Sambat is Nepal's official calendar system. Government documents, academic calendars, cooperative financial records, court dates, and most formal Nepali correspondence use BS dates. Any WordPress plugin that handles dates for a Nepal audience - booking calendars, event scheduling, academic notice dates, financial reporting periods, deadline reminders - needs to handle BS-to-AD and AD-to-BS conversion correctly, display dates in the format Nepali users expect, and calculate date arithmetic (days between dates, instalment due dates, academic year durations) in BS. WebApp Nepal builds Nepali calendar plugins that handle this conversion and display correctly for all WordPress post types, custom fields, and plugin-generated date outputs. The conversion library used is validated against the official NRB calendar rather than approximation algorithms that accumulate errors across the calendar's non-uniform month length structure.




##### Devanagari and Bilingual Content Plugins



WordPress handles Unicode text without modification, but displaying Nepali Devanagari content correctly - with appropriate fonts, line-height, letter-spacing, and text rendering for the range of screens Nepal users use - requires deliberate implementation. WordPress's default TinyMCE and Gutenberg editor experiences for Devanagari input are adequate but not optimised: auto-correct behaviour interferes with Devanagari conjunct consonants, spell checking flags correct Nepali words, and font selection defaults to system fonts that render inconsistently across Android and iOS. WebApp Nepal builds bilingual content management plugins for Nepal websites that need both English and Nepali content: language toggle implementations that switch content without a full page reload, Devanagari-optimised editor configurations with the correct font stack applied in the editing view, hreflang metadata generation for bilingual sites, and Nepali date display options in content that shows dates to users.




#### How the Plugin Development Process Works




##### Requirements and Specification



Every custom plugin project begins with a detailed requirements session. WebApp Nepal documents the exact functional requirements of the plugin: what inputs it receives, what processes it runs, what outputs it produces, how it stores data in the WordPress database, what admin interface is needed, what user permissions apply to which functions, and what third-party APIs or systems it must communicate with. For payment integrations, the API documentation from the payment provider is reviewed in detail - not the summary documentation that often describes the happy path without covering error handling, signature validation, or webhook retry behaviour. For Nepal-specific data processing (BS date calculation, Nepal tax rules, NRB reporting formats), the source of authoritative data is identified before development begins. A written specification document is produced before any code is written, reviewed with the client, and agreed before development starts. Changes to requirements after the specification is agreed are documented as scope changes and handled transparently.




##### Development Standards



WebApp Nepal builds custom plugins to WordPress's published coding standards for PHP, JavaScript, CSS, and security. All database interactions use WordPress's $wpdb class with prepared statements - never direct string interpolation into SQL queries, which is the origin of the SQL injection vulnerabilities that compromise WordPress sites. All user-facing output is escaped with the appropriate WordPress escaping function (esc_html, esc_attr, esc_url, wp_kses) before it is rendered to the page - preventing the XSS vulnerabilities that allow injected JavaScript to run in admin sessions. All form submissions include nonce verification - a WordPress security token system that prevents cross-site request forgery. All file operations sanitise input paths. These are not optional practices that WebApp Nepal applies to some projects and not others. They are the standard that every line of code in every plugin is held to because the alternative is building a vulnerability into the client's site that becomes the entry point for a breach.




##### Testing and Deployment



Custom plugins are tested in a local WordPress development environment that mirrors the client's production server configuration - same PHP version, same WordPress version, same active theme and plugin set. For payment integrations, the full payment flow is tested in the payment provider's sandbox environment and then in production with a minimal live transaction before the plugin is deployed. Form submissions are tested with valid data, invalid data, missing required fields, and malformed inputs to verify that validation and error messages function correctly. Admin interface actions - delete, update, export - are tested with the correct user permissions and with insufficient permissions to verify that unauthorised actions are blocked. After client sign-off on testing, deployment to the production site is executed during a low-traffic window with a pre-deployment backup taken immediately before. Post-deployment verification runs the key user journeys to confirm the plugin is functioning correctly on the live server before the deployment is considered complete.




##### Documentation and Handover



Every custom plugin WebApp Nepal delivers includes a written operations document: how to install and activate the plugin, how to configure each setting, how to use the admin interface, what each shortcode does and what parameters it accepts, and what to do if common problems occur. For plugins that require configuration in third-party systems - eSewa merchant credentials, Khalti public keys, Sparrow SMS API keys - the document includes step-by-step instructions for obtaining and entering those credentials. Source code is delivered in a clean, commented state with an explanation of the plugin's architecture. Maintenance retainer options are offered for businesses that want ongoing support: plugin updates for WordPress version compatibility, monitoring for payment API changes that require integration updates, and minor feature additions within agreed scope. Plugins built by WebApp Nepal are owned entirely by the client - there is no licensing fee, no subscription, and no dependency on WebApp Nepal's continued operation to keep the plugin running.




#### Why Custom Over Off-the-Shelf for Nepal




##### Nepal Payment APIs Are Not Supported by International Plugins



eSewa and Khalti are used by tens of millions of Nepali users. They are not supported by any of the major international WooCommerce payment plugin providers - Stripe, Braintree, Square, PayPal. The Nepal-specific payment plugins available on WordPress.org and the premium plugin marketplaces are predominantly built by individual developers, often with incomplete webhook verification, no active maintenance as eSewa and Khalti update their APIs, and no support infrastructure. The cost of a payment integration failure on a live e-commerce site - lost sales, customer trust damage, bank dispute processes - is significantly higher than the cost of a correctly built custom integration. WebApp Nepal's custom payment plugins are built to the current production API specifications of both eSewa and Khalti, maintained as those APIs change, and supported by the same team that built them.




##### Nepal Regulatory Requirements Are Invisible to International Plugin Developers



Nepal's IRD invoice format requirements, NRB cooperative reporting formats, EPF and CIT deduction rules, Nepal income tax slab calculations, and Labour Act provisions for gratuity and festival allowance are not problems that plugin developers in Europe, North America, or even India have built solutions for. They are Nepal-specific regulatory requirements that require Nepal-specific implementation. A payroll plugin built for India handles GST, PF under India's EPFO rules, and income tax under India's Finance Act - none of which applies in Nepal. A plugin built for Nepal handles EPF under the EPFO Nepal rules, income tax under Nepal's Income Tax Act, and VAT under Nepal's VAT Act. The developer who understands these requirements is in Nepal, building for Nepal. WebApp Nepal is that developer.




##### Performance Starts at Zero with Custom Code



An off-the-shelf plugin loads its full CSS and JavaScript on every page of a WordPress site, whether or not the plugin's functionality appears on that page. A WooCommerce payment plugin loads payment processing JavaScript on blog posts and about pages where no payment ever occurs. A booking plugin loads its calendar library on the home page where no calendar is displayed. This unnecessary asset loading degrades Core Web Vitals scores - particularly Largest Contentful Paint and Total Blocking Time - for every page of the site, not just the pages where the plugin is active. Custom plugins built by WebApp Nepal load assets only on the pages and in the contexts where they are needed, through WordPress's conditional enqueueing system. The performance difference between a site with eight off-the-shelf plugins and the same site with two purpose-built custom plugins is consistently measurable in PageSpeed Insights mobile scores - and those scores directly affect Google Search rankings for Nepal businesses competing in increasingly contested organic search markets.




##### Ownership and Longevity



A purchased plugin creates a dependency. The plugin developer decides when to update it, whether to maintain Nepal API compatibility as eSewa and Khalti change their endpoints, whether to keep developing it at all, and what to charge for continued access. Businesses that have built their payment and booking infrastructure on a plugin sold by a developer who later abandons it face either staying on an insecure, unmaintained codebase or rebuilding from scratch. A custom plugin is owned entirely by the client. There is no licence renewal, no subscription, no risk of the plugin being abandoned by a remote developer. The client holds the code, can give it to any WordPress developer for future modification, and has a complete operational document explaining how it works. WebApp Nepal recommends a maintenance retainer for ongoing compatibility updates, but the plugin continues to function on the client's site regardless of whether that retainer is active.




#### Plugin Development for Every Nepal Industry




##### Tourism and Hospitality



Hotels, resorts, trekking agencies, rafting and adventure operators, and luxury lodges across Nepal need booking and inquiry management plugins built for Nepal's hospitality sales process. Guests research, inquire through WhatsApp or a contact form, receive a quote, and confirm with a deposit payment. This inquiry-to-booking flow is a sales workflow that generic contact form plugins do not handle as a structured pipeline. Custom plugins for Nepal's hospitality sector capture the inquiry, route it to the correct staff member by property or service type, track follow-up status through the pipeline stages, generate quote documents with the property's branding, and process deposit payments through eSewa or Khalti when the guest confirms. For international guests, the inquiry captures travel dates, nationality, and special requirements. For the property's operations team, the admin interface shows the pipeline at a glance with alerts for inquiries that have not received a response within a defined period.




##### Education



Schools, colleges, and universities across Nepal have WordPress-based websites that serve students, parents, prospective applicants, and staff simultaneously. The plugin requirements for an educational institution site are significantly more complex than a business website: online admission form submission with document upload, result publication with NEB-format grade display and student authentication for access, fee payment through eSewa or Khalti with automated receipt generation, teacher and staff directory with designation and department taxonomy, academic notice publication with category filtering by audience (all students, specific class, parents only), library book availability check, and BS-calendar academic event scheduling. WebApp Nepal builds educational institution WordPress plugins modularly - a school can deploy the fee payment module first, add the admission management module for the next intake cycle, and expand to the full student portal over successive project phases.




##### Financial Services and Cooperatives



Cooperative societies, microfinance institutions, and rural development banks across Nepal operate WordPress sites that are primarily informational. The next layer of value is member-facing functionality: a portal where members log in to view their savings passbook, check their loan outstanding, download their share certificate, receive dividend announcements, and register for the AGM. This member portal functionality requires a plugin that authenticates against the cooperative's member database, retrieves and displays financial records in the correct NRB format, and generates downloadable documents in PDF with the cooperative's letterhead. WebApp Nepal builds these cooperative member portal plugins for societies using FECOFUN-registered cooperative software in the backend and WordPress as the public-facing platform. The plugin connects to the cooperative's database via an internal API, never exposing the database credentials to the public web layer.




##### Healthcare



Hospitals, diagnostic centres, and specialist clinics using WordPress need patient-facing functionality beyond a contact form: online appointment booking with doctor availability calendar integration, OPD queue number display for waiting patients, lab result notification by SMS when results are ready, health package inquiry with pricing in NPR, and pharmacy product catalogue. WebApp Nepal builds healthcare WordPress plugins for Nepal's clinic and hospital sector with these specific requirements - appointment booking integrated against the clinic's OPD scheduling system, patient authentication for result access, and Sparrow SMS integration for appointment reminders and result notifications. Nepal's medical practice setting requires specific patient data handling: all personal health information is stored only within the hospital's own server infrastructure, with no third-party analytics or tracking scripts loading on patient-facing pages of the portal.




##### Manufacturing and Trading



Trading companies and manufacturers in Nepal's industrial corridor - Birgunj, Bhairahawa, Hetauda, Simara - with WordPress websites need dealer and distributor portal plugins: login-protected pages where authorised dealers access current product pricing, stock availability, promotional materials, and order status tracking. For exporters targeting international buyers, a product inquiry plugin with HSN code display, MOQ specification, and Nepali origin certification detail captures the information international buyers need before placing a sample order. For businesses managing multiple warehouses across the Terai region, inventory display by location lets dealers and internal staff see stock levels in real time from the WordPress dashboard. WebApp Nepal builds these B2B functional layers for Nepal trading and manufacturing websites as custom plugins that operate entirely within the client's WordPress installation without dependency on external SaaS platforms.




#### Custom Plugin Pricing in Nepal



Custom plugin pricing reflects the complexity of the functionality being built. A straightforward contact or inquiry form plugin with admin inbox, email notification, and basic Nepal-specific fields (district, phone format validation) ranges from NPR 15,000 to NPR 35,000. A payment plugin integrating a single gateway - eSewa or Khalti - with full HMAC signature validation, webhook handling, and admin reporting ranges from NPR 40,000 to NPR 80,000. A dual-gateway plugin covering both eSewa and Khalti with WooCommerce integration ranges from NPR 60,000 to NPR 1,20,000. A school management plugin covering admissions, results, fee payment, and notice management ranges from NPR 80,000 to NPR 2,00,000 depending on the breadth of modules included. A cooperative member portal plugin with savings passbook, loan statement, and document generation ranges from NPR 1,00,000 to NPR 2,50,000. A full HR and payroll plugin with EPF, CIT, income tax calculation, and slip generation ranges from NPR 1,20,000 to NPR 3,00,000. All projects include full source code delivery, operations documentation, testing on the client's WordPress environment, and thirty days of post-deployment bug support. Maintenance retainers for ongoing compatibility and minor updates are available from NPR 5,000 per month.




#### Starting a Custom Plugin Project



The first step is a requirements conversation - a structured discussion of what the plugin needs to do, what systems it needs to connect with, who the users are (customers on the front end, staff in the admin), and what the project timeline is. WebApp Nepal prepares a functional specification document from that conversation, covering every feature, data flow, and integration point in concrete detail. The specification is reviewed and agreed before any development begins - because changes to requirements after development starts cost significantly more time and money than changes to a document before development starts. From agreed specification to delivered plugin, timelines depend on scope: a simple inquiry management plugin in two to three weeks, a payment integration plugin in three to five weeks, a full school management or cooperative portal plugin in six to twelve weeks. The conversation starts with a description of what your WordPress site needs to do that it currently cannot.




#### Frequently Asked Questions: Custom WordPress Plugin Development in Nepal




##### What is a custom WordPress plugin?



A custom WordPress plugin is a software module built specifically for one business's website, designed to add functionality that no publicly available plugin provides correctly - particularly for Nepal-specific requirements like eSewa and Khalti payment integration, Bikram Sambat date handling, Nepali language support, NRB-format financial reporting, Nepal tax calculations, and Nepal SMS gateway integration. Unlike downloaded plugins from WordPress.org or premium marketplaces, a custom plugin is built to the exact specifications of the business that commissions it, is owned outright by that business, and contains only the code needed for that specific functionality without the bloat of unused features designed for other use cases.




##### Why can't I just use a plugin from WordPress.org for eSewa or Khalti payment?



The eSewa and Khalti plugins available on WordPress.org and in premium plugin marketplaces are predominantly maintained by individual developers and frequently lag behind eSewa's and Khalti's API changes. The critical issue with many available integrations is incomplete payment verification: plugins that redirect to eSewa's payment page and mark orders complete on redirect return without running the server-to-server payment verification API call are vulnerable to spoofed payment notifications. A technical user can craft a forged return URL that marks an order as paid without money moving. WebApp Nepal's custom payment plugins run the verification API call on the server after every payment redirect before any order status is updated - the step that makes the integration secure and reliable.




##### How long does it take to build a custom WordPress plugin in Nepal?



A simple custom plugin - a contact form with Nepal-specific fields and admin inbox - takes two to three weeks from agreed specification to delivered, tested plugin. A payment integration plugin for eSewa or Khalti with full sandbox testing and production validation takes three to five weeks. A WooCommerce Nepal extension with Nepal shipping zones, NPR currency, and dual eSewa/Khalti checkout takes four to six weeks. A school management plugin covering admissions, results, and fee payment takes eight to fourteen weeks depending on module count. A cooperative member portal plugin takes ten to sixteen weeks. Timelines assume that the client is available for review and sign-off at key milestones and that access to third-party API credentials is provided promptly.




##### Do I own the plugin code after WebApp Nepal builds it?



Yes, completely. WebApp Nepal delivers the full plugin source code to the client on project completion. There is no licence fee, no subscription, no ongoing payment required to keep the plugin running, and no clause that returns ownership to WebApp Nepal. The client can install the plugin on any number of their own websites, give the code to another WordPress developer for future modifications, and operate the plugin indefinitely without any dependency on WebApp Nepal's continued involvement. The only exception is that the client cannot resell or redistribute the plugin as a commercial product without a separate agreement, since it was commissioned as a bespoke work for their use.




##### Can you build a plugin that works with existing plugins on my WordPress site?



Yes. Custom plugin development at WebApp Nepal begins with a review of the client's existing plugin and theme set to understand the environment in which the new plugin will operate. Conflicts between plugins are typically caused by functions or class names that clash, JavaScript libraries that conflict, or CSS specificity issues. Custom plugins are namespaced to avoid function and class name collisions with other plugins. JavaScript and CSS assets are enqueued conditionally and checked against the libraries already loaded by the active theme and plugin set. Testing includes running the full site with all existing plugins active alongside the new custom plugin to identify and resolve any interaction issues before the plugin is deployed to production.




##### What Nepal-specific features does WebApp Nepal include in custom plugins?



Nepal-specific features that WebApp Nepal builds into custom plugins include: eSewa HMAC-SHA256 payment integration with server-side verification, Khalti OAuth2 payment integration with webhook handling, Sparrow SMS and Aakash SMS API integration for OTP and notification delivery, Bikram Sambat calendar handling with correct BS-to-AD conversion, Nepal's 77 districts and 7 provinces as structured taxonomy, Nepal phone number format validation (+977 prefix, 10-digit mobile, NTC and Ncell number range checking), NPR currency display and IRD VAT (13%) calculation, NEB grade scale calculation for school result publishing, EPF and CIT payroll deduction calculation, Nepal income tax slab calculation under the current year's Finance Act, and Devanagari text input and display optimisation for Nepali content.




##### Can a custom plugin connect to Nepal government systems or external APIs?



Yes. Custom WordPress plugins can connect to any external API that provides an accessible endpoint. WebApp Nepal has built plugins that connect to Nepal government-adjacent systems including: eSewa's payment API, Khalti's payment API, Sparrow SMS gateway, Aakash SMS gateway, Prabhu SMS gateway, Google Maps with Nepali locality data, and Nepal Telecom's VOIP billing APIs. For systems that do not provide a public API - such as some cooperative accounting software or hospital HMS platforms - WebApp Nepal builds a secure internal API layer within the hospital's or cooperative's own server infrastructure that the WordPress plugin accesses through authenticated internal HTTP calls, keeping sensitive data within the client's own environment at all times.




##### Does WebApp Nepal build multilingual plugins that support Nepali and English?



Yes. Bilingual plugin development is a standard capability. Admin interfaces for plugins are built with WordPress's internationalization functions - __(), _e(), esc_html__() - which means the plugin's text strings can be translated using WordPress's standard .po and .mo translation file system. For plugins where bilingual front-end output is required - a plugin that displays content in Nepali to Nepali users and English to international users - language detection and output switching are built into the plugin's rendering logic. Devanagari text in admin notices, email notifications, PDF documents, and SMS messages is handled with correct UTF-8 encoding throughout the plugin's data flow.




##### Is it possible to add a plugin to an existing WordPress website that someone else built?



Yes, in most cases. Custom plugins are installed on WordPress sites as standard plugin ZIP files - they do not require the site to have been built by WebApp Nepal. Before taking on a custom plugin project for a WordPress site built by another developer, WebApp Nepal reviews the site's PHP version, WordPress version, active theme, and existing plugin set to assess compatibility. Sites running outdated PHP versions (below 7.4), very old WordPress versions, or heavily customised themes with non-standard structures may require remediation before a new custom plugin can be deployed cleanly. This assessment happens at the specification stage, and any required prerequisite work is scoped and priced separately from the plugin development itself.




##### How does WebApp Nepal handle plugin security?



Plugin security at WebApp Nepal is implemented through WordPress's established security mechanisms applied consistently throughout the plugin code. All database queries use $wpdb->prepare() with parameterised values - never string concatenation that creates SQL injection exposure. All form submissions validate a WordPress nonce - a one-time cryptographic token that prevents cross-site request forgery. All output is escaped before being rendered to HTML using esc_html(), esc_attr(), esc_url(), or wp_kses() as appropriate to the output context - preventing cross-site scripting. All file upload handling sanitises filenames and validates MIME types against an allowlist. All capabilities checks verify that the current user has permission to perform the requested action before the action is executed. Admin-only functionality is protected by current_user_can() checks. These security practices are applied to every line of every plugin WebApp Nepal delivers - they are not optional or conditional on project budget.




##### Can you build a plugin that generates PDF documents - invoices, receipts, certificates?



Yes. PDF generation is a common requirement in Nepal business WordPress plugins - fee receipts for schools and cooperatives, VAT invoices for e-commerce, share certificates for cooperatives, salary slips for HR systems, loan repayment schedules for microfinance institutions. WebApp Nepal builds PDF generation into custom plugins using TCPDF or FPDF libraries integrated within the WordPress plugin structure. PDFs are generated server-side and delivered as downloads or saved to the server for later retrieval. Devanagari text in PDFs is handled with Unicode font embedding - a requirement that many PDF libraries handle incorrectly, producing garbled output for Nepali text. WebApp Nepal validates Devanagari PDF rendering across the range of PDF viewers that Nepal users access documents through - Chrome's built-in PDF viewer, Adobe Reader, and mobile PDF applications on Android.




##### What is the difference between a WordPress plugin and a WordPress theme?



A WordPress theme controls how the website looks - the visual design, layout, typography, colour system, and the template structure that wraps page content. A WordPress plugin adds functional capability - what the website does beyond displaying content. Payment processing, form submission and storage, booking management, member authentication, email notification, PDF generation, API integration - these are plugin functions. Custom post types, custom fields, shortcodes, widget areas, and Gutenberg blocks can be either theme or plugin components depending on whether the functionality is tied to the visual presentation (theme) or is independent of it (plugin). WebApp Nepal separates functionality from presentation correctly: custom post types and shortcodes that should persist when a theme changes are built as plugins, not baked into the theme's functions.php where they would be lost in a theme switch.




##### Can a custom plugin send SMS notifications to Nepal phone numbers?



Yes. SMS notification integration with Nepal SMS gateways - Sparrow SMS, Aakash SMS, Prabhu SMS, and Thamel.com - is a standard component of custom plugin builds that require notification delivery. Common use cases include: school fee payment confirmation SMS to parents, cooperative loan instalment due date reminder SMS to members, hotel booking inquiry acknowledgement SMS to guests, OTP delivery for two-factor authentication on member portals, and appointment reminder SMS for clinics. SMS gateway integration requires an active account with the SMS provider and API credentials (API key, sender ID) which the client obtains and provides. The SMS integration is built with retry logic for failed delivery attempts and delivery status logging in the plugin's admin interface so operations staff can verify that critical notifications reached their recipients.




##### Does WebApp Nepal build WooCommerce plugins specifically for Nepal?



Yes. WooCommerce extension plugins for Nepal are one of the most frequently requested plugin types. The gaps in WooCommerce's out-of-box Nepal support are significant: no eSewa or Khalti checkout integration in the core, no Nepal province and district shipping zones with Nepali names, no NPR currency symbol (NRS or ??), no IRD-compliant VAT invoice format, no Nepal address fields for tole and ward number, and no COD with advance deposit option used by many Kathmandu Valley delivery operations. WebApp Nepal builds WooCommerce Nepal extension plugins that address these gaps as a modular package: the client can deploy the full extension suite or select the specific modules relevant to their operation - payment only, shipping zones only, or the complete Nepal commerce configuration.




##### How does a custom plugin handle WordPress updates?



WordPress updates its core version approximately eight to ten times per year, with three to four major releases and the remainder minor security and maintenance releases. A well-built custom plugin that follows WordPress coding standards is rarely affected by minor WordPress updates. Major WordPress version updates sometimes change internal APIs or deprecate functions that plugins depend on. WebApp Nepal writes custom plugins against WordPress's stable public APIs rather than internal functions marked as private or deprecated, which minimises the compatibility impact of WordPress version changes. Clients on maintenance retainers receive compatibility verification and any required updates after each major WordPress release. Clients not on retainer can request compatibility reviews on a per-incident basis at the applicable hourly rate.




##### Can you build a plugin that handles Nepal's BS (Bikram Sambat) calendar?



Yes. Bikram Sambat calendar handling is a recurring requirement in Nepal WordPress plugins because BS dates appear in school academic year references, cooperative financial period statements, court and government document dates, and any context where the formally correct Nepal date format is required. WebApp Nepal implements BS calendar functionality using a validated conversion library that correctly handles the irregular month length pattern in the BS calendar - a pattern that varies by year and cannot be calculated by a simple formula, requiring lookup against a stored calendar table verified against NRB's published official BS calendar. The plugin implementation covers: BS-to-AD conversion, AD-to-BS conversion, BS date input in admin and front-end forms, BS date display in output, and BS date arithmetic for calculating periods, due dates, and deadlines.




##### What happens if WebApp Nepal is unavailable in the future - will my plugin still work?



Yes. The plugin runs on your WordPress server entirely independently of WebApp Nepal's operation. There is no call-home function, no licence validation against a remote server, no subscription requirement, and no dependency on any service that WebApp Nepal operates. If WebApp Nepal ceased to exist tomorrow, every plugin delivered to every client would continue to function exactly as it did the day before. The client owns the code, the code runs on the client's server, and the client can give that code to any competent WordPress developer for future modifications. The only scenarios in which the plugin would require attention are changes in the third-party APIs it integrates with (eSewa or Khalti changing their API endpoint or signature method), changes in WordPress core that deprecate an API function the plugin uses, or the client's requirements changing. All of these are scenarios that any WordPress developer can address given the source code and the operations document delivered with every WebApp Nepal plugin project.




##### Does WebApp Nepal build Gutenberg blocks as custom plugins?



Yes. Custom Gutenberg block development is part of WebApp Nepal's plugin development work. Gutenberg blocks are the components that editors use in the WordPress block editor to compose pages. A custom Gutenberg block can be a Nepal district selector that editors use to tag content by location, a staff profile block with contact and designation fields, a trek itinerary day-by-day accordion block, a property listing card block for real estate sites, or a price table block with NPR formatting and festival offer badges. Custom blocks are built as WordPress plugins using React and the @wordpress/blocks package, registered in WordPress's block registry, and available in the editor's block inserter. Block attributes are stored in the page's post_content as structured data, making them reliable across WordPress version updates and theme changes.




##### Can a custom plugin restrict access to certain pages or content by user role?



Yes. Content access control by user role is a common custom plugin requirement for Nepal membership and portal sites: cooperative member portals that show financial data only to authenticated members, school parent portals that show a specific student's records only to that student's registered guardian, dealer portals that show wholesale pricing only to approved dealers, and INGO staff intranets that restrict field documentation to verified employees. WebApp Nepal builds content access control into custom plugins using WordPress's native user role and capability system - extending it with custom roles (cooperative_member, verified_dealer, school_guardian) and custom capabilities that match the client's access control requirements. Authentication can be against WordPress's own user database or against an external member database via an internal API, depending on whether the member database is managed in WordPress or in a separate backend system.




##### How does WebApp Nepal test payment plugins before going live?



Payment plugin testing follows a two-stage process. Stage one is sandbox testing: both eSewa and Khalti provide sandbox API environments with test merchant credentials and test wallet accounts that allow the complete payment flow - from checkout initiation through payment redirect through webhook receipt through order status update - to be executed without real money moving. WebApp Nepal tests every payment scenario in sandbox: successful payment, failed payment, payment initiated but user closes browser before returning, webhook arriving out of sequence, duplicate webhook delivery, and payment amount mismatch between the order total and the webhook-reported amount. Each scenario is verified to produce the correct outcome - order marked paid only when payment is verified, pending orders for incomplete flows, error logging for unexpected scenarios. Stage two is production validation: a live test transaction using a real eSewa or Khalti account for a minimal amount (NPR 10 or NPR 1) on the client's production server, verifying that the production credentials, the production webhook URL, and the production server's SSL configuration all work correctly before the plugin is made available to real customers.




##### What support is available after a custom plugin is delivered?



Every custom plugin delivery includes thirty days of bug support from the deployment date: if the plugin does not function as specified in the requirements document during that period, the issue is investigated and resolved at no additional charge. After the thirty-day period, support is available under two arrangements: a monthly maintenance retainer (from NPR 5,000 per month) that covers WordPress core compatibility verification after major releases, third-party API compatibility monitoring and updates when eSewa or Khalti change their APIs, security patch responses, and minor adjustments within agreed scope; or per-incident support billed at the applicable hourly rate for clients who prefer not to commit to a monthly retainer. New features or significant functionality changes beyond the original specification are scoped and quoted as separate development projects.




##### Can WebApp Nepal migrate functionality from an existing plugin to a custom-built replacement?



Yes. Plugin migration - taking functionality from an off-the-shelf plugin and replacing it with a custom-built equivalent that works correctly in Nepal's environment - is a common project type. The process begins with a full audit of the existing plugin's functionality: what it does, how its data is stored in the WordPress database, what settings the client has configured, and what has historically not worked or has required workarounds. The custom replacement is designed to cover all the working functionality, fix the functionality that does not work, and import the existing plugin's data so that historical records (past inquiries, past payment records, past bookings) are preserved in the new system. The migration is tested in a staging environment before the production switch, with a rollback plan in place if the staging tests reveal issues. Production migration is executed during a low-traffic window with a complete site backup immediately before.




##### Does WebApp Nepal build plugins for WordPress multisite installations?



Yes, with the specific consideration that multisite introduces additional complexity in plugin design. A plugin built for a single WordPress site manages its data within that site's database tables. A plugin designed for multisite must decide whether its data is network-wide (shared across all sites in the network) or site-specific (each site in the network maintains its own copy). For cooperative networks with a central office site and branch sites, or for school chains with a head office site and individual school sites, the plugin architecture must reflect the data ownership structure of the organisation. WebApp Nepal designs multisite plugin architecture in the requirements session - establishing which data is shared at the network level and which is managed per site - before development begins, because changing the data architecture after the plugin is built requires rebuilding the storage and retrieval logic from scratch.




##### How do I know if I need a custom plugin or a standard off-the-shelf plugin?



A standard off-the-shelf plugin is appropriate when the functionality you need is generic - a basic contact form, a standard image gallery, a simple appointment booking for a service where no Nepal-specific payment or calendar integration is required, or an SEO meta tag management tool. An off-the-shelf plugin has the advantage of being immediately available, lower upfront cost, and community support from a wide user base. A custom plugin is appropriate when the functionality requires Nepal-specific payment integration (eSewa, Khalti), Nepal regulatory compliance (NRB reporting, IRD invoicing, EPF/CIT payroll), Bikram Sambat date handling, Nepal SMS gateway integration, Nepali language content in generated documents or notifications, integration with Nepal-specific backend systems (cooperative accounting software, hospital HMS, school ERP), or a specific workflow that generic plugins approximate but do not deliver correctly. If you have tried an off-the-shelf plugin and found that it does not work for your Nepal business requirement, the answer is almost certainly a custom plugin. WebApp Nepal offers a free requirement assessment conversation to help businesses determine which approach is right for their specific situation.

## Frequently asked questions

### What is custom WordPress plugin development in Nepal?

Custom WordPress plugin development in Nepal means building a bespoke software module for a WordPress website that addresses Nepal-specific functional requirements — eSewa and Khalti payment integration with HMAC signature verification, Bikram Sambat calendar handling, Nepali language and Devanagari text support, NRB-format financial reporting, IRD VAT invoice generation, EPF and CIT payroll deduction, Nepal SMS gateway (Sparrow, Aakash) integration, and Nepal's 77 districts and 7 provinces as data structures. Unlike plugins downloaded from WordPress.org, a custom plugin is built specifically for one business, owned outright by that business, and contains no unnecessary code for features the business does not use.

### How much does custom WordPress plugin development cost in Nepal?

Custom WordPress plugin development pricing in Nepal reflects the complexity of the functionality. A basic contact or inquiry form plugin with Nepal-specific fields and admin inbox costs NPR 15,000–35,000. An eSewa or Khalti payment integration plugin with full webhook verification costs NPR 40,000–80,000. A dual-gateway WooCommerce extension (eSewa + Khalti) with Nepal shipping zones costs NPR 60,000–1,20,000. A school management plugin covering admissions, results, and fee payment costs NPR 80,000–2,00,000. A cooperative member portal plugin costs NPR 1,00,000–2,50,000. An HR and payroll plugin with EPF, CIT, and Nepal income tax calculation costs NPR 1,20,000–3,00,000. All projects include full source code delivery and 30 days of post-deployment support.

### Can WebApp Nepal build an eSewa payment plugin for WordPress?

Yes. WebApp Nepal builds custom eSewa payment plugins for WordPress and WooCommerce with production-grade implementation: HMAC-SHA256 merchant credential signing, redirect flow handling, server-to-server payment verification API call after redirect return (the critical step many plugins skip), and conditional order status update only after verified payment confirmation. The plugin is tested end-to-end in eSewa's sandbox environment and validated with a live production transaction before deployment. Both standard eSewa merchant gateway and eSewa for Business flows are supported.

### Does WebApp Nepal build Khalti payment plugins for WordPress?

Yes. WebApp Nepal builds Khalti payment plugins for WordPress and WooCommerce using Khalti's OAuth2-based payment API with full webhook handling and server-side payment verification. The implementation covers the complete payment lifecycle: checkout initiation, redirect to Khalti's payment page, return handling, webhook capture, payment verification API call against Khalti's server, and order status update. The integration is tested in Khalti's sandbox environment and validated with a live transaction. Khalti integration is frequently bundled with eSewa integration as a dual-gateway WooCommerce extension for Nepal e-commerce sites.

### Can you build a WordPress plugin that handles Bikram Sambat (BS) dates?

Yes. Bikram Sambat date handling is a standard WebApp Nepal plugin capability. The implementation uses a validated BS calendar lookup table verified against the NRB's published official calendar — not an approximation algorithm, which produces errors across the BS calendar's irregular month length pattern. The plugin provides BS-to-AD conversion, AD-to-BS conversion, BS date input fields in admin and front-end forms, BS date display in generated output, and BS date arithmetic for calculating deadlines, instalment due dates, and period durations. Used in school academic scheduling plugins, cooperative financial period plugins, and any context where official Nepal dates are required.

### How does a custom plugin differ from plugins on WordPress.org?

A plugin on WordPress.org is built for a global market — for Stripe and PayPal payment, for US tax structures, for English SMS gateways, for postal code address formats. Nepal businesses trying to use these plugins for Nepal-specific requirements find they either do not integrate with eSewa or Khalti, do not calculate EPF or Nepal income tax correctly, do not handle Bikram Sambat dates, or do not connect to Nepal's SMS gateways. A custom plugin built by WebApp Nepal is designed from the ground up for the specific Nepal business that commissions it, implementing Nepal's actual technical and regulatory requirements rather than adapting a generic global solution. The client owns the code outright with no licence fees or subscriptions.

### What industries does WebApp Nepal build custom plugins for?

WebApp Nepal builds custom WordPress plugins for tourism and hospitality (hotel booking inquiry management, trekking agency inquiry pipelines, WhatsApp follow-up automation), education (school admissions, result publication, fee payment, BS calendar scheduling), financial services and cooperatives (member portals, savings passbook, loan statements, NRB reporting), healthcare (appointment booking, OTP-gated lab results, pharmacy catalogue), manufacturing and trading (dealer portals, B2B pricing access, inventory display), real estate (Nepal measurement units, locality taxonomy, property listings), and HR and payroll (EPF, CIT, Nepal income tax, salary slip generation).

### Can WebApp Nepal build a Nepal cooperative member portal plugin?

Yes. WebApp Nepal builds cooperative member portal WordPress plugins for SACCOS and savings and credit cooperatives across Nepal. The plugin authenticates members against the cooperative's member database, displays savings account passbook with BS-date transactions, shows loan outstanding and instalment schedule, delivers dividend announcements, generates downloadable share certificates in PDF, and publishes AGM and meeting notices to members. NRB-format financial data display is built into the reporting templates. The plugin connects to the cooperative's backend accounting system via an authenticated internal API, keeping member financial data within the cooperative's own server infrastructure.

### Does WebApp Nepal build WooCommerce plugins specifically for Nepal e-commerce?

Yes. WebApp Nepal builds WooCommerce Nepal extension plugins covering the gaps in WooCommerce's standard Nepal support: eSewa and Khalti checkout integration with HMAC and OAuth2 verification, Nepal province and district shipping zones with Nepali names, NPR currency display with NRS symbol, IRD VAT (13%) invoice generation in PDF format with taxpayer number fields, Nepal address fields (tole, ward number, municipality, district, province), COD with advance payment option for Kathmandu Valley delivery networks, and festival-season promotional pricing capability for Dashain and Tihar sales periods.

### Is it possible to build a plugin that sends SMS to Nepal mobile numbers?

Yes. WebApp Nepal integrates Nepal SMS gateways — Sparrow SMS, Aakash SMS, and Prabhu SMS — into custom WordPress plugins for notification delivery. Use cases include school fee payment confirmation to parents, cooperative loan instalment reminders to members, OTP delivery for member portal authentication, appointment reminders for clinics, and booking acknowledgement for hotels and trekking agencies. The integration includes delivery status logging in the plugin's admin interface, retry logic for failed SMS deliveries, and Devanagari text support for Nepali-language notification messages.

### How does WebApp Nepal ensure plugin security?

WebApp Nepal applies WordPress's security standards consistently throughout every plugin's code: $wpdb->prepare() with parameterised queries for all database interactions (preventing SQL injection), WordPress nonce verification on all form submissions (preventing CSRF), output escaping with esc_html(), esc_attr(), esc_url(), and wp_kses() before rendering any user-supplied data to HTML (preventing XSS), current_user_can() capability checks before every admin action, sanitised file upload handling with MIME type allowlisting, and HTTPS enforcement for all third-party API calls. These are applied uniformly — not selectively based on project budget or timeline.

### Can WebApp Nepal build a school management plugin for Nepal schools?

Yes. WebApp Nepal builds school management WordPress plugins for Nepal educational institutions covering: student admission form with document upload and BS-calendar academic year assignment, examination result publication with NEB-format grade display (for SEE and SLC grading scales), online fee payment with eSewa and Khalti integration and automated receipt generation, teacher and staff directory with designation and department taxonomy, academic notice publication with audience-specific access (all students, specific class, parents), and library book availability display. Plugins are built modularly so schools can deploy the fee payment module first and add additional modules in subsequent phases.

### Do custom plugins built by WebApp Nepal work with WordPress page builders like Elementor or Divi?

Yes, in most cases. Custom plugins built by WebApp Nepal are designed to coexist with Elementor, Divi, WPBakery, and other page builders without conflict. Shortcodes generated by custom plugins work within page builder text and shortcode elements. Custom Gutenberg blocks work in WordPress's native block editor. The main consideration is performance: sites using heavy page builders already carry significant CSS and JavaScript overhead, and adding custom plugin assets can push page weight further. WebApp Nepal's custom plugins load assets conditionally — only on pages where the plugin is active — which minimises the additional performance impact on page-builder-based sites.

### What documentation does WebApp Nepal deliver with a custom plugin?

Every custom plugin delivery from WebApp Nepal includes: an operations manual covering installation, activation, settings configuration, admin interface usage, shortcode reference with all accepted parameters and example output, and troubleshooting for common issues; API credential setup guides for third-party integrations (eSewa, Khalti, Sparrow SMS) with step-by-step instructions for obtaining and entering credentials; and clean, commented source code with an architectural explanation of how the plugin's components relate to each other. The documentation is written so that the plugin can be operated by non-technical admin staff and maintained by any competent WordPress developer — not only by WebApp Nepal.

### Can a custom WordPress plugin generate PDF documents in Nepali language?

Yes. PDF generation with Devanagari text is a standard WebApp Nepal plugin capability, implemented using TCPDF or FPDF with embedded Unicode fonts. Documents generated include fee receipts with Nepali school letterhead, IRD VAT-compliant sales invoices with Nepali business registration details, cooperative member passbooks with BS-format transaction dates, share certificates, loan repayment schedules, and salary slips with EPF and CIT deductions labelled in Nepali. Devanagari rendering in PDF is validated across Chrome's built-in PDF viewer, Adobe Acrobat Reader, and Android mobile PDF applications before delivery.

### Can WebApp Nepal build a custom Gutenberg block plugin?

Yes. Custom Gutenberg block development is part of WebApp Nepal's plugin work. Examples built for Nepal clients include: Nepal district selector blocks for content tagging, trek itinerary accordion blocks with day-by-day format and altitude profile fields, hotel room showcase blocks with image gallery and pricing in NPR, staff profile blocks with designation and department fields, property listing card blocks with ropani/aana/bigha/kattha measurement unit inputs, cooperative notice blocks with member-audience targeting, and service pricing table blocks with NPR formatting. Custom blocks are built using React and the @wordpress/blocks package, stored in post content as structured data, and designed to remain functional across WordPress version updates.

### Does WebApp Nepal build HR and payroll plugins that handle Nepal tax rules?

Yes. WebApp Nepal builds HR and payroll WordPress plugins for Nepal businesses with all Nepal-specific deduction calculations: Employee Provident Fund (EPF) at 10% employee and 10% employer contribution on basic salary, Citizens Investment Trust (CIT) contribution, Nepal income tax calculated on the current year's Finance Act tax slabs with applicable exemption thresholds for individuals and couples, gratuity calculation under Nepal's Labour Act after five years of continuous service, festival allowance provisions, and advance deductions against earned salary. Monthly salary slips are generated in PDF with each deduction itemised. Annual tax statements are generated for employee submission to the IRD. Leave management includes Nepal public holidays in both BS and AD calendar formats.

### Can WebApp Nepal integrate a custom plugin with an existing Nepal accounting or ERP system?

Yes, where the accounting or ERP system provides an accessible API or database endpoint. WebApp Nepal has integrated WordPress plugins with: cooperative accounting software via internal REST API, hospital HMS platforms via internal database query layer, school ERP systems via read-only API access to student and fee records, and inventory management systems for real-time stock display in product listings. For systems that do not expose a public API, WebApp Nepal builds a secure internal API layer within the client's own server infrastructure — accessible only by the WordPress plugin via authenticated internal HTTP calls — so that the integration never exposes sensitive financial or personal data to the public internet.

### How does WebApp Nepal handle plugin performance so it does not slow down the website?

Custom plugins built by WebApp Nepal load CSS and JavaScript assets only on the pages and in the contexts where the plugin is active — using WordPress's wp_enqueue_scripts with is_page() and has_shortcode() conditional checks rather than loading assets globally. Database queries are optimised with indexed lookups and result caching using WordPress's transient API for data that does not change on every page load. Admin-facing queries use pagination rather than loading complete result sets for large datasets. The combination of conditional asset loading, query optimisation, and transient caching means that a custom plugin from WebApp Nepal adds minimal performance overhead compared to the broad, unconditional asset loading that characterises most off-the-shelf plugins.

### Is a custom plugin the right choice for a small Nepal business website?

It depends on the specific requirement. For a small business that needs only a basic English-language contact form with no Nepal payment integration, a well-maintained standard plugin from WordPress.org is sufficient. A custom plugin becomes the right choice when the business needs eSewa or Khalti payment integration with correct webhook verification, Nepali language in generated notifications or documents, Bikram Sambat date handling, Nepal district and province data structures, or a specific workflow that generic plugins do not handle. WebApp Nepal offers a free requirement assessment conversation to help any Nepal business determine whether their specific need is best served by a custom plugin or a standard solution.

### What Nepal real estate plugin features can WebApp Nepal build?

WebApp Nepal builds custom real estate listing plugins for Nepal property websites with: property listing custom post types with Nepal-format land area inputs (ropani-aana-paisa-dam for hill districts, bigha-kattha-dhur for Terai), Nepal province, district, and municipality taxonomy with Kathmandu Valley locality sub-taxonomy (Lazimpat, Khumaltar, Bhaisepati, Budhanilkantha, etc.), NPR price display with price per ropani and price per square feet fields, filterable property search by location, property type, price range, and land measurement unit, Google Maps integration with Nepal-specific location data, WhatsApp direct inquiry with pre-filled property reference in message, and property developer showcase with site plan and floor plan PDF download.

### Can WebApp Nepal build a plugin for hotel or trekking booking management?

Yes. WebApp Nepal builds custom booking inquiry management plugins for Nepal hotels and trekking agencies. The plugin captures structured inquiry data (travel dates, party size, room or trek preferences, dietary requirements, nationality), routes the inquiry to the correct staff member by property or service type, sends an automated acknowledgement email and WhatsApp notification to the guest, tracks follow-up status through a pipeline (new, acknowledged, quoted, confirmed, rejected) visible in the admin dashboard, generates quote documents with the property or agency's branding, and processes deposit payments through eSewa or Khalti on booking confirmation. Bulk inquiry export to CSV is included for agencies managing high inquiry volumes.

### Does WebApp Nepal build plugins that restrict access to content by user role?

Yes. Content access control plugins are built for cooperative member portals, school parent portals, dealer portals, and staff intranets. The plugin uses WordPress's native user role and capability system extended with custom roles (cooperative_member, verified_dealer, school_guardian) and custom capabilities matching the client's access requirements. Authentication is against WordPress's own user database or against an external member database via an internal API, depending on whether the membership is managed in WordPress or in a separate backend system. Protected content can be entire pages, sections of pages, custom post types, or generated documents — with unauthorised access redirecting to a login page or showing a permission-denied message.

### Can a custom plugin handle online admission forms for Nepal schools and colleges?

Yes. Online admission form plugins are a standard WebApp Nepal education plugin type. The admission form captures student personal details, parent information, previous academic record, and required document uploads (SLC/SEE certificate, citizenship, passport photo). Submitted applications are stored in the WordPress database with application status tracking (received, under review, accepted, waitlisted, rejected). Email notifications go to the applicant on submission and on status changes. The admin interface shows all applications with filter by status, search by name or registration number, and bulk export to CSV or Excel. BS-calendar academic year assignment is built into the application record. Application fee payment through eSewa or Khalti is included where required.

### How do I start a custom WordPress plugin project with WebApp Nepal?

Contact WebApp Nepal with a description of what your WordPress site needs to do that it currently cannot — the specific functionality gap, the Nepal-specific requirement (eSewa payment, cooperative member portal, school result publication, HR payroll calculation), and any existing systems the plugin needs to connect with. WebApp Nepal will schedule a free requirements conversation covering the full functional scope, user types, admin interface needs, third-party integrations, data storage requirements, and timeline. From that conversation, a written specification document is produced covering every feature and data flow. After the client reviews and approves the specification, development begins. The gap between first contact and specification approval is typically one week. Development timeline runs from the specification approval date.
