עברית
Home › WooCommerce
WooCommerce developer

WooCommerce store development, built to hold up at peak sales.

We build WooCommerce stores in code: a theme written from scratch, connections to payment processing, invoicing and a shipping carrier, and ERP and CRM sync where needed. Before the store opens to customers, we run full test orders. The price is set in a quote, based on scope.

Let's build your store

A WooCommerce store built the right way

When the site is a store, every problem at checkout or in inventory shows up as orders that never came in. These are the areas where a WooCommerce store is put to the test.

Stable under sales load

Code-level optimization that lowers the risk of a crash exactly when it matters most.

Secure payment processing

A direct connection to leading payment gateways and a smooth payment flow.

Shipping integration

A full connection to shipping carriers, with automatic status updates.

ERP / CRM sync

Inventory and orders synced with Priority, SAP and other management systems.

Discounts and coupons

Complex discount and coupon rules that follow your promotions exactly.

A cart that converts

A smooth shopping experience that reduces cart abandonment.

What does a WooCommerce developer do, and who is it for?

A WooCommerce developer builds and adapts the store at the code level: the pricing and promotion logic, the checkout flow, inventory management, and the connections to the systems your business already uses. WooCommerce is an open-source WordPress plugin whose core is written in PHP. It can be changed and extended through Hooks and its other official extension points, without touching core files and without losing the changes in the next update.

This suits businesses where the store is the main sales channel and the requirements are no longer solved well by one more plugin: a catalog with many variations, a separate price list for business customers, inventory managed in an ERP system, or shipping and pickup rules specific to the business. It also suits anyone running an existing store that has started to slow down and who needs someone who understands what is happening underneath the admin interface.

When you work with us, you talk directly to the developer who writes the code, from scoping through to after launch, and the code written for the store stays yours. If you have not chosen a platform yet, the online stores page has a short comparison of WooCommerce, Shopify and a custom-coded store.

How is a WooCommerce store built, step by step?

Building a WooCommerce store starts with a scoping call. Before a line of code is written, we settle what the store sells, how the catalog is structured, which payment gateway and which shipping carrier the business works with, and which systems need to receive data from the store. In online store development these decisions set most of the scope, and it is better to make them before the quote than halfway through the work. The work breaks down into these stages:

The weight of each stage varies from store to store. In a store with a small catalog and payments only, the integrations stage is very short. A store that replaces an old store spends most of its time on moving the data and on checking that no URL has disappeared. When testing an order, we check that the invoice was created, that inventory went down and that the order reached the system that receives it, not only that the page loaded.

When does a store need a WooCommerce developer instead of another plugin?

A store needs a developer when the problem is performance or business logic, not a simple feature that an existing plugin already solves well. Every active plugin loads on each request that reaches WordPress and runs its own code, so one more plugin usually adds load instead of dealing with the source of the problem.

In these cases we start by reviewing the existing store: which plugins are active and what each one loads, which queries put load on the database, and what happens on the pages where the customer pays. Sometimes several plugins are replaced by one piece of dedicated code, and sometimes it is enough to fix the server and cache settings. A rebuild is considered only when the theme itself limits the store. These are the signs that usually lead to such a review:

A ready-made, maintained plugin that solves a simple need is usually a reasonable choice, and we do not replace it with code just for the sake of writing code. Dedicated code comes in when the logic is specific to the business, or when one plugin needs several more plugins to work. And anyone who prefers a store that does not rely on WordPress at all can look at the page on building a sales website in custom code.

The technical decisions behind a WooCommerce store

The foundation is a lightweight theme, business logic kept in dedicated code instead of scattered across off-the-shelf plugins, and a database and cache set up for the needs of a store. With us, the theme is written in code from scratch, with no Elementor, and the business logic lives in a dedicated PHP plugin. That way every customization, from discount rules to shipping fee calculation, is written through WooCommerce's official extension points and is not erased when the core updates. It is the same approach we use in WordPress development.

On the data side, in current versions of WooCommerce new stores keep orders in dedicated tables (HPOS) rather than in the general posts tables of WordPress, which eases the load on the database as the number of orders grows. In an existing store, we check that all plugins are compatible before moving to HPOS. The cart, checkout and account pages are excluded from page caching because they differ for every customer, and on those pages speed comes down to the code and the server.

ERP and CRM connections are built against the API of the external system and against the REST API and Webhooks of WooCommerce, and heavy sync runs in the background, not while the customer is paying. Product and checkout pages are planned mobile first and made accessible in code to the Israeli standard IS 5568, including the checkout form, and payments connect to cards and digital wallets depending on what the payment gateway supports.

Hosting is part of these decisions too. A store with inventory and orders puts more demand on the server than a business website, and its database is working all the time, so it makes sense to host it on a server set up for that. With us, it can be hosted on NVMe servers with SSL and a daily backup. When the developer who wrote the code is also the one who runs the server, it is easier to match the code and the server settings to each other, and when something does not work there is one place to go. Details are on the hosting and domains page.

Store integrations: what can be connected and what to decide upfront

Every integration needs a decision on which system is the source of truth, what happens when the connection fails, and how to trace a problem that only surfaces a week later. Connecting to a system with a documented API is easy to price in advance, while connecting to a closed system with no API is usually the expensive part of a project. So it is worth asking the ERP vendor in the scoping call whether an API exists and who grants access to it. You can find more about connections to business systems on the business systems and integrations page.

Connecting WooCommerce to an email marketing system is worth planning from the start, because it affects the checkout. Order confirmations and status updates are sent from the store itself, while marketing emails, for example after a purchase, are sent from the email marketing system the business uses. It is worth deciding who goes on the list and with what consent, and adding the matching field to the checkout.

The table summarizes the common integrations in a store, what passes through each one, and what is worth deciding before development starts:

IntegrationWhat passes between the systemsWhat to decide upfront
PaymentsCredit card payment, and, depending on what the payment gateway supports, also Bit, Apple Pay and Google PayWhich gateway the business works with, and what happens with a failed payment or a refund
InvoicingAn automatic invoice for every orderWhich invoicing system the business uses, and what happens with a canceled order
ShippingShipping and pickup options at checkout, and with carriers that allow a connection, also the order details and shipping statusWhich regions and prices are set up, and who updates the status when there is no connection
ERP or CRMInventory, prices and orders, through the system's API and the REST API and Webhooks of WooCommerceWhich system sets inventory and price, how often the sync runs, and what happens when it fails
Email marketing systemCustomers and orders sent to the email marketing system the business usesWho goes on the list, and with what consent

How do you design the store and plan the customer journey?

The theme of the store is written in code to fit the brand and the catalog, with no Elementor, so there is no page builder layer adding code to every page. This matters most on the product and checkout pages, where the customer decides whether to buy. We went through the comparison of the two approaches in detail on the custom code vs Elementor page.

The customer journey is the sequence a buyer goes through from the moment they reach the store until the order reaches them. It can be planned step by step, asking at each step what could stop them:

Often what stops a buyer is friction: an unnecessary field, a cost that shows up late, or a payment that fails without a clear message. If the store has data, for example how many visitors reach checkout and do not complete it, that data shows which step to fix first. A new store has no such data yet, so in the testing stage we go through the journey from end to end, on mobile as well, as if you were the customer.

How much does it cost to build a WooCommerce store?

Our WooCommerce stores start at NIS 4,490 (Israeli shekels). That is a starting point, and the final price is set by scope. For comparison, the guide to what a business website costs gives the market ranges: an online store usually costs between about NIS 5,000 and 30,000, and a custom-coded store from a development company between about NIS 15,000 and 50,000. A store with a simple catalog and payments only is one project, and a store that syncs with an ERP, calculates the price by customer type and migrates data from an old store is a different project altogether.

That is also why quotes for the same store can be very far apart: each quote assumes a different number of products, different integrations, and someone different preparing the content. So the starting amount does not replace a quote: the exact price is set after the scoping call, based on the number of products, the integrations and the logic the store needs. Anyone who is not yet sure which type of website suits the business can start with the guide to building a business website. The table breaks down what moves the price in each area and what is worth asking about in a quote:

FactorWhat changes the scopeWhat to ask in the quote
CatalogNumber of products, variations such as size and color, attributes for filtering, and who prepares the photos and descriptionsWhether entering the products is included, and how a large catalog is imported
Payments and invoicingOne gateway or several, additional payment methods and an automatic invoiceWhich providers the integration is built against, and confirmation that processing fees are set with the payment processor and are not included in the build price
ShippingShipping and pickup options, regions, and connections to the carriers that allow itWhich shipping carriers are included, and what happens with a carrier that has no connection
ERP or CRMSync direction, one-way or two-way, and what is synced: inventory, prices, ordersWhether there is a documented API, and who is responsible when the sync fails
Pricing logicA price list for business customers, quantity discounts, coupons and complex promotionsWhether the logic is written in a dedicated plugin whose code you own
Existing storeMigrating products, customers and orders, and 301 redirectsWhat exactly is migrated, and how to check that everything arrived
Design and account areaA theme in code built around the brand, and customizations in the customer's account areaHow many page types are designed separately

Comparing store quotes: what to check and which red flags to watch for

WooCommerce itself is free, but the build quote is only part of the cost. On top of it come ongoing costs: hosting and a domain, licenses for paid plugins if you choose any, and processing fees that are set directly with the payment processor. There is no platform subscription here as there is with Shopify, but there are updates and maintenance. When comparing quotes, it helps to separate what you pay once from what you pay every month or year, and to go through the items one by one:

And these are mistakes and red flags that come up again and again in stores and quotes:

The initial consultation with us is free and without commitment, and after it you get a quote that spells out what is included, so that you can compare.

How long does it take to build a WooCommerce store?

There is no fixed duration for developing a WooCommerce site, because the time is set mainly by the scope and by what happens outside development itself. As a market reference: the service page of another Israeli studio estimates three to four weeks for a basic store of up to 50 products, and stores with complex variations take longer. With us, the schedule is set in the quote, after the scoping call and according to the materials that are already ready.

Four things extend the process more than anything else, and almost all of them are on the business side:

Before the store opens to customers we run full test orders, from the cart through to the confirmation email. We covered the stages themselves in our article on how long a business website takes to build.

How does a well-built store help sales, SEO and marketing?

A well-built store helps in two places: at checkout, where the customer decides whether to complete the purchase, and in Google's search results. A checkout with fewer steps and fields, payment inside the store as far as the payment gateway allows, and inventory synced with the warehouse reduce the cases where customers leave halfway or order a product that is already out of stock.

On the Google side, we make sure every product page shows structured data of the Product type with price and availability, keep clean URLs for categories and products, and handle the URLs generated by filtering and sorting, so that Google does not waste crawling on duplicate versions of the same page. The speed and visual stability of product pages are measured by Core Web Vitals, which Google takes into account as part of page experience. A position in the results cannot be guaranteed. What can be done is to remove common technical obstacles in stores.

Marketing a store is separate work from building it, but a few things are better ready in the store before the first campaign: a product page where a visitor can buy right away, measurement of purchases to know which source they came from, and, in a store that advertises products in campaigns, accurate product data that can go into a product feed, such as one for Google Merchant Center. It is worth settling this already in scoping, because it is easier to plan during development than to add afterward. We covered organic search ranking in general in the guide to SEO and how pages rank on Google.

To update a price or launch a promotion you do not have to wait for a developer: you manage products, prices, orders and inventory yourself from the admin interface, with separate permissions for employees and without touching code. And when you need a new feature, another sync or a change in the purchase flow, you go back to the same WooCommerce developer who knows the store from the inside.

What happens after launch: maintenance, updates and backups?

A WordPress store needs work after launch as well. It is made of several parts that update separately: the WordPress core, the WooCommerce plugin, the theme and the other plugins. An update to any one of them can change how the checkout or an integration behaves, so every update is followed by a check that the store still works, including a test order that goes from the cart through to confirmation. It is best to do updates before a sale and not in the middle of one.

On the server side, it is important to have a daily backup that you can restore from. A store receives orders all the time, and orders that came in after the last backup will not appear in it, so a daily backup matters especially for a store. In a store hosted with us, the daily backup and SSL are included on the NVMe servers.

The scope of maintenance varies from store to store, so it is agreed in the quote and not left open. Prices, inventory and orders are managed by you in the admin interface, and a change in logic or a new integration goes back to the developer who built the store.

Frequently asked questions about WooCommerce

How much does it cost to build a WooCommerce store?

Our WooCommerce stores start at NIS 4,490 (Israeli shekels), and the final price is set by scope: the structure of the catalog and variations, the connection to payments, invoicing and shipping, sync with an ERP or CRM, special pricing rules and migrating data from an existing store. In the Israeli market, ranges of about NIS 5,000 to 30,000 are published for an online store and about NIS 15,000 to 50,000 for a custom-coded store from a development company. WooCommerce itself is free, but beyond the build price there are separate costs: hosting, a domain, paid plugins if you choose any, and payment processing fees. After an initial consultation, free and with no commitment, you will receive a detailed quote.

What is included in a WooCommerce store build?

The store is built on a custom-coded theme, with no Elementor, planned mobile first and accessible to the Israeli standard for web content accessibility. It includes a payment connection, automatic invoicing, shipping options, structured data for products and an admin interface for orders, inventory and customers, with permissions for employees. If needed, you can add hosting on NVMe servers with SSL and a daily backup, as well as domain registration. You work directly with the developer, and the code written stays yours.

How long does it take to build a WooCommerce store with ERP sync and payment integration?

It depends on the scope and on how ready the materials are. A store with an organized catalog and payments only moves faster than a store with ERP sync, data migration and custom pricing logic. Payments and sync also depend on a third party: merchant approval with the payment processor is a process the business runs with them, and ERP sync requires API access from the vendor and a round of testing with real data. It is worth starting both early. Photos and product descriptions that are not ready yet delay a project just as much. In the scoping call we build a schedule around the stages of your project.

When is custom-coded WooCommerce a better choice than Shopify?

Custom-coded WooCommerce suits stores with complex business logic, such as a separate price list for business customers or unique shipping rules, stores that need integration with an existing ERP or CRM, or stores with a lot of content alongside the shop. It runs on WordPress on hosting you choose, so the code and the data are under your control, and almost every step of the purchase process can be customized. Shopify is a managed, subscription-based platform, quick to set up and easy to maintain, but customization is limited to what the platform and its apps allow. We work with both and recommend one based on your products and budget.

Can the store be connected to a payment gateway and a shipping carrier?

Yes. We connect the store to the payment gateway the business already works with, for credit card payments and digital wallets such as Bit, Apple Pay and Google Pay, depending on what the gateway supports, and we set up automatic invoice creation for every order. On the shipping side, the store shows the customer shipping and pickup options, and when the carrier allows a connection, the order details are passed to it and the shipping status updates automatically. Complex discount and coupon mechanisms are built in the same process, so that the total at checkout matches the promotion rules.

Can you sync inventory with an ERP system?

Yes. We sync inventory, prices and orders with ERP systems such as Priority and SAP, or with a CRM system, through the system's API and the REST API and Webhooks of WooCommerce. We define in advance which system sets the inventory and the price, how often the sync runs, and what happens when a connection fails. That way orders enter the ERP without double entry, and the inventory on the site is updated according to what is in the warehouse.

How do you connect a WooCommerce store to an email marketing system?

The store is connected to the email marketing system the business already works with, so that customers and orders are sent to it automatically. Before that, we define which data is passed, who goes on the list and with what consent to receive mailings. Order confirmations and status updates are sent as usual from the store, while marketing messages, such as a follow-up email after a purchase, are sent from the email marketing system. It is worth deciding this already in scoping, because it affects the checkout fields and the consent collected there.

Why do WooCommerce stores slow down or freeze under load?

Usually the cause is a buildup of plugins, each of which runs its own code and queries, together with a server that was not tuned for the load of a store. It is especially noticeable on the cart and checkout pages, which are not kept in the page cache. We solve this in code: we replace heavy plugins with dedicated code and optimize the database queries and the server settings, so that the store handles the load of sales and campaigns better.

Can an existing WooCommerce store be improved without rebuilding it?

Usually yes, but it depends on the source of the problem. We start by reviewing the plugins, the queries and the cart and checkout pages, and then fix the actual cause, such as replacing several plugins with one dedicated piece of code or tuning the server and the cache. A rebuild is needed only when the theme itself is limiting, and then every URL that changes gets a 301 redirect, so that the ranking and the links the old URL accumulated are not lost.

Can you develop a custom WooCommerce plugin?

Yes. When the business needs logic that is not available in the settings or in off-the-shelf plugins, such as a price list for a customer group, a quantity discount or a unique shipping rule, we write a dedicated PHP plugin that builds on the Hooks and API of WooCommerce. The plugin is separate from the theme and from core files, so a WooCommerce update does not erase it. It includes only what the store needs, and the code written stays yours, so it can keep being developed as the business grows.

Ready for a stable store that is tested before launch?

Tell us about your business. The initial consultation is free and carries no commitment.

Get a Quote