WooCommerce store setup: products, checkout and records

Set up WooCommerce from a supported installation through products, theme settings, checkout and the order records needed to fulfil a retail purchase.

WooCommerce store setup is complete when a customer can choose the right product, pay through checkout and receive order details that match your records. Start with an installed store, configure one checkable product and follow its purchase through payment and fulfilment before expanding the catalogue.

WooCommerce adds ecommerce to WordPress. The procedure below covers merchant settings and verification on an existing installation, using a supported block theme and the Checkout block. Hosting selection and custom theme development are separate jobs.

Confirm the supported store and business settings

Record the installed WordPress, WooCommerce and theme versions before changing the store. You need access to store settings, products and orders, plus an administrator who can manage extensions and theme settings.

  1. Open WooCommerce > Status and record the system report, active theme and extensions. Compare their installed versions with each provider’s supported requirements. Resolve a compatibility warning before building the buying flow around that extension.
  2. Prepare an isolated test store with fictional customers. Route its emails to test inboxes and disconnect live fulfilment and accounting exports. A test payment can still create an order and trigger notifications.
  3. In WordPress Settings > General, set the site title, language and timezone. Choose an unambiguous date convention for customer documents. WordPress provides date and time settings, but an extension can apply its own format. See the WordPress general settings.
  4. Open WooCommerce > Settings > General. Enter the store address, selling countries, shipping locations and store currency. Under Products, choose the measurement units that your catalogue uses. The WooCommerce settings guide identifies the owner of each setting.

Configure tax from your business’s confirmed treatment for its products and destinations. Enabling a tax setting does not establish registration or a tax obligation. WooCommerce’s tax documentation distinguishes software configuration from deciding what your business must charge.

For the fictional example below, assume the retailer has confirmed a 10% tax treatment for the goods and shipping. Prices include that tax. This is a calculation assumption for the example, not a rule for every Australian purchase.

Build a checkable product catalogue

Build one variable product whose displayed choices match its stock records. A variation is a separately purchasable version, with its own price or stock. An add-on records an extra choice, such as gift wrapping. Account fields describe the customer and belong in registration or checkout.

  1. Go to Products > Add New and create a fictional cotton napkin. Select Variable product in Product data. Give the parent a stock-keeping unit (SKU), such as SCN, and describe its material and care requirements.
  2. Add a Colour attribute with Navy and Oat as its values. Mark it for variations and create the two variations. WooCommerce’s variable-product instructions explain the attribute and variation controls.
  3. Give Navy the SKU SCN-NAVY, a $22 tax-inclusive price and three units in stock. Set Oat to SKU SCN-OAT with zero stock. Disable backorders for this exercise. Choose variation-level stock management so each colour has its own count.
  4. Upload a photograph for each colour and check that the selected variation displays the matching image. State the napkin’s 45 cm by 45 cm finished size in the description. Enter its measured packed weight and dimensions in the shipping fields, using your configured units.
  5. Save and open the product page on a phone and a desktop. Select each colour. Confirm its price and availability, then compare the basket line with the selected variation.

A required colour choice must prevent an ambiguous purchase. For this exercise, leave the default variation unset so you can check the missing-selection behaviour. If you later choose a default, make that choice visible to the customer.

Gift wrapping needs a supported add-on method if you sell it. A customer registration field is a poor place to store a purchase-specific wrapping request. Keep option labels beside the product choice and confirm that the saved order retains the answer. The WooCommerce product add-ons guide covers that separate configuration task.

Use the block theme’s supported editor controls for presentation. In Appearance > Editor, inspect the Product Catalog template and the Single Product template. Keep the product choice and add-to-cart control visible together. WooCommerce’s store editing documentation separates block-theme editing from classic-theme customisation.

Configure checkout and customer documents

Configure payment and shipping around the countries you actually serve. A method enabled in settings still needs to appear for an eligible customer in the rendered checkout.

  1. Open WooCommerce > Settings > Shipping and add your shipping zones. Put a narrow postcode zone ahead of a broader country zone. Customers match the first applicable zone and see its methods. Add the method and its charge inside that zone, following the shipping-zone procedure.
  2. Under Accounts & Privacy, choose whether customers can buy as guests and where they can create an account. Test a guest purchase and an existing customer’s login separately. Collect extra registration data only when your process needs it.
  3. Select a payment gateway that supports your merchant country and Checkout block. For a store using WooPayments, go to Payments > Settings and enable test mode on the isolated store. Save it and confirm the mode before entering any test payment details.
  4. Open the assigned Checkout page in the block editor. The Payment Options block identifies incompatible integrations. After adding a Checkout block, assign that page under WooCommerce > Settings > Advanced. Follow the Checkout block settings.
  5. Under Emails, enable the intended order notifications and set the sender identity. Check customer-facing processing, completed and refunded messages separately from the merchant’s New order alert. Use the order fields for quantities and totals, with wording that matches the event.

For the example purchase, configure two napkins at $22 each and shipping at $11. The expected total is $55, including $5 tax under the stated assumption. Any discount changes this example and needs its own expected total.

Multi-currency requires a supported payment setup. With WooPayments, its multi-currency controls let customers choose an enabled purchase currency. Enable the feature under Payments > Settings > Advanced settings, then manage currencies in WooCommerce settings. Confirm the basket, checkout and saved order all use the intended currency. The customer’s purchase currency and your payout currency are separate.

Choose your invoice or packing-slip method explicitly. An order notification does not establish that a PDF extension is installed or that a tax invoice contains the required business details. Compare any generated document with the saved order, including its currency and payment state. Full numbering and attachment setup belongs in the WooCommerce invoice guide.

Complete and recover the buying task

Run one fictional purchase through the isolated store and compare every resulting record. Use the gateway’s documented success and failure inputs. WooPayments testing creates test orders without moving real funds.

Purchase and missing option

  1. Open the napkin page with no colour selected. Attempt to add it to the basket. Expect a request to choose an option, with no ambiguous product added.
  2. Select Navy and buy two units using the successful test payment. Expect SCN-NAVY, quantity two and the $55 total in the saved order. Under the chosen stock setup, one Navy unit remains.
  3. Compare the order number and currency across the customer’s confirmation page, received email and merchant order. Check the shipping destination and selected service. Confirm that any document uses the same quantities and totals.

Failed payment

Repeat with the gateway’s documented declined-payment input. WooPayments documents a generic-decline test card ending in 0002. Expect a failure message and no successful charge. Inspect the order notes and gateway test transaction before retrying. A failed attempt must not start fulfilment or produce a message saying payment succeeded.

If checkout shows success but the merchant record does not show payment, compare the gateway transaction with the order notes. Capture the order number and error details for the gateway’s support team. Avoid repeated payment attempts until you know whether a charge exists.

Partial fulfilment and refund

Suppose one of the two napkins cannot be supplied. Record one item as dispatched in your chosen fulfilment workflow and tell the customer which item remains unresolved. A whole-order status alone does not explain a split shipment.

From the order’s refund controls, refund the unavailable unit for $22, including its $2 tax under the example’s assumptions. Keep the $11 shipping charge for this scenario. The original order is $55, the refund is $22 and the net amount retained is $33. Compare the refund record and customer message with those figures.

WooCommerce’s refund procedure distinguishes automatic gateway refunds from manual refund records. A manual record needs a separate return of funds. Changing the status to Refunded does not return money. A partial refund also does not automatically make the entire order Refunded.

Decide whether to restock the refunded unit from the physical inventory facts. An unavailable item must not become available merely because you issued a refund.

Before connecting shopping assistance or exporting orders, inspect the saved variation identifiers and destination records. The customer’s chosen colour must survive into the fulfilment record. Payment, refund and dispatch information must describe the same purchase.

Check merchant-facing shortcodes and blocks

Use blocks for the selected block-theme buying flow, and use a shortcode only for a supported legacy placement. A shortcode is a merchant content instruction placed in a page, not a theme-development hook.

  1. For a selected product list, add a Shortcode block to a page and enter [products limit="4" columns="2"]. WooCommerce also supports filtering product shortcodes by categories or SKUs. Preview the actual products and follow the shortcode settings for product lists.
  2. An existing classic cart can use [woocommerce_cart], and a classic checkout can use [woocommerce_checkout]. Place these in a Shortcode block, or directly in Classic Editor content. WooCommerce’s shortcode guide explains those placements.
  3. Keep the Cart and Checkout blocks for this guide’s block-based route. An extension that requires block checkout needs that route. Conversely, a classic-only extension needs a compatible replacement or a deliberately maintained classic flow. Do not mix duplicate cart or checkout implementations on one page.
  4. Open the storefront, add the variation and follow the rendered checkout again after changing a page or template. Check the narrow-screen controls and payment methods. An editor preview cannot prove that the gateway works.

Check ongoing merchant operations

Verify order storage and staff access before treating the first successful checkout as a finished operating setup.

  1. Open WooCommerce > Settings > Advanced > Features and inspect High-Performance Order Storage (HPOS). Review incompatible extensions and any pending synchronisation before changing the storage setting. Follow the HPOS compatibility guidance. Test your invoice and export extensions against the selected storage mode.
  2. Connect the WooCommerce mobile app with an authorised staff account. The iOS setup guide explains its connection requirements. Open the fictional order and compare its status and total with the desktop record. Test the staff permissions and notifications your team needs.
  3. If you use the separate Customer / Order / Coupon Export extension, select only the fictional orders in WooCommerce > Orders. Choose Download to CSV in Bulk actions. Its order export documentation also describes automated sending, which is a separate configuration.
  4. Open the export locally and compare the SKU, quantity, currency and refund values with the saved order. Include only fields the receiving system needs. Keep customer data out of public folders and test remote sending only against an isolated destination.

Repeat the purchase and refund checks after a payment, theme or order-processing extension changes. Release the store when the displayed choice, payment record and fulfilment instructions agree for both the successful purchase and its recovery paths.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup