Shopify online store
created for you across Aargau
A business serving several areas in Aargau does not necessarily need several separate shops. A shared Shopify online shop can combine central products with genuinely different collection and delivery information. We plan the relationship between regional entry points and a consistent product range so that prices and product information are not maintained in several places without coordination. Aargau is the cantonal page here; Aarau, Baden and Rheinfelden appear as example areas, not as claimed business locations. Widmer & Kunz supports the collaboration from Basel, digitally and with in - person appointments by arrangement.

A shared catalogue for actual service areas
Shopify can provide a shared foundation when central product management and regional handover arrangements work together. First, it must be clarified whether the differences concern content, inventory, delivery or responsibilities. A location selector alone does not constitute a genuine area eligibility check or an access restriction. Special regional rules are checked against the existing plan and any app that may be required.
One Shopify online shop for several regions
Several regional target groups need a shared core of product and business information. We define which product details apply everywhere and which information genuinely differs. The region selector in the example shows Aarau, Baden or Rheinfelden and adds the local information. This does not imply any promise of collection points or delivery coverage throughout the area.
Shopify Markets is not treated as equivalent to a location selector within a canton. International markets and local delivery areas serve different purposes. For a real shop in Aargau, the desired logic is described first and only then assessed in technical terms. To be checked before implementation.
Interactive Shopify example
Drei Beispielgebiete, ein gemeinsamer Shopify Produktkern
Illustrative structure · no real orders or business figures
- 01
Aarau · Example
- 02
Baden · Example
- 03
Rheinfelden · Example
- 04
Zentrale Produkte
- 05
Collection and shipping
- 06
Responsibility
- 07
Shared order overview
Produkte zentral verwalten
Product descriptions, variants and prices should be maintained by those responsible for them. If the same bag appears in several regional views, it does not need three independent data records. We distinguish a central catalogue from additional regional information and document the effects of a change.
The local example changes a central product title and immediately displays it in several area views. It does not update any Shopify products. Subsequent implementation depends on the theme, data model and desired display. A central change must not overwrite differing stock levels or operational information unnoticed.
Interactive Shopify example
Collection and shipping by area
Before setting anything up, we record the business’s actual handover locations and delivery terms. A cantonal page must not invent additional branches. Customers need clear information on whether a selected area is served by shipping or offers a confirmed collection option. Responsibilities and readiness form part of the process.
The demo links an area selection with collection or standard shipping. Free shipping above a certain amount is expressly a demo value. Complex postcode rules, inventory across multiple locations and bespoke delivery logic must be checked before implementation; they do not work automatically without an app or an additional solution.
Interactive Shopify example
Passende Shoparten across Aargau
Illustrative uses · not client references
- Regional retail across several areas
- Central accessories range
- Business with confirmed collection arrangements
- Shipping service with area rules
- Zielgruppenspezifische Produktpakete
- Schrittweise wachsender kantonaler Katalog
Regional entry points and shared products
A regional entry point only provides information of its own value if its details are genuinely relevant. We combine central products with substantiated regional information rather than duplicating the same shop text under many place names. A canton represents a different level from a city.
In the example view, the additional information for the generic product changes according to the selected area. For a real Shopify shop, the technical presentation and responsibility for maintenance are aligned. Market - specific theme adjustments may require particular plans; local additional information is not advertised across the board as an identical standard function.
Interactive Shopify example
Orders and responsibilities
When several teams or functions handle an order, the allocation must be traceable. We gather the information that is actually needed for this and distinguish an operational area of responsibility from a supposed regional office. Additional forwarding and external systems require a specific technical and data protection assessment.
The local model assigns a sample order to a fictional area of responsibility according to the area and handover method. It does not send a message, create an order or change any user role. Shopify permissions must not be presented across the board as area - based restrictions on individual products or orders. To be checked before implementation.
Interactive Shopify example
Product bundles for different target groups
A bundle might, for example, offer a small starter selection or a more comprehensive set of equipment. The decision starts with actual needs, not with the largest possible number of items that can be combined. We check stock, variants, the desired pricing logic and how returns are handled.
The local bundle selector combines generic products according to the target group and changes a purely illustrative demo price. Shopify Bundles and freely customisable bundles have different requirements. The plan, app and compatibility are checked in advance. Any desired recurring purchase also requires a suitable subscription solution and a supported payment method.
Interactive Shopify example
Shopify schrittweise erweitern
A shared initial catalogue can later gain further area views or confirmed collection options. We plan these stages so that central information can continue to be maintained clearly. Additional requests are not implemented immediately simply because an app is available. Every connection creates operational and monitoring tasks.
For a Shopify shop for businesses in Aargau, we consider product management, orders and regional content together. External interfaces and bespoke functions are separate points for assessment. A general website without a purchasing purpose remains a separate service, not an additional regional Shopify website page.
Bestehenden Shop analysieren
Where several views already exist, we check whether information is contradictory and where the shared product core is being lost. Which data is maintained in duplicate, which delivery information is unclear and which areas of responsibility respond to enquiries? The analysis is based on confirmed observations and agreed access.
The review view highlights local example tasks and does not measure real sales. Old URLs remain untouched until approval is given at a later stage. An existing Shopify online shop in Aargau can be improved in a targeted way; a migration or comprehensive restructuring is recommended only following its own separately scoped assessment.
Interactive Shopify example
Payment, taxes and shipping areas
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; for a cantonal shop, this means confirmed areas rather than blanket promises. We configure tax information only on the basis of confirmed customer instructions and the 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 do not make blanket legal statements.
Product integration with centralised maintenance
Products are integrated to the agreed extent. 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 assess extensive imports and data cleansing in advance.
Customer product data is not automatically invented or supplemented. We separate central information from additional regional notes at the data collection stage so that subsequent changes remain controlled.
Categories and bundles for several areas
Clear categories, collections, filters and variants apply to all areas in the shared catalogue. Complementary products, product bundles, promotions, vouchers and discount codes can be tailored to target groups. We identify functions that depend on the Shopify plan, an app or the specific configuration as requiring checks in advance.
We assess regional package ideas for stock availability, pricing logic and maintenance effort. Not every desired combination can be implemented without an additional solution.
Handover with clear responsibilities
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.
Where several areas are involved, we focus particularly on practising who changes central data and who maintains regional information. We document responsibilities in writing; any further support is agreed separately.
Which shop setup supports your areas
A One Product Store focuses on a single main product, with a product page, basket, payment, shipping, domain, contact information and possible marketing integrations. A Niche Store covers a manageable product range with categories, product variants, product packages, discounts, statistics and product maintenance. A comprehensive online store provides a larger range with clear categorisation, filters, variants, product data, shipping logic and structured administration.
We determine the appropriate shop size based on the product range, variants, data quality, functions and maintenance effort; for regional structures, who maintains which data also matters. No fixed product counts and no prices: the selection is a guide, not an automatic quotation.
Interactive Shopify example
Design aligned with your corporate visual identity
The shop should fit your brand rather than look like an unmodified standard template. We align colours, fonts, imagery, page structure, product presentation, navigation, basket and mobile display with your corporate design, consistently across all area views.
The local demo changes the colour, font appearance, card style and product presentation of a sample card. Additional regional information remains unaffected; we check implementation in the chosen theme before building begins.
Interactive Shopify example
Domain and shop name
We connect an existing domain to the shop or set up a new one by agreement. The individual shop name applies centrally; the platform used provides the encrypted connection. A cantonal focus comes from content, not from special domain technology.
Business email is a separate additional service. We coordinate the timing of the domain changeover and shop launch.
Suchmaschinen Grundlagen
Possible services include clear page titles, meta descriptions, product names, product descriptions, image descriptions, image optimisation, categories, internal links and technical indexability. Regional entry pages provide genuine informational value rather than copied lists of places. We do not promise a particular position on Google.
For more extensive work, we refer you to SEO and GEO optimisation. Suitable measures depend on the product range, areas and existing content.
Marketing and tracking as an extension
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.
We assess regional campaigns for their actual benefit to the areas being promoted. We clarify purpose, compatibility and data processing before connecting them.
Legal content
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 created in a legally compliant form. Templates are no substitute for a professional review.
Laufende Kosten
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. For a growing cantonal catalogue, we discuss ongoing costs and maintenance effort together.
Shopify features with clear prerequisites
Not every feature is included as standard. The plan, app, payment provider, region and existing technical setup will be checked for your project. Official feature information: checked on 3 November 2026.
- Products and variants
- Product data, images and permitted combinations are agreed before the build.
- Collections and filters
- Groups and attributes need a suitable theme and clearly structured data. To be checked before implementation.
- Product bundles
- Fixed bundles and multipacks differ from freely configurable combinations. App and compatibility: to be checked before implementation.Offizielle Shopify Anleitung
- Subscriptions
- A subscription app and a supported recurring payment method are required. To be checked before implementation.Offizielle Shopify Anleitung
- Discounts and vouchers
- Validity, compatibility with other offers and conditions of use are defined to suit the business.
- Shopping cart and checkout
- Branding does not mean complete design freedom at every step. Extensions may require Shopify Plus. To be checked before implementation.Offizielle Shopify Anleitung
- Zahlungen in der Schweiz
- Visa, Mastercard, American Express, Maestro and UnionPay are documented, as are Apple Pay, Google Pay and Shop Pay. TWINT must be activated. Customer region and requirements: to be checked before implementation.Offizielle Shopify Anleitung
- Shipping and pickup
- Destination areas, rates, inventory and confirmed locations determine the process. Custom logic: to be checked before implementation.Offizielle Shopify Anleitung
- Orders and accounts
- Account models and app connections differ. No actual access is created in our examples. To be checked before implementation.Offizielle Shopify Anleitung
- Markets and currencies
- Multiple customer currencies require suitable payment processing. Market-specific prices and theme adjustments may depend on the plan. To be checked before implementation.Offizielle Shopify Anleitung
- Multilingualism
- The theme, language selector and maintained translations must work together. To be checked before implementation.Offizielle Shopify Anleitung
- Statistiken
- Shopify documents analytics and reports; specific data access and the available functionality are checked in the account. No example sales figures.Offizielle Shopify Anleitung
- SEO, domain and SSL
- Titles, content and the domain connection are planned. SSL provides neither legal certainty nor a ranking guarantee.Offizielle Shopify Anleitung
- Apps and marketing
- Additional services may incur fees and involve data processing. Compatibility and consent: to be checked before implementation.Offizielle Shopify Anleitung
- Benutzerrechte
- The plan and tasks determine access. Permissions do not provide a blanket way to block individual products or orders. To be checked before implementation.Offizielle Shopify Anleitung
A central core with justified regional additions
- Central product details remain separate from additional regional information.
- A cantonal overview can explain several actual delivery areas.
- Collection and shipping are planned alongside operational responsibilities.
- Regionale Einstiege erhalten Informationswert statt kopierter Ortslisten.
- New areas and package ideas can be assessed as separate expansion steps.
Special regional logic requires a specific assessment
A central Shopify shop does not automatically handle special regional rules. Delivery areas, inventory and allocation may require apps or additional development. Shopify Markets is not the same as a local location selector. Ongoing platform and app costs still need to be planned for. User permissions do not provide a guaranteed block on individual orders from particular areas. Subscriptions, freely configurable packages and interfaces are checked in advance; legal content and product material are based on confirmed specifications. Sales or rankings are not guaranteed.
Eight steps for your Shopify shop across Aargau
- 01
Define areas and operations
We record your actual coverage without claiming new locations.
- 02
Gemeinsamen Katalog erfassen
Central data is separated from additional regional information.
- 03
Plan handover arrangements
Collection, shipping and internal areas of responsibility are confirmed.
- 04
Gebietsansichten entwerfen
You compare a cantonal entry page with specific local information.
- 05
Shopkern umsetzen
Shopify and previously checked additions form the shared product foundation.
- 06
Zuordnungen kontrollieren
Product changes, delivery information and order routes are tested together.
- 07
Kantonalen Aufbau freigeben
Outstanding inconsistencies are corrected and your explicit approval is obtained.
- 08
Practise central maintenance
Your team learns to edit shared data and regional additions in a targeted way.
Understand regional differences in the existing setup
To assess your current setup, we compare the same products in the existing views. If prices or information differ without a valid business reason, responsibility for the data is clarified first. Targeted data clean - up may be worthwhile before a larger technical expansion.
Coordinate Aargau delivery areas and the shop's core setupSeparate central products from regional operational information
We gather the shared catalogue alongside confirmed regional information on collection, delivery and processing. Area names are not evidence of business locations. A sample product is checked in all intended views before extensive data or additional area logic is incorporated.
Agree payment and delivery arrangements before the project begins
Before setting anything up, we record the business’s actual handover locations and delivery terms. A cantonal page must not invent additional branches. Customers need clear information on whether a selected area is served by shipping or offers a confirmed collection option. Responsibilities and readiness form part of the process. Shopify Payments lists Switzerland as a supported country. TWINT and other payment methods require appropriate activation and prerequisites. Check availability and terms before the project begins.
Swiss payment methods on ShopifyCheck central changes and regional information
During the handover, your team changes a central product and checks the effects in several views. Regional information and order allocation are then discussed. Technical access, legal responsibility and additional support remain separately agreed tasks.
Ihre Fragen zum Shopify online store across Aargau
Does a company in Aargau need a shop for every town?
Not necessarily. A shared catalogue can incorporate regional information if the actual differences are clearly planned and technically checked.
Are Aarau, Baden and Rheinfelden your collection locations?
No. They appear as example areas. Widmer & Kunz is based in Basel; actual handover locations come from confirmed information supplied by your company.
Ist Shopify Markets eine Postleitzahlsteuerung im Aargau?
Not automatically. International markets and local delivery logic are considered separately. The specific area rule must be checked before implementation.
Can a product change reach several views?
A central core of product data can be displayed accordingly. The example only shows local changes; the data model and theme output are checked in the actual build.
Who receives an order from a particular area?
You define the operational area of responsibility. Actual automation and suitable interfaces are assessed separately. The demo does not send anything.
Can a regional package be put together freely?
The demo allows you to put one together locally. Actual freely configurable packages may require an additional app or development and are not a guaranteed part of the standard scope.
Is free shipping offered in the example?
Only as a demo value, not as a business term. Your actual costs, areas and thresholds are confirmed before setup.
Welche laufende Pflege braucht ein gemeinsamer Katalog?
Central product data and regional information must remain under control. We provide training on the agreed tasks; platform costs, app costs and further support are discussed separately.