Decide what the first version needs to sell
Start with a manageable catalogue and a clear customer. A hypothetical independent homeware shop might launch with its best-prepared collection rather than uploading every historical item. The important point is that the products are available, accurately described and practical to fulfil.
List the product types and variations. A T-shirt offered in three sizes and two colours needs a way to distinguish those choices. A download needs a reliable delivery route after payment. A personalised item may need customer instructions and a clear approval process. Those differences affect the build and the tests.
Write down what the first version will deliberately leave out. Wholesale pricing, subscriptions, overseas delivery and complicated custom bundles may be valid future needs, but they should not arrive as surprises during launch week.
Build a clean product master
Prepare one agreed source of product information before import. Useful columns include a unique reference or SKU, product name, description, price, category, variation choices, stock approach, weight, dimensions and image filenames. Add product-specific information where the product requires it; do not guess ingredients, suitability or safety details from a photo.
Check duplicate names and references. If your shop and till will share stock, stable references become particularly important. Decide which system is authoritative for price and stock, whether all channels use the same catalogue and what should happen if a connection is delayed.
Images should show what the customer will receive. If a photo includes props or several items, explain the actual quantity being sold. Keep useful consistency in lighting and framing, but do not edit away important packaging, labels or product differences. Confirm permission for supplied photography.
Organise the catalogue around customer questions
Categories should help shoppers choose. Product type, intended use and relevant attributes may be more useful than the supplier’s internal range names. Avoid creating so many filters that a small catalogue becomes harder to browse.
Think through the words a customer might search for. Test a common product name, an alternative description and a misspelling. Check whether out-of-stock products appear, and whether a customer can tell that they cannot currently buy them.
A product page should explain the item, show the relevant choices, display the price and make delivery information easy to find. Long descriptions are only valuable when they answer useful questions. Do not copy the same generic paragraph across every item and assume more text means better SEO.
Agree delivery and fulfilment before checkout is built
Write down the regions you serve, the carriers or collection options you use, and how charges are calculated. Decide how thresholds, heavy parcels, remote areas, mixed baskets and unavailable destinations should work. A postcode at the edge of your coverage is a good test case.
Distinguish dispatch from delivery. If you normally hand parcels to a carrier the next working day, that does not mean every customer receives them the following morning. Publish statements your fulfilment process can support and account for weekends, holidays and exceptions.
Decide who packs orders, where order notifications go and how staff record fulfilment. Include refunds, cancellations, damaged goods and stock corrections in the operating plan. Product and consumer obligations vary; arrange an appropriate review of the actual products, policies and markets before selling.
Treat stock connections as a separate project risk
If you sell online and in a physical shop, do not assume a stock connection is included simply because both tools support integrations. Check the exact products, variants, subscription entitlement, location mapping and direction of updates.
Use a small authorised test catalogue first. Sell or adjust a supported test item through each route and check what changes in the other system. Test a refund, a failed update and a temporary connection failure. Record how staff identify and reconcile a mismatch.
Customer accounts and loyalty balances also need their own migration plan. An email address exported from an old system is not the same thing as a transferable password, available marketing permission or a verified points balance. Keep the original records safe until the new process has been checked.
Rehearse an order before announcing launch
- Open the shop on a phone and find an item through navigation and search.
- Select every relevant option and check unavailable combinations.
- Add and remove quantities, then check the basket totals.
- Test delivery below and above any threshold, including a boundary address.
- Use supported payment test facilities for success, decline and cancellation.
- Confirm which business receives the order and who gets notified.
- Check stock changes once, with no duplicate order or fulfilment action.
- Rehearse fulfilment, refund and the customer’s confirmation emails.
- Check guest checkout and account routes where offered.
- Confirm who can access orders and how staff get support.
A successful payment screen alone does not prove the whole order journey works. Check the order record, stock outcome and operational handover too. Use supported test modes and obtain specific authorisation for any real charge.
Budget for the shop after launch
Vemblo’s physical-product shops start from £1,695, and digital-product shops from £1,595, for their agreed scope. Platform subscriptions, payment processing, domains, paid apps and ongoing support are separate decisions. Catalogue size, migration and stock connections can change the work required.
Before launch, make sure somebody can add a product, amend stock, fulfil an order and find the customer’s details. Agree what happens when something fails and which work sits with the platform, the shop owner or the developer. Then plan how customers will discover the shop: existing customers, relevant content, partnerships and paid promotion are different channels to evaluate.
Start with a store you can operate reliably and improve it using real customer questions and order data. Our cost guide explains how to separate the initial build from ongoing services.
Further reading
External references checked on 1 November 2026. Provider guidance may change.