WOOCOMMERCE DEVELOPMENT

WooCommerce is Nepal's most common e-commerce setup — and eSewa integration, hosting performance, and WPML configuration are where most stores break

Ignited Nepal builds, fixes, and extends WooCommerce stores for Nepali domestic brands and export businesses. We handle eSewa ePay API integration, object caching configuration for Nepali hosting environments, WPML multilingual setup for Nepali/English stores, and WooCommerce database optimisation for stores with growing product catalogues.

Request a WooCommerce Development Brief → View the evidence →
This is for you if

WooCommerce development in Nepal is relevant to you if any of the following describes your situation.

You are a Nepali retail or export brand that built on WordPress because your developer was familiar with it, and you added WooCommerce as the shopping layer. Your store works at a basic level but you are noticing that payment failures are increasing, pages load slowly, or your multilingual configuration is not sending the right traffic to the right language version.

You are running eSewa or Khalti as your payment gateway and have either installed the official WooCommerce plugin and found it breaks periodically, or you have not yet set up payment gateways at all and are handling transactions manually.

You have more than 500 products on your WooCommerce store and you are experiencing noticeably slower performance on product listing pages, the cart, or checkout — particularly during higher-traffic periods.

You have a Nepali/English store configured with WPML and you suspect — or have been told — that your hreflang implementation is incorrect and is affecting your organic search visibility with international buyers.

You know your WooCommerce installation has not been maintained properly: plugins are outdated, the WordPress version is behind, and you are uncertain whether your hosting configuration is adequate for your current traffic.

What's broken

Four WooCommerce problems that are common in Nepal

eSewa's official WooCommerce plugin breaks when eSewa updates its API

eSewa has an official WooCommerce plugin, but it is updated irregularly. When eSewa updates its ePay API — which it has done multiple times — stores relying on the official plugin begin experiencing payment failures that are difficult to diagnose because the error messages from the plugin are not specific. Customers reach the eSewa payment screen and are either unable to complete the transaction or are returned to the WooCommerce store with an order status that does not match what happened in eSewa's system. For production WooCommerce stores that depend on eSewa as a primary payment method, a custom plugin built directly against eSewa's ePay API is more reliable than the official plugin. It gives your development team direct control over the integration logic and means a future eSewa API update does not break checkout until an official plugin update is eventually released.

No object caching configured on Nepali shared hosting

WooCommerce is a database-heavy platform. Every product page, cart update, and checkout step triggers database queries. On a correctly configured server with Redis or Memcached object caching, many of those queries are served from cache rather than hitting the database on every request. On a shared hosting environment — such as those commonly used by Nepali WooCommerce stores on Vianet, Subisu, or similar providers — object caching is typically not enabled by default. The result is that your WooCommerce store runs every query against the database on every page load. Product pages are slower than they need to be. The cart and checkout are particularly affected because they involve non-cacheable operations that stack on top of the already uncached database queries. Customers experience slow load times that are not a code problem — they are a server configuration problem. Configuring Redis or Memcached object caching, combined with a page caching plugin such as WP Rocket or LiteSpeed Cache, significantly reduces database load and improves page response time without changing any of your WooCommerce code.

WPML hreflang configured incorrectly for Nepali/English stores

WPML is the most widely used multilingual plugin for WooCommerce and WordPress. When it is set up correctly, it creates separate Nepali and English versions of your product pages and tells Google which version to serve to which audience using hreflang tags. When it is configured incorrectly — which happens frequently because the WPML hreflang settings interact with both your WordPress permalink structure and your SEO plugin — Google does not receive clear signals about which page is for which language. The consequence for a Nepali e-commerce brand targeting both domestic Nepali buyers and international English-speaking buyers is that Google may serve the Nepali-language page to an English-language searcher from Australia or the US, or it may index both versions as duplicate content and reduce the ranking authority of both. Fixing WPML hreflang configuration requires auditing your current hreflang output, correcting the WPML language settings, ensuring your SEO plugin (Yoast or Rank Math) is not overriding WPML's hreflang, and validating the output with Google Search Console.

WooCommerce product database not optimised for stores with growing catalogues

WooCommerce stores accumulate database weight over time. Every product update creates a post revision. Every session creates a transient. Orphaned product metadata from deleted or edited products accumulates in the wp_postmeta table. Stores that have been running for two or more years with 500 or more products, and that have not had a database maintenance pass, typically have wp_postmeta tables three to five times larger than necessary. The effect is slow product listing pages — particularly collection pages that query across many products — and slower checkout performance. This is not a hosting problem and not a code problem. It is a database problem that is resolved by removing post revisions, clearing expired transients, removing orphaned metadata, and running a database optimise pass. Following that, implementing a database maintenance schedule and limiting the number of stored revisions in wp-config.php prevents the problem from recurring.

What we engineer

WooCommerce development services for Nepal

eSewa and Khalti integration

We build custom WooCommerce payment gateway plugins against the eSewa ePay API and Khalti API. For production stores, this approach is more reliable than the official plugins because your integration is not dependent on third-party plugin maintenance cycles. We handle the full integration: API authentication, payment initiation, callback handling, order status updates, and failed payment logging.

Object caching and performance configuration

We audit your current hosting environment, identify whether Redis or Memcached is available, configure object caching at the WordPress and WooCommerce level, and implement page caching. We also audit your WooCommerce settings for performance-relevant configuration: product query settings, session handling, and background processing configuration for WooCommerce's action scheduler.

WPML multilingual WooCommerce setup

We configure WPML for Nepali/English WooCommerce stores correctly from the start, or audit and fix existing WPML configurations. This includes hreflang output validation, permalink structure for multilingual stores, product translation workflow, and WooCommerce-specific WPML settings for shipping zones, tax, and currency by language.

WooCommerce database optimisation

We audit your WooCommerce database, identify and remove accumulated weight (post revisions, expired transients, orphaned metadata), optimise database tables, and implement ongoing maintenance settings. For stores with large product catalogues, we also review and optimise the product query configuration in WooCommerce settings and consider indexed database views where relevant.

Custom WooCommerce plugin development

Where standard WooCommerce plugins do not cover your business requirements — custom order flows, integration with Nepali logistics providers, export documentation generation, or bulk order handling for B2B buyers — we build custom WooCommerce plugins that are maintainable and documented.

WooCommerce store builds

For new WooCommerce store builds, we handle theme selection or custom theme development, plugin selection and configuration, payment gateway setup, shipping zone configuration, tax setup, and initial performance configuration. We do not build stores on page builders that create maintenance overhead; we build on themes and configurations that are sustainable.

Request a WooCommerce Development Brief →
What changes

What a correctly built and maintained WooCommerce store looks like

Before
After
Before eSewa has an official WooCommerce plugin, but it is updated irregularly. When eSewa updates its ePay API — which it has done multiple times — stores relying on the official plugin begin experiencing payment failures that are difficult to diagnose because the error messages from the plugin are not specific. Customers reach the eSewa payment screen and are either unable to complete the transaction or are returned to the WooCommerce store with an order status that does not match what happened in eSewa's system. For production WooCommerce stores that depend on eSewa as a primary payment method, a custom plugin built directly against eSewa's ePay API is more reliable than the official plugin. It gives your development team direct control over the integration logic and means a future eSewa API update does not break checkout until an official plugin update is eventually released.
After Payment failures from eSewa drop significantly. Orders that were previously getting stuck at the payment gateway — or completing on the eSewa side but not updating in WooCommerce — are processed correctly and order statuses are reliable. Your operations team stops spending time manually reconciling eSewa payments against WooCommerce orders.
Before WooCommerce is a database-heavy platform. Every product page, cart update, and checkout step triggers database queries. On a correctly configured server with Redis or Memcached object caching, many of those queries are served from cache rather than hitting the database on every request. On a shared hosting environment — such as those commonly used by Nepali WooCommerce stores on Vianet, Subisu, or similar providers — object caching is typically not enabled by default. The result is that your WooCommerce store runs every query against the database on every page load. Product pages are slower than they need to be. The cart and checkout are particularly affected because they involve non-cacheable operations that stack on top of the already uncached database queries. Customers experience slow load times that are not a code problem — they are a server configuration problem. Configuring Redis or Memcached object caching, combined with a page caching plugin such as WP Rocket or LiteSpeed Cache, significantly reduces database load and improves page response time without changing any of your WooCommerce code.
After Product pages load faster. The combination of object caching, page caching, and database optimisation means your store is not running unnecessary database queries on every page load. The improvement is most visible on product listing pages and checkout, which are the two points in the purchase path where slow performance most directly affects conversion.
Before WPML is the most widely used multilingual plugin for WooCommerce and WordPress. When it is set up correctly, it creates separate Nepali and English versions of your product pages and tells Google which version to serve to which audience using hreflang tags. When it is configured incorrectly — which happens frequently because the WPML hreflang settings interact with both your WordPress permalink structure and your SEO plugin — Google does not receive clear signals about which page is for which language. The consequence for a Nepali e-commerce brand targeting both domestic Nepali buyers and international English-speaking buyers is that Google may serve the Nepali-language page to an English-language searcher from Australia or the US, or it may index both versions as duplicate content and reduce the ranking authority of both. Fixing WPML hreflang configuration requires auditing your current hreflang output, correcting the WPML language settings, ensuring your SEO plugin (Yoast or Rank Math) is not overriding WPML's hreflang, and validating the output with Google Search Console.
After Your multilingual store sends the right traffic to the right page. English-speaking buyers from international markets reach your English product pages. Nepali-speaking buyers reach your Nepali pages. Google Search Console shows correct hreflang implementation and you stop seeing international organic traffic going to Nepali-language pages.
Before WooCommerce stores accumulate database weight over time. Every product update creates a post revision. Every session creates a transient. Orphaned product metadata from deleted or edited products accumulates in the wp_postmeta table. Stores that have been running for two or more years with 500 or more products, and that have not had a database maintenance pass, typically have wp_postmeta tables three to five times larger than necessary. The effect is slow product listing pages — particularly collection pages that query across many products — and slower checkout performance. This is not a hosting problem and not a code problem. It is a database problem that is resolved by removing post revisions, clearing expired transients, removing orphaned metadata, and running a database optimise pass. Following that, implementing a database maintenance schedule and limiting the number of stored revisions in wp-config.php prevents the problem from recurring.
After Your development team can maintain the store reliably. Custom plugins are documented. Plugin count is rationalised. The WordPress and WooCommerce installation is on a current version with a defined update process. You are not dependent on a single developer who knows the undocumented configuration history of the store.
How it works

How we work on WooCommerce projects in Nepal

  1. 01

    Technical discovery

    Before any development work begins, we audit your current WooCommerce installation. This covers: WordPress and WooCommerce version, active plugin list and last-updated dates, hosting environment and available server-level caching, database size and table health, current payment gateway configuration, and any known issues you have been experiencing. For new builds, we scope the technical requirements based on your product catalogue, payment methods, and any integration requirements.

  2. 02

    Brief and scope

    We document the specific work to be done, the expected outcomes, and the timeline. For complex projects — custom payment gateway plugins, multilingual store configurations, or migration work — we include a technical specification that describes the implementation approach. You review and approve the scope before work begins.

  3. 03

    Development

    Development work is carried out in a staging environment that mirrors your production hosting. For payment gateway integrations, we test against the sandbox environments provided by eSewa and Khalti before going to production. For performance work, we measure before and after using consistent benchmarks so the improvement is documented.

  4. 04

    Testing and quality review

    We test the complete purchase path — product discovery, product page, cart, checkout, payment, order confirmation, and post-order email — in both languages where applicable. Payment gateway integrations are tested for success, failure, and timeout scenarios. We document any edge cases encountered during testing.

  5. 05

    Deployment and handover

    We deploy to production during a low-traffic window and monitor immediately after deployment. We provide documentation for any custom plugins developed, and a written summary of the configuration changes made. If your team needs training on ongoing maintenance tasks, we provide that as part of the handover.

Request a WooCommerce Development Brief →
Common questions

WooCommerce questions from Nepali e-commerce businesses

Is eSewa's official WooCommerce plugin reliable for a production store?

eSewa's official WooCommerce plugin works for low-stakes testing but has a history of breaking when eSewa updates its ePay API, because the plugin is not always updated in step with API changes. For a production WooCommerce store where eSewa is a primary payment method, a custom WooCommerce payment gateway plugin built directly against the eSewa ePay API is more reliable. You control the integration code, you can update it immediately when eSewa changes the API, and you have full visibility into the payment flow and error handling rather than relying on what the official plugin exposes. The build cost of a custom eSewa integration is typically recovered within weeks by eliminating the revenue lost to payment failures and manual reconciliation.

How do I set up object caching for a WooCommerce store hosted in Nepal?

Object caching for WooCommerce requires Redis or Memcached to be enabled at the server level by your hosting provider. On Nepali shared hosting plans, this is not always available by default, but many providers will enable it on request. Once the server-level cache store is available, you install a WordPress object cache drop-in — the most common are the Redis Object Cache plugin or the W3 Total Cache object cache module — and configure the connection to the Redis or Memcached instance. This is separate from page caching (which caches full HTML pages) and covers the database query caching that WordPress and WooCommerce use internally. The two work together: page caching handles anonymous page loads, object caching handles the internal query results that non-cacheable pages and logged-in user sessions rely on.

How do I configure WPML correctly for a Nepali/English WooCommerce store without duplicate content issues?

Correct WPML configuration for a Nepali/English WooCommerce store requires setting the language URL format (subdirectory is the most reliable for SEO: yourstore.com/ne/ for Nepali and yourstore.com/ or yourstore.com/en/ for English), enabling the WPML hreflang output, and confirming that your SEO plugin (Yoast SEO or Rank Math) is set to defer to WPML for hreflang rather than generating its own. After configuration, validate the hreflang tags by inspecting the page source of both your English and Nepali product pages and checking that each page references the other with the correct lang attribute. Submit the updated sitemap — which WPML generates with both language versions — to Google Search Console and monitor the International Targeting report for errors. WPML also requires that you translate WooCommerce-specific strings (checkout fields, email templates, order statuses) separately from product content, using the WPML String Translation module.

How do I optimise a WooCommerce database that has become slow with too many products?

WooCommerce database optimisation for a slow store starts with a database audit to identify where the weight is: run a query against your wp_postmeta table to count rows and identify tables above normal size, check for expired transients in wp_options, and count post revisions in wp_posts. The cleanup process removes expired transients (using WP-CLI: wp transient delete --expired), removes post revisions (either via WP-CLI or a plugin like WP-Sweep, with a backup taken first), removes orphaned postmeta (rows in wp_postmeta where the associated post no longer exists), and then runs OPTIMIZE TABLE on the affected tables. After cleanup, set a post revision limit in wp-config.php (define( 'WP_POST_REVISIONS', 3 )) to prevent accumulation. For stores with 2,000+ products where product queries are the bottleneck, the WooCommerce product lookup tables (introduced in WooCommerce 3.7) should be enabled and verified as indexed correctly.

Should a Nepali e-commerce brand use WooCommerce or Shopify?

WooCommerce is the better choice for most Nepali domestic e-commerce brands for three practical reasons: eSewa and Khalti have WooCommerce integrations (official and custom) but no Shopify integrations, so Shopify stores in Nepal require workarounds for local payment; most Nepali developers with e-commerce experience are WordPress-familiar, making WooCommerce stores easier to maintain locally; and the total cost of ownership for a WooCommerce store on Nepali hosting is lower than Shopify's monthly subscription cost for a business at early stage. Shopify becomes more relevant for Nepali brands that are primarily targeting international buyers (where eSewa/Khalti are not needed), want a fully managed platform with no server maintenance, or are building a brand that plans to scale internationally and prefers Shopify's ecosystem of international apps. For businesses that are primarily selling to Nepali customers and processing payments via eSewa and Khalti, WooCommerce is the practical choice.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
About Us →
Start here

Start with a WooCommerce development brief

If your WooCommerce store has payment gateway failures, performance problems, or a multilingual configuration that is not working correctly, a development brief is the right starting point. We audit what is actually broken before scoping any work.

Request a WooCommerce Development Brief →