Online store analysis
in Basel

Widmer & Kunz is based in Basel; by arrangement, we can discuss the findings in person or online. We start with your actual processes, not a blanket proposal to build a new shop. Which language do your customers need, which goods are collected, which are dispatched, and who answers queries? An online store analysis brings these questions together with the visible purchase journey. We document observations, flag missing evidence and prioritise possible changes. Creating a new online store is a separate service; any subsequent improvements are also agreed separately.

Before assessing individual buttons, we jointly establish what your existing shop should achieve. A regional shop that also offers delivery faces different questions from a multilingual catalogue serving customers further afield. We record important product groups, known customer queries and the routes visitors take to reach the shop. In doing so, we distinguish assumptions from evidenced problems: a page that subjectively feels confusing is not yet a proven reason for abandonment. Your chosen objectives determine which views are examined first and which existing data is needed. The selection of examples contrasts different approaches to checking a shop without opening your shop, giving an assessment or pre - empting an individual analysis.

German, English and French can provide different starting points for an offering near the border. We compare not only the product name, but also delivery information, variants, categories and customer queries across the language versions actually available. Translating the main text is not enough if the basket then displays only one language. Technical terms and product characteristics must be confirmed by your company; missing translations are not invented. Using the selected sample product, we record where meaning, availability or usability differ. Which multilingual features your system supports, and whether additional extensions would be needed, must still be checked before implementation. In the local product check, example gaps are visibly filled in.

Someone who visits your company website first brings different expectations from someone who lands directly on a product page. In Basel, we therefore check the transition between information and purchasing: is it clear when visitors leave the website, where the product range begins and how to find the contact information again? Colours alone do not create coherence. Terms, navigation and the tone of notices should also be consistent. An illustrated comparison view shows how an unclear product section could be made easier to understand. It is not a client project or evidence of sales success. Existing content and addresses remain unchanged during the analysis; changes to both sites require an agreed brief.

The way a Basel business organises items internally does not necessarily match how its customers search. We examine whether categories express a need, whether the same products appear more than once without explanation, and whether filters match the available attributes. Particularly when several languages are involved, seemingly identical categories can have different meanings. Sold - out items must not appear available to buy without any indication to the contrary; on the other hand, an informative product page can still be useful. Groups and availability can be changed in the example overview. The visible organisation is a local demonstration. A recommendation for your shop can only be developed from confirmed product data, actual usage and the limitations of the existing system.

A size or version may seem self - explanatory in a physical shop yet still prompt questions online. We compare variant names with images, stock information and the contents of the basket. For customers near the border, it also matters whether the same variant is offered in their chosen delivery area. A general availability message can conceal these differences. Any discrepancies found are documented against the affected product and discussed with your team. We do not change any stock levels or make any delivery promises in the process. Whether variant - specific information is technically supported depends on the platform and its configuration. The first step is to clarify which details are reliably maintained and who confirms their factual accuracy.

If a shop offers both collection and delivery, customers should not only find out at the final step. We look at which delivery details appear in the basket and whether quantities, versions and subtotals are clear. A visible next step must not be displaced by advertising or additional offers. The example view deliberately contains missing information that can be added step by step. This does not imply anything about your actual shop. To make a genuine recommendation, we compare the basket with your confirmed delivery processes and the queries handled by your team. Unexpected costs are recorded as an observation, not replaced with invented amounts.

The Basel analysis examines the journey from the basket through contact details, delivery method and address to payment selection and the order summary. We ask which details are genuinely needed and where an explanation is missing. An excessively long journey is not automatically wrong; individual fields may be necessary for operational processes. We document the reason for them rather than removing them indiscriminately. The demo works exclusively with local steps and does not collect any personal details. A real test order is not included in the analysis without explicit agreement. Whether it is necessary, permitted and useful, and under what conditions, must be agreed with you separately.

Cards, TWINT or payment by invoice are possible areas to examine, not promised integrations. We check the existing shop to see whether the payment methods offered are explained and whether customers become aware of restrictions in good time. The company's location, the country, provider and plan can affect availability. For visitors from Germany or France, we distinguish between language, delivery area and payment requirements rather than treating these topics as interchangeable. No payment details are requested and no providers are connected. The example combination of delivery and payment highlights open questions. Before any change is made, a technical anomaly is assessed using the official system information and your existing contracts. Tax and legal questions are answered by a qualified professional.

A company's registered location is not automatically a collection point. We therefore ask about confirmed locations, information on when goods are ready, and responsibilities if your shop offers collection. The analysis focuses on whether these details can be found before purchase and remain clear after the option is selected. We invent neither collection points nor opening hours. Delivery throughout Switzerland is examined alongside this: which products can be delivered, what information is missing, and when do customers learn about restrictions? Observations from the two routes are documented separately. A possible improvement might be an earlier notice, but could also be a clearer internal handover between order processing and preparing goods for collection.

A shop can look well organised on a large screen yet lose important information on a phone. For Basel, we compare product copy, images, variant selection and collection information in small - screen views. We check whether fixed elements obscure the purchase button and whether filters can be closed again after a selection. The device view in the demo changes only its own width; it does not load a real shop. In an agreed analysis, we select real views and clearly defined tasks. What matters is not an attractive screenshot, but whether customers can read information, correct decisions and reach the next step without an unexpected jump.

Images for multiple languages, additional shop features and integrated services can affect loading behaviour. We record noticeable delays and distinguish them from problems with individual devices or connections. Image size, scripts, font files, animations and external extensions are considered as possible causes, not blamed without measurement. The domain and encrypted connection also form part of the technical assessment. The local speed view uses example data only and does not scan any website. A reliable finding requires an agreed scope of measurement and repeatable conditions. The analysis is not a comprehensive security review; anomalies may require a separate technical or specialist assignment.

In a multilingual Basel shop, we compare product names, descriptions, page titles and image descriptions with the visible information. Categories and internal links must connect different purchase intentions in a way that makes sense. Technical indexability, duplicate content, redirects and unavailable products are possible additional areas to examine. SEO concerns traditional organic search results; GEO concerns clear and verifiable content for generative search systems. Both differ from paid Google Ads and Meta Ads. An analysis guarantees neither rankings nor mentions or source citations. Our recommendations identify the area observed and the evidence missing for it before technical changes or copywriting work are commissioned.

A visitor count alone does not explain whether someone is looking for a local offering or wants to order for delivery within Switzerland. We examine existing reports by origin, device category and purchase journey, insofar as the data has been collected lawfully and is meaningful. Missing consent or incomplete events can distort results. An observed decline must therefore not be presented as an obstacle to purchasing without context. Personal form data does not belong in analytics services. A suitable summary containing no personal data is often sufficient for the discussion. We connect figures with specific observations about pages and make clear which questions remain open, rather than inventing supposedly precise figures for your business.

At an in - person appointment in Basel, your team can show how product copy, languages and delivery information are currently maintained. We look at roles, access and coordination between order processing and content maintenance. A recurring error may stem from unclear responsibilities rather than the shop's design. The analysis therefore also covers training needs and the clarity of existing instructions. Passwords are never requested publicly or in ordinary enquiry fields. If access is needed, we agree on a suitable secure method and the minimum scope required. The handover of the findings should enable staff to understand the observations and take internal responsibility for planned steps.

The assessment connects observation, significance and recommendation. A missing collection notice may be more urgent than a new image style if it leaves the selected delivery method unclear. We consider impact, effort, urgency, dependencies and technical risk. The assessment remains a reasoned prioritisation, not an automatic revenue forecast. The matrix contains example measures that can be assigned to different fields. For your shop, the affected language versions, available data and responsibilities would also need to be specified. Initially, a measure may simply identify a need for clarification. The in - person discussion serves to align the order of priorities with your operational capabilities before implementation is offered.

The analysis is suitable for companies with an existing online store that want to understand its purchase journey, content or maintenance better. Building a new shop falls under online store creation; prioritised changes fall under online store improvement. We separate these services so that an investigation does not automatically lead to a change of system. Existing customisations, product data and addresses can be valuable and must be protected during any later migration. Legal texts, prices, taxes and mandatory information remain the responsibility of your company or a qualified professional. The investigation does not replace legal advice, tax advice or a security review. Unresolved specialist questions are explicitly marked as open rather than concealed behind statements that merely sound certain.

Discount codes, vouchers, product bundles and recurring subscriptions can work differently in a multilingual shop. We examine the existing offering to see whether a promotion is explained in all language versions, whether a voucher is applied to the basket as expected, and whether a bundle remains clearly understandable compared with individual products. Product images are also part of the check: does the image match the selected variant, and does the display remain readable on a phone? Which of these features your system and plan support must be clarified using the official system information before a recommendation is made. We invent neither terms nor example prices and do not place a real order. Any discrepancies found are documented with evidence and discussed with you before they lead to a measure being taken.