WooCommerce is the most popular e-commerce plugin for WordPress. These WooCommerce interview questions cover store setup, products, payments, shipping and taxes for beginners, then hooks, customisation, performance and scaling for developers who build and maintain online stores.
30 questions · Updated
Fundamentals, definitions and simple scenarios. Good for freshers and warm-ups.
WooCommerce is a free, open-source plugin that turns a WordPress site into an online store.
It gives full control over code, hosting and data and has thousands of extensions, but you manage hosting, updates, security and performance yourself.
Shopify is a hosted platform with a monthly fee that handles all of that for you, with less freedom to customise checkout and the backend.
Simple products (one item with one price), variable products (variations such as size and colour, each with its own price, SKU and stock), grouped products (a collection of related products), and external or affiliate products that link to another site.
A product can also be marked virtual (no shipping) or downloadable.
Extensions add subscriptions, bookings and bundles.
Under WooCommerce settings I enable payment gateways such as Razorpay, PayU, Stripe, PayPal or cash on delivery.
For shipping I create shipping zones by region and add methods such as flat rate, free shipping above an amount, or live carrier rates.
For tax I enable taxes, set whether prices include tax, and add tax rates, for example GST slabs in India, by class and location.
Install the WooCommerce plugin on WordPress, run the setup wizard to set the store address, currency (such as INR), industry and product types, then configure payments, shipping, tax and emails. Choose a WooCommerce-compatible theme, add products and policy pages, enable HTTPS, and place test orders before launch.
Shop (the product archive), Cart, Checkout and My Account, plus pages such as order received and lost password.
They are set in WooCommerce settings.
New stores use the block-based cart and checkout, while older ones may use shortcodes such as [woocommerce_cart].
Deleting or changing these pages without updating the settings breaks the store.
Coupons, created under Marketing > Coupons, can give a percentage discount, a fixed cart discount or a fixed product discount, and can include free shipping. Restrictions include minimum and maximum spend, specific products or categories, excluded sale items, allowed emails, usage limits per coupon and per user, and expiry dates.
Categories organise products hierarchically for navigation, such as Men > Shirts.
Tags are flat keywords.
Attributes describe product characteristics such as size, colour or material; global attributes are reusable across products and can be used for layered filtering, and attributes marked "used for variations" create variable products.
Orders appear under WooCommerce > Orders with their status: pending payment, processing (paid and awaiting fulfilment), on hold, completed, cancelled, refunded or failed. Store staff view details, add order notes for the customer or privately, print invoices with a plugin, process refunds (automatically through supported gateways) and mark orders completed when shipped.
Guest checkout reduces friction and usually increases conversion, because many buyers abandon carts when forced to register.
Account creation can still be offered at or after checkout.
Accounts help repeat customers view orders and save addresses, and are required for subscriptions or memberships.
The settings are under Accounts & Privacy.
Customer emails include processing order, completed order, refunded order, customer invoice, customer note, new account and password reset; admin emails include new order, cancelled order and failed order.
They can be customised in settings or by overriding templates in the theme.
Reliable delivery needs an SMTP or transactional email service rather than the server's PHP mail.
Payment gateways (Razorpay, PayU, Stripe, PayPal), WooCommerce Subscriptions for recurring payments, Bookings for appointments, Product Add-Ons, Memberships, shipping integrations such as Shiprocket, invoice and GST plugins, product reviews and email marketing integrations. Each extension adds code, so only well-maintained ones should be installed.
Applied problems, trade-offs and questions about your own projects.
I use WooCommerce's actions and filters, such as woocommerce_before_add_to_cart_button or woocommerce_checkout_fields, in a child theme or custom plugin.
To change templates I copy the file from woocommerce/templates into my theme's woocommerce folder and edit that copy, keeping an eye on template version notices after updates.
Editing plugin files directly is lost on the next update.
For the classic checkout, I add the field with the woocommerce_checkout_fields filter, validate it on woocommerce_checkout_process, and save it to the order with woocommerce_checkout_create_order using $order->update_meta_data.
I display it in the admin and emails with the relevant hooks.
The newer block checkout uses the Additional Checkout Fields API instead, so I check which checkout the store uses first.
High-Performance Order Storage moves orders out of the WordPress posts and postmeta tables into dedicated order tables.
Queries become much faster and the database scales better for stores with many orders.
Custom code should use the WooCommerce CRUD objects such as wc_get_order and $order->get_meta instead of get_post_meta, so it works with both storage methods.
With stock management enabled, WooCommerce reduces stock when an order is paid or set to processing, can hold stock for unpaid orders for a set time, and sends low-stock notifications.
Order statuses include pending payment, on hold, processing, completed, cancelled, refunded and failed.
Custom statuses can be registered for workflows such as "shipped".
The block-based Cart and Checkout are the default for new stores: faster, more modern and with a better user experience, but older customisations made with classic PHP hooks such as woocommerce_checkout_fields do not apply, and they are extended with the Store API and JavaScript extensibility instead. Some payment and checkout plugins still require the classic shortcode checkout, so compatibility must be checked.
Generate consumer key and secret pairs under Settings > Advanced > REST API with read or read/write permissions, then call endpoints such as /wp-json/wc/v3/products and /orders over HTTPS with those credentials.
It is used to sync products, stock and orders with ERPs, mobile apps and marketplaces.
The Store API serves customer-facing cart and checkout actions for headless frontends.
Webhooks send an HTTP POST with JSON data to a URL when an event happens, such as order created, order updated or product updated, configured under Settings > Advanced > Webhooks.
They let external systems react in real time, for example sending orders to a fulfilment service.
The receiver should verify the signature, respond quickly and process the data in the background.
WooCommerce has a built-in CSV product importer and exporter that handles simple and variable products, prices, stock, categories, attributes and image URLs, and can update existing products by ID or SKU.
I test with a few rows first and back up before large imports.
For complex or scheduled imports, plugins such as WP All Import or the REST API are used.
The product page is built from actions such as woocommerce_single_product_summary, where each element (title, rating, price, excerpt, add to cart button, meta) is attached with a priority number. You can move or remove elements with remove_action and add_action using those priorities, or add content such as a delivery estimate, in a child theme or custom plugin.
Each variation of a variable product can have its own SKU, regular and sale price, stock quantity, weight, dimensions, image and shipping class, and stock can be managed at product level or per variation.
Default selections can be set, and the price range shown on the shop page comes from the variations.
Hundreds of variations slow the product page, so they are kept reasonable.
Simplify checkout (guest checkout, fewer fields, address autocomplete), show shipping costs and delivery times early, offer trusted local payment options such as UPI and cash on delivery, make the site fast on mobile, and add trust signals. Abandoned cart recovery plugins or email and WhatsApp tools send reminders to customers who left their contact details, sometimes with an incentive.
System design, deep internals, leadership and tough follow-ups.
I use managed WordPress hosting with enough PHP workers, Redis object cache and page caching that excludes the cart, checkout and account pages.
I enable HPOS, offload images to a CDN, remove slow plugins found with Query Monitor, and move heavy tasks such as emails and imports to Action Scheduler background jobs.
Before sales events I load-test the checkout.
I use the WooCommerce REST API with API keys, or webhooks for events such as order created or product updated, to sync orders, stock and prices with the ERP.
I decide which system owns each piece of data, handle failures with retries and logs, and avoid overloading the store by batching updates.
Off-the-shelf connectors exist for systems like Zoho and Tally.
I check the WooCommerce status logs and the payment gateway dashboard to see whether payments succeeded.
A common cause is the gateway's webhook or callback failing because of a wrong URL, a firewall, a caching rule or an SSL issue, so the order stays pending.
I test in sandbox mode, check the webhook delivery log, fix the cause, and reconcile affected orders manually with the gateway records.
For multiple languages, use WPML, Polylang or TranslatePress to translate products, pages and emails, with hreflang tags for SEO. For multiple currencies, use a multi-currency plugin or WooCommerce Payments' multi-currency feature, with exchange rates or fixed prices per currency, gateways that support those currencies, and correct tax and shipping rules for each market.
Use payment gateways that keep card data off your server, such as hosted payment pages, redirects or tokenised payment fields, so PCI scope stays minimal. Keep everything updated, use strong admin passwords with two-factor authentication, limit admin users, use a web application firewall and malware scanning, enforce HTTPS, protect against card testing attacks with rate limiting and CAPTCHA, and take regular off-site backups.
Create a plugin with a class extending WC_Payment_Gateway, set its ID, title and settings fields, and implement process_payment to create a payment with the provider and return a redirect URL or result.
Handle the provider's callback or webhook to verify the payment signature and update the order status with payment_complete, and implement process_refund.
It must also support the block checkout through the payment method integration API.
Use HPOS, a persistent object cache such as Redis, and page caching for non-cart pages.
Move product search and filtering to Elasticsearch or OpenSearch (for example with ElasticPress), avoid huge numbers of variations, optimise images, limit plugins that run on every page, and keep the database tidy by cleaning old sessions, transients and logs.
Cart fragments AJAX can be disabled where not needed.
Use customer roles or groups with role-based pricing and tiered quantity discounts, hide prices or require login for wholesale catalogues, set minimum order quantities, allow quote requests, offer payment on account or invoice terms, apply tax exemptions with GST details, and provide quick order forms for bulk ordering. Plugins such as B2BKing or WooCommerce Wholesale Prices add these features.
See all WordPress & Shopify Developer interview questions, covering WordPress, WooCommerce, Shopify, Shopify Liquid, Wix and more.