Shopify online store
created for you in Bern

Before designing, we establish which product families exist and how customers distinguish between them. Categories should help customers find what they need, not mirror your internal departmental structure. A small catalogue can start with a few groups; a large inventory needs reliable attributes and carefully planned maintenance.

In the navigation demo, the example range is organised by use or material. No real Shopify menus are created. The selection shows the different ways a structure can help customers find their way around. For a real Shopify webshop in Bern, terminology and product assignments are agreed with the people responsible.

A product should only appear in several collections if the additional connections are useful. We define which details are maintained centrally and which groups can be created using rules. Duplicate data entry increases the workload and is not introduced merely to create a larger menu.

Shopify supports collections as product groups. The exact filter display depends on product attributes, the theme and the chosen solution. This must be checked before implementation. The maintenance guide subsequently explains the same terms used in the visible shop. This keeps internal editing and the customer view connected.

Variants need clear names, appropriate prices and up - to - date stock information. Additional attributes such as material or care instructions should appear in a logical place. We define a sample product with complete details and check its mobile display before using the structure for further items.

The local data - entry example visibly changes the product title, material and one variant. It does not update real products or stock data. In a customer project, permitted combinations and special data fields are determined separately. Structured information makes subsequent maintenance easier, but does not replace a professional review of product descriptions.

A size guide or care instructions can answer questions before an order is placed. We check which documents may be made publicly available and how customers can tell whether they are up to date. File names alone are often not clear enough. Documents are therefore given an appropriate context alongside the product information.

The demo displays a purely local size guide or care instructions. It does not upload a file or offer a real customer download. Digital products, protected content and automatic delivery may require an additional app. This must be checked before implementation. Image rights and legal approval of the documents remain matters for the customer to specify.

After purchase, order information and clear responsibilities are important. We discuss which details your customers should be able to see themselves and which enquiries will continue to be handled personally. New Shopify customer accounts differ from older account models; desired app connections and changes are reviewed in relation to the specific shop.

The example view switches between an account overview and simplified order statuses. It does not create an account or send a login code. The order shown is a local example with no real order number or customer data. An actual status workflow must match your operational processes.

Customers need clear delivery information before completing their purchase. We record actual shipping methods, destination regions and collection requirements, and review the appropriate settings. Special cases are not brushed aside with an unsupported promise that every set of rules can be implemented without an app. Tax details and legal terms are confirmed by the business.

The local selection links a delivery method to an example payment method and displays the resulting information. For a Swiss Shopify shop, payment requirements and terms are checked. The checkout contains no real payment fields. Availability and terms must be checked before the project begins.

A new product range must also be manageable by the staff responsible. We demonstrate typical steps: checking a title, adding a variant, reviewing a document note and assigning a collection. Not everyone needs access to all technical settings. Plan - dependent user access and permissions are agreed before use.

The local administration demo shows changed product information alongside how it appears in the shop. No data is saved. For your training, we use the actual agreed fields rather than giving a general tour of all Shopify features. Further introductory sessions or ongoing support are planned separately.

For an established Bern shop, we first document product groups and important information. Where are consistent details missing, which documents are out of date, and which routes seem confusing? This produces a clear set of priorities, not a claim about past revenue losses.

Reorganisation may be possible within the existing structure. However, migrations, external data sources and special interfaces require their own review scope. Old product URLs and relevant search engine information are recorded before changes are made. Improving a Shopify online store in Bern therefore starts with understanding what needs to be retained from both a business and a technical perspective.

Products are integrated within the agreed scope. Images, descriptions, prices, variants and other product data must be supplied in full or prepared separately. Variants may relate to size, colour or version, for example. We review extensive imports and data cleansing in advance so that the workload and data quality are clear before work begins.

Customer product data is not automatically invented or supplemented. This is particularly important for a structured product range in Bern: a reviewed sample product with complete details comes before any further data is imported.

Clear categories, collections, filters and variants form the backbone of an organised product range. Complementary products, product bundles, promotions, vouchers and discount codes are added where they serve a genuine shopping occasion. We identify features that depend on the Shopify plan, an app or a specific configuration as requiring review in advance.

We define bundles and promotions in terms of stock, pricing logic and how returns are handled. A freely configurable bundle may require a different solution from a fixed bundle.

Possible services include clear page titles, meta descriptions, well - formed product names and product descriptions, image descriptions, image optimisation, organised categories, internal links and technical indexability. This work starts with the quality of the product range's data. We do not promise a particular position on Google.

For more extensive measures, please see SEO and GEO optimisation. What makes sense for your Bern product range depends on content and competition.

Possible training topics include viewing and processing orders, adding products, editing variants, maintaining categories, updating order statuses, managing discounts, understanding statistics, access and roles, and basic shop administration. Training is tailored to the agreed project scope and uses your actual fields.

We separate product maintenance from technical administration and record responsibilities in writing. Additional sessions or ongoing support are agreed separately.

A one - product shop brings everything together around a single main product: product page, basket, payment, shipping, domain, contact details and possible marketing integrations. A niche shop maintains a manageable range with categories, product variants, product bundles, discounts, statistics and product maintenance. A large online shop organises a wider range with clear categorisation, filters, variants, product data, shipping logic and defined administration processes.

We determine the right shop size based on the product range, variants, data quality, functions and maintenance workload. We do not use fixed product counts or prices; the selection is a guide, not an automatic quotation.

Even a structured shop should reflect the brand rather than look like an unmodified standard template. We align colours, fonts, visual style, page structure, product presentation, navigation, basket and mobile layout with your corporate visual identity. A clear information hierarchy and a strong brand presence are not mutually exclusive.

In the local demo, you can change the colour, typographic feel, card style and product presentation of a sample card. The actual implementation depends on the chosen theme and is checked before the build begins.

We connect an existing domain to the shop; we set up a new domain by agreement. The shop name is chosen individually, and the platform used provides the encrypted connection. As the business, you are responsible for resolving naming and trade mark matters.

Business email is a separate additional service. We coordinate the technical changeover so that existing addresses remain in place and you remain contactable.

We check payment methods against their current availability and your customer account. We set up shipping methods, shipping areas and any collection options according to your requirements. We configure tax information only on the basis of confirmed customer instructions and the platform’s technical capabilities.

Widmer & Kunz does not provide tax advice. You remain responsible for the technical and legal accuracy of your tax and shipping information; we avoid blanket legal statements.

Possible additions include connected advertising accounts, technically prepared tracking, Meta advertising, Google advertising, advertising content, campaign pages, statistics and analysis. We activate tracking only with due regard to consent and the data protection solution in use.

For a data - driven product range, it is worth first asking which analysis should support which decision. We review the purpose and data processing before connecting anything.

We can technically integrate legal pages such as terms and conditions, a privacy policy and a legal notice, and prepare them to the agreed extent. Legal review, completeness and approval are the responsibility of the customer or a suitably qualified professional.

We do not claim that all necessary legal documents are automatically produced in a legally sound form. Documents and templates are no substitute for professional review.

Shopify incurs ongoing platform costs. Apps may incur additional ongoing costs; domains, payment providers and external services may incur further costs. We check current prices and what each plan includes before the project begins.

We do not carry over old prices from existing quotations. We discuss the maintenance workload and platform costs together to keep the shop financially and operationally manageable.