Before you build a WooCommerce store, settle four decisions: whether WordPress and WooCommerce fit how you sell, how the catalog is structured (products, variations, stock), which payments shipping and invoicing you must connect, and what “ready to launch” means for a real purchase. A store built without those four usually goes live into a week of emergency fixes.

You already sell by phone or in a physical shop, and it is time to sell online too. The first call with a developer jumps to “nice theme” and “checkout”, while you still have not decided whether you need live stock, shipping by weight, or just a product page with a contact button. Before anyone builds, here is what is worth deciding.

When does a WooCommerce store fit your business?

WooCommerce fits when you want a store on WordPress: content and products in one place, control over the purchase flow, and room to connect outside systems without moving to a closed platform. If you already run WordPress, or you need strong content pages beside the shop, it is a natural base.

It fits less well if you only need a single page with a link to an external payment form, or if every sale stays on a marketplace and you do not plan to manage stock and prices yourself. In those cases a full store adds complexity without payoff. The question is not whether WooCommerce is popular. It is whether you need to own the catalog, orders and customers.

Tip: Write one sentence for what the customer does from landing to payment. If you cannot write it without “it depends”, you are not ready to pick a theme or a plugin.

What should you decide about the catalog first?

Decide what a product means in your business, not what the theme demo shows. How many product types you have, whether there are variations (size, colour, pack), whether price changes by quantity, and whether stock drops automatically after an order. Those choices shape the store more than the colour palette.

If products come from different suppliers, or some are pickup-only, that has to be clear before development. Same for content: who writes product names, who uploads photos, who owns the descriptions. A store without clear catalog ownership stalls after design, not before it.

Tip: Take ten real products and paste them into a table: name, price, variations, shipping weight, stock status. If ten products already feel messy in a spreadsheet, they will feel worse in a live store.

Payments, shipping and invoices: what do you connect?

Connect what the business already uses, or choose the provider before development, not halfway through. Payments, shipping and invoicing are not a “finish later” add-on. They sit inside checkout, and late connections create surprises at the card form, in the customer email and in your reporting.

Before you start, answer three questions: which payment methods your customers actually use, whether you offer pickup beside delivery, and who issues the invoice after purchase. If those answers are open, design and products can move forward, but a real completed order cannot.

Tip: Ask your payment and shipping providers for their WooCommerce or API connection notes before anyone clicks “start building”. You will know early whether you need a ready connector or custom work.

Ready-made theme or a custom WooCommerce build?

A ready-made theme saves time when the flow is simple: a clear catalog, standard payments, shipping by zone or a flat rate. As soon as you need complex discounts, made-to-order products, a business customer area, or a connection to an internal system, a theme starts breaking at the edges.

Custom development does not mean rebuilding everything for pride. It means shaping the flow around your business, with clean code and room to grow. Websight’s development page covers WordPress sites, WooCommerce stores and connections to payments and internal systems, on a fixed project price. That is the path when the store is a core sales tool, not a two-week experiment.

Tip: If you are unsure, describe two real purchase scenarios from your business, not a demo product. The theme-versus-custom answer usually appears as soon as the scenario includes one real exception.

What do you check before the store goes live?

You check a full purchase, not only that the page looks right. Before launch, run at least once through: add to cart, coupon if you use one, shipping choice, a real or sandbox payment, the customer confirmation email, the order in admin, stock decrease, and the same path on mobile.

Also check what happens when something fails: a declined payment, a product that sells out mid-checkout, an odd shipping address, and a cancelled order. A store that cannot show a clear error makes customers guess and fills your phone with calls.

Tip: Run the purchase test from a device and phone number that are not known as admin users. What works for a logged-in editor often breaks for a normal visitor.

What happens after the store is live?

After launch comes routine: core and plugin updates, backups, watching failed orders, and fixing connectors that break after an update. A WooCommerce store with nobody owning that work stays stable only until the next update that breaks a payment or shipping plugin.

If you do not have an internal team for that, look at Websight’s WordPress maintenance plans, which include updates, daily off-site backups and WooCommerce support by plan level. Design still matters after launch too: if checkout confuses people, UX/UI design is where you fix the flow before stacking more plugins.

One last step before you ask for a quote or open a theme: write down ten products, the payment methods, the shipping options and the one purchase path that must not fail. Those four save more arguments than any debate about button colour. If you want to talk it through with people who build these stores for a living, start on the development page and say what you sell and what must work on day one.

שאלות נפוצות

How long does it take to build a WooCommerce store?

It depends on catalog size, how many payment shipping and invoice connections you need, and whether you use a ready-made theme or a custom build. A store with products ready and a simple flow is shorter than one with complex variations and links to existing systems. Lock the four decisions at the top of this article before you lock a timeline.

Can you build a WooCommerce store without a developer?

You can start alone if the catalog is small, connectors are standard, and you are willing to learn the breakage too. Once you need local payment methods, weight-based shipping, complex discounts or a mobile checkout that does not fall apart, most businesses find the “saved” build time returns as urgent fixes after launch.

What is the difference between a WooCommerce store and a single sales page?

A single sales page pushes one product or campaign. A store manages a catalog, stock, orders and customers over time. If you sell several products and repeat the same purchase path, a store saves work. If you have one product and no real inventory, a focused page can be enough at the start.

Do you have to redesign the whole site to add WooCommerce?

Not always. If the site already runs on WordPress and is built cleanly, you can add a store beside existing pages. If the site is old, slow or fragile, it is often better to plan the store as part of a proper upgrade than as a plugin on a shaky base.

What happens to orders and customers if you switch platforms later?

You only move the data if you planned for it: products, customers, orders and addresses. Without a clean export and field mapping, some history stays behind. When you choose WooCommerce or any other platform, ask on day one how you export the data on the day you need to leave.