BruktTech: The WooCommerce Store We Build and Run Ourselves
BruktTech is our own online store for used business laptops in Oslo. We did not build it for a client and hand it over. We built it, we run it every day, and we fix what breaks. Every order, payment and shipment goes through code we wrote or configured.
That makes it our most useful case study. It shows how a WooCommerce store is built, and also what it takes to keep one selling after launch.
What the store runs on
- Payments Norwegians expect. Vipps, Klarna, card, Apple Pay and Google Pay in one checkout.
- Shipping with pickup points. Customers choose a PostNord pickup point in the checkout, or collect for free in Oslo.
- Margin-scheme VAT. Used goods are sold under the Norwegian margin scheme (avansesystemet). The store’s admin works out the VAT on each sale and prepares the figures for every VAT term.
- Consent-based tracking. A cookie banner asks first, and Google Analytics and Google Ads load only after the visitor agrees.
- Product pages that answer questions. Every unit has its own page with condition, specifications and price, and the catalogue can be filtered by model, specification and price.
- A listing workflow with AI help. One unit’s details become a product page and listings for other sales channels, without retyping.
- A release process. Changes are tested on a staging copy first and reach the live store through a deploy pipeline, with off-site backups.
Problems we found and fixed in production
Running a store means meeting the problems that never show up in a demo. A few from the last months:
1. Bots crawling the filter pages
About half of all requests came from a crawler cycling through combinations of catalogue filters, adding load and nothing else. We blocked those URLs with robots.txt rules and a Cloudflare rule, and kept clicks from Google Ads exempt so paid traffic was never challenged.
2. A cookie banner that covered most of a phone screen
The first version of the banner took 57% of a phone screen. Shorter text and buttons in one row brought it down to 32%, so shoppers see the product before the consent question.
3. A checkout hold that made laptops look sold
Each laptop is a single unit. An unpaid checkout attempt reserved it for 60 minutes and showed it as sold to everyone else, including the same buyer on another device. We cut the hold to 20 minutes and changed the wording, the same day we found it.
4. Replies going to the wrong inbox
An email plugin setting copied a rewritten sender address into Reply-To, so customers who replied to an order email reached the wrong mailbox. We fixed it in code and checked every type of email the store sends.
How we keep it running
- Staging first. Every change is tested on a copy of the store before it goes live.
- Checks after every release. Key pages, the checkout and each payment method are tested once a release is live.
- Backups away from the server. The whole site is backed up off-site, not just on the same machine.
Technologies used
WooCommerce, Flatsome, Vipps, Klarna, Stripe (card, Apple Pay and Google Pay), PostNord, Complianz, Google Analytics 4, Google Ads, WP Rocket, Cloudflare and GitHub Actions.
What it means for your store
When you hire us for a WooCommerce build, a fix or a care plan, you get developers who deal with payment plugin updates, cookie rules, shipping options and VAT schemes in their own store every week. If your store has a problem like the ones above, book a free consultation and we will look at it with you.
Related case studies
Elementor Hamburger Menu Not Working: A JavaScript Console Error Case Study
The mobile menu was visible but wouldn't open. It looked like a caching issue, but the browser console revealed a single JavaScript syntax error from an Elementor plugin that was breaking every interactive element on the page. Here's how we traced it, and the safe way to fix it without touching plugin core files.
Read articleWordPress Site Loading Without CSS, JavaScript, or Images: A File Permission Fix
A WordPress site was loading as mostly unformatted HTML: layout gone, images broken, navigation reduced to plain links. Its pages, database and admin area were still running. The cause was not malware or a failed update. It was one directory permission on wp-content.
Read articleRestoring a Legacy WordPress Website After PHP Compatibility Errors
A legacy WordPress site built with an older theme, bundled shortcodes, dated builder components and outdated plugins started breaking after a PHP update. We restored admin access, resolved the critical fatal errors, handled plugin and builder conflicts, and recovered the broken promo box shortcode section while preserving the existing design.
Read article