Launch a small WooCommerce shop with a limited, accurate catalogue and a complete order rehearsal before opening checkout to customers. A finished homepage does not prove that the right colour is in stock, payment has been confirmed or the person packing orders knows what to send.
For a Formby or Freshfield shop adding online sales, start with the range you can keep accurate alongside counter sales. Build one representative product, carry it through a controlled test order, and use the result to settle the catalogue, delivery and staff workflow. Add the rest of the range after that route works.
If the platform is still undecided, use our Shopify versus WooCommerce decision test. This plan assumes you have chosen WooCommerce and need to turn that choice into a shop people can use.
Choose a launch range you can actually run
Count sellable combinations as well as product pages. Ten designs offered in four sizes and three colours can mean 120 separate stock positions. Some combinations may not exist; others may share the same physical supply. Write that down before a developer generates every possible variation.
A smaller first range reduces the work of preparing descriptions, checking photographs and maintaining availability. It can also expose gaps early: the supplier may not provide a reliable stock feed, staff may sell the last item over the counter, or a fragile product may need a different packing and delivery route.
Choose representative products for the build: a simple item, an item with the most awkward options, one that has run out, and one with different fulfilment needs. A shop that passes only the easiest sample has not rehearsed its ordinary work.
| Launch question | Record before building |
|---|---|
| What can customers buy? | Named range, real variants, included items and unavailable combinations |
| How much is available? | Stock source, counter-sales update process and backorder decision |
| How does it reach them? | Delivery/collection rules, packing owner and ready-to-collect message |
| Who deals with exceptions? | Named person for payment problems, returns, stock mistakes and enquiries |
| What ends the launch hold? | Recorded acceptance checks and owner approval |
Build the catalogue record before the product page
Keep a master product record with a stable internal identifier, customer-facing name, description, price, stock basis, options, dimensions where useful and image filenames. Distinguish a supplier’s code from your shop SKU; changing a title should not create a new stock identity.
Use descriptions to answer buying questions: what arrives, who it suits, the size or fit, care instructions where supported, and any meaningful restriction. A mug photo with a spoon and gift box can imply a bundle even when neither is supplied. Resolve that in the photo and copy instead of relying on a note buried below checkout.
Our phone product photography guide covers repeatable views and image preparation. Keep full-resolution originals separate from web copies and record image permission. Never generate a replacement product photograph that misrepresents what the buyer receives.
For a range with options, work through the WooCommerce variation planning guide. For a spreadsheet or supplier file, follow the safe product CSV import workflow before loading the whole catalogue. A small sample is easier to reconcile than several hundred wrong prices.
Agree the buying promise before configuring it
The shop owner should approve the customer prices, tax treatment, fulfilment areas, collection instructions and policies. Ask the accountant to settle the tax decisions that apply to the business; a plugin setting cannot decide them for you.
Use the collection and shipping planning guide for address boundaries and mixed baskets. A local collection option needs a real location and an operational message: whether the order is ready immediately or the buyer must wait for confirmation.
The government’s online selling guidance lists information and ordering requirements to review. Prepare business-specific delivery, cancellation, returns and privacy information, then check where customers see it and what they receive after ordering. Do not copy another shop’s policies and assume they fit your products.
Buy hosting for a trading workflow
A small shop needs more than storage for product photos. Ask how the host handles uncached checkout requests, staging, backups, incident support and the live order data created during a restore or migration.
Krystal’s managed WordPress plans are one option to compare. Its current service page describes staging, backups and WordPress management. Obtain a plan-specific answer for your WooCommerce plugins and workload; neither the word managed nor a visitor allowance proves your checkout will meet its needs.
Use the small-shop WooCommerce hosting checklist to compare quotes on the same basis. Include business email, paid plugin renewals and the person who checks trading after updates. Keep hosting support and shop operation as separate named responsibilities.
Keep the first build small enough to inspect
Start with a maintained theme and only the extensions required by the written order workflow. Every additional dependency brings another renewal, compatibility question and support boundary. Wishlists, loyalty schemes and elaborate filters can wait if customers cannot yet buy the correct item.
Record the checkout type and verify that payment, delivery and other required extensions support it. A plugin demonstration on a different theme or checkout is not evidence of compatibility on your installation. Build and test the difficult product and basket early, before spending the budget on decorative changes.
Check the product journey on a phone while logged out: find a category, open a product, identify the selected option, read delivery information and reach checkout. Use the first-pass accessibility check for navigation and form usability.
Rehearse the order at both ends
Use a controlled staging environment with the payment provider’s supported test mode. Test notifications and integrations must reach agreed test destinations; a cloned shop must not send a fake order to a warehouse or accounting system.
Follow the checkout and order rehearsal from product selection to payment evidence, stock movement, confirmation, picking and the cancellation/refund route. Record expected and actual results. A thank-you page is only one observation; the gateway record and shop order must agree.
Give the person who will run the shop a test order to process. Can they tell navy from black, find the right stock item, recognise a payment awaiting confirmation and send the agreed collection message? Fix any missing information in the workflow and product data before opening sales.
A launch sequence with clear stop points
- Catalogue accepted: representative products have checked prices, images, options and availability.
- Trading rules accepted: tax, delivery, collection and customer information match owner-approved decisions.
- Test order accepted: checkout, payment evidence, stock, messages and fulfilment agree.
- Recovery accepted: a backup and recovery route exist, with responsibility for new orders during a rollback.
- Handover accepted: staff can operate the store and reach the support contacts.
- Live configuration checked: test payment settings, staging endpoints and temporary content are absent from the public shop.
Use the website handover checklist for account ownership and sign-off records. A date on the launch plan should not override an unresolved payment, stock or delivery failure.
Plan the first week as shop work
Assign somebody to check incoming orders and customer messages at the intervals your service promise needs. Inspect the first orders against the payment provider’s records and physical stock; record exceptions rather than quietly correcting them without finding the cause.
If you also sell in person, decide which system owns availability and how quickly counter sales reach the website. A manual process may suit a modest range, but it needs a named owner and a rule for the last item. A stock integration should be tested with refunds and corrections as well as successful sales.
Keep the website continuity plan outside the store so the account and fallback contact details remain available during an outage.
For a Formby, Freshfield or L37 shop-build brief, send the launch range, approximate variation count, existing stock system and delivery/collection rules through our contact page. Include one awkward product and one awkward order; they are more useful for scoping than a favourite theme demo.
