A new WooCommerce store
Catalogue and category structure, key buying journeys, cart and customer account, payment and delivery configuration, sales measurement and order-management training.
Catalogue · Checkout · Integrations
Launch a new store or improve the WooCommerce site you already use. We bring product presentation, mobile shopping and the daily work behind orders into one agreed plan.
WordPress / WooCommerce
Dutch-language learning materials. Archived view.
The starting point
Before choosing functions, we look at your products, buyers, payment and delivery methods, and the way orders are processed. That gives the store a practical starting point and helps identify which integrations need a separate technical review.
Catalogue and category structure, key buying journeys, cart and customer account, payment and delivery configuration, sales measurement and order-management training.
A technical review followed by priorities: mobile layouts, search and filters, new selling functions, integrations, repetitive tasks or a planned cycle of development.
The agreed work
Products, variants and categories, with search, filters and product information suited to the actual range.
The cart, order flow, customer accounts and selected payment and delivery providers, checked against relevant purchase scenarios.
Connections to stock, accounting, ERP or other tools after reviewing APIs, data flows and responsibility for errors.
Data imports where agreed, a trial migration, checks of orders and messages, and preparation for your team’s daily work.
Core store functions, data migration, advanced selling features and system integrations are itemised separately. The proposal also records licences, account ownership and renewal costs. Ongoing support has its own scope.
From conversation to delivery
We review the catalogue, sales markets, payments, deliveries, existing systems and data that must be retained.
We prepare the buying journey, configure the store and develop the integrations and imports included in the scope.
We check variants, cart, delivery, test payments, order statuses and messages before the agreed launch and handover.
Work and context
Explore two WooCommerce projects that connect the story behind the products with a route to purchase.

Travel technology · E-commerce
Our 2025 implementation combined a product website with a WooCommerce store, device variants, accessories and delivery rules. The screenshot shows the later public site as brand context.
Explore the project
Culture · Clothing collection
A brand website and WooCommerce store connecting the initiative, creators and editorial material with clothing sales. The gallery shows an archived version.
Explore the projectBefore we begin
Still have a question? Tell us about your situation.
Ask our teamWe assess the current platform, integrations and a sample of the data before confirming feasibility. Products, customers, orders, content and URLs need their own migration plan, trial import and checks. We confirm the data that can be retained before committing to the scope.
Each integration must be named in the proposal. We define the data, direction of synchronisation and responsibility for errors. Development or configuration costs are separate from fees charged by an external provider.
Yes, after checking the dependencies. The first release must contain the functions needed to fulfil an order. Other features can form a planned development list and be prioritised using information from real sales.
Separate the initial build from hosting, domain renewal, paid licences, external services and any support agreement. The proposal identifies the account owners and renewal responsibilities so the store’s running costs are visible.
We agree the purchase scenarios that matter to your store, such as product variants, delivery options, test payments, order statuses and customer messages. The checks use the configured providers and available test environments. Your team also reviews product data and the operational steps before the agreed release.
Tell us which countries, languages, currencies and delivery providers you need. These affect the catalogue, checkout, account configuration and connected systems. We assess the relevant tools and integrations before estimating. Your advisers supply the applicable commercial, tax and legal requirements; the proposal defines the implementation work.
A typical WooCommerce implementation takes 3–4 weeks after the scope has been agreed and all agreed materials and product data have been supplied. Migration, extensive integrations and additional functions are planned separately. We confirm the timing before work starts, allowing for approvals and purchase testing.
After project settlement, we hand over the agreed access and rights to the materials produced for the project. Third-party tools remain subject to their providers’ terms.
Within the agreed support scope, we create a backup, assess the risk, follow the agreed update procedure and test the key purchase journey.
How your store works
Choose a topic to explore the decisions we make before implementation.
Discuss your store functionsWho can order, who approves catalogue access, and which prices should each customer see? Bring an example order, from an authorised buyer’s sign-in to submission, together with the systems it needs to exchange data with. These help define the roles, access rules and ordering steps for your store.
Agree products, renewal rules, cancellation and customer account information. Recurring payment options depend on the chosen provider and setup; we confirm those requirements before promising a particular flow.
Connect purchase confirmation with access to agreed downloadable products. File preparation, access rules, customer emails and the way your team updates materials are part of the scope.
Work from real product data: attributes, variants, stock, images and identifiers. For a move from another store, we review data mapping, important addresses and test orders before the final switch.
These selling features are planned around the products you offer, their margins and the way orders are fulfilled. They are quoted separately from the core store build.
Order statuses, notifications, documents and connected workflows can form a separate scope to reduce manual handling. We agree the required processes and quote this work separately.
The proposal confirms the selected functions, materials, integrations, licences and checks. Features are agreed for the specific project.
Your next project
Share your current store, the product range and the systems your team uses. We will discuss the buying journey, integrations and the right scope for the next stage.
Discuss your storeWhatsApp · Testin
Planning a website, a store or a change to your existing site? Tell us a little about it. We’ll work out how we can help.
Message on WhatsAppYour conversation opens in the WhatsApp app or website.
+48 882 114 129
With your consent, Testin will use Google Analytics 4 and analytics cookies to measure visits, brief downloads and contact activity. We do not start Google Analytics without your consent. Declining does not restrict access to the website or contact form.
Google receives information about pages visited, your device and interactions, and an identifier stored in cookies. Connecting to Google also reveals your IP address; according to the GA4 documentation, IP addresses of EU users are not stored. We do not send names, email addresses, phone numbers, form content or URL parameters to GA4. We do not enable ad personalisation or Google Signals.
The tool is provided by Google. Data may also be processed outside the European Economic Area. How Google processes data.
Your choice stored in browser storage and the necessary consent cookie, as well as analytics cookies, is set to expire after up to 180 days. You can change or withdraw consent at any time using the “Analytics and cookie settings” button at the bottom of the page. Withdrawal stops further measurement and removes accessible GA cookies for this website; it does not delete data already sent. For questions about your data: [email protected].
Current setting: analytics disabled.