Built for ten orders.
Ready for ten thousand.
The most expensive minute in a webshop's life arrives right after the campaign email lands in ten thousand inboxes. A customer with a full cart sees a blank page where the checkout should be. The Vipps window has stopped responding. Bring's rate lookup has just timed out. The agency that built the store suggests updating a plugin.
How far a WordPress webshop scales has surprisingly little to do with WooCommerce. On an indexed database with a server that has headroom, ten thousand orders a day pass without drama; on bargain shared hosting, fifty can be a struggle. The plugin itself is rarely where the trouble lives. The setup wrapped around it is.
We operate WooCommerce stores that put through millions in revenue every year, and not one of them lives on the cheapest tier of a shared host. Some came to us as new builds. Most didn't. Most were rescues, businesses ready to get away from a store that never worked properly.
WooCommerce stores running worldwide
NOK spent in Norwegian e-commerce, 2025
Product pages on our stack
Cart including live shipping rates
What makes WooCommerce fit Norwegian e-commerce
Full data ownership
Norwegian integrations
VAT handling
Content-driven sales
What 50,000 products
do to a store
Five hundred products run fine on almost anything. Five thousand start to creak. By fifty thousand a default install has stopped responding altogether, and the admin panel had turned sluggish well before the storefront did. We see the same arc on rescue after rescue: the assortment expands, variants and filter attributes accumulate, the catalog query count quietly triples, and one day the product page needs 4.7 seconds to render.
WooCommerce itself is rarely the bottleneck. An unindexed catalog with 10,000 variants fires hundreds of SQL queries at the database for a single page view, and no amount of frontend polish will hide that. We tune the schema until a product lookup costs milliseconds, and a Redis object cache goes in during the build rather than getting bolted on once the database has already buckled once.
Then the images. Three photos across 50,000 products makes 150,000 files, and a lone origin server in Norway hands them out slowly to anyone far away. Put a node closer to the visitor and the same image arrives in 40 ms where the origin needed 400. Underneath all of it runs FrankenPHP, the application server we use for WordPress webshops, which keeps responses under 200 ms even with a heavyweight catalog.
WooCommerce or Shopify?
Pick WooCommerce when
- The catalog runs past 1,000 products or the variant logic gets complicated
- Vipps, Bring and the rest of the Norwegian stack are business-critical
- An ERP, warehouse system or POS has to talk to the store
- Guides and articles carry part of the sales work
- Owning your customer and order data is non-negotiable
- Margins won't survive a 2% transaction fee stacked on card costs
Pick Shopify when
Shopify earns its place too. Honestly, it's the saner choice when:
- You sell fewer than 500 products and want something that just works
- Launch has to be ready within a couple of weeks
- No Norwegian back-office systems need to plug in
- The budget sits under 50,000 NOK and turnkey is the whole point
When the choice stays open, our pricing guide runs the long-term numbers on both platforms.
Where WooCommerce
tops out
Plenty of Norwegian webshops belong on WooCommerce and nowhere else. When the marketing team already lives in WordPress and the editors move quickly in Gutenberg, years of accumulated skill sit under the project, and the investment in themes and content keeps its value. It is mature software with an enormous community behind it, and it takes a lot before that becomes the wrong call.
Some briefs point elsewhere, though. An oversized catalog, layered pricing models, storefronts in several countries or hard requirements for API freedom call for a different shape — so we build those on MedusaJS as the commerce engine, with Sanity handling content. That is a different architecture, and it raises the ceiling accordingly.
Our recommendation follows the business case, not whichever stack we happen to enjoy building. If your team already ships fast in WordPress, that on its own is a strong argument for staying put on WooCommerce. When you are starting from a blank slate with several markets in your sights, the alternatives deserve a serious look before a single line gets written.
Payments
Vipps MobilePay
The one payment app that lives on nearly every Norwegian phone. We implement Vipps Checkout, Vipps Express and Hurtigkasse (Vipps express checkout) to match whatever the checkout flow needs.
Klarna
Invoice and installment options. They visibly lift conversion once orders pass 1,000 NOK.
Nets Easy
Visa, Mastercard and BankAxept handled under one agreement. The Norwegian default for card payments.
Stripe
Covers markets beyond the Nordics, along with subscriptions and recurring billing.
Shipping & delivery
Bring/Posten
Live rates calculated from weight, dimensions and postcode. Mailbox parcels, pickup points or delivery to the door, all selectable at checkout.
Helthjem
Evening home delivery. Strongest in the major cities, with coverage spreading steadily across the country.
Porterbuddy
Same-day delivery in Oslo, Bergen, Trondheim and Stavanger. Built for stores that compete on delivery speed.
PostNord
Parcel flows across the Nordics in both directions. A requirement once Swedish and Danish customers enter the picture.
The stack underneath the store
FrankenPHP
Redis object cache
Intelligent page cache
CDN
Auto-scaling
Before and after, measured
Each added second of load time cuts conversion by up to 7% [1]. The four seconds shown above take close to 28% of purchases with them. On 5 million NOK in annual revenue that adds up to more than a million NOK lost each year, with the same products at the same prices. The infrastructure is the only variable.
What you'll pay at PXL
| Type | What's included | Investment |
|---|---|---|
| Simple webshop (<500 products) | Standard theme plus Vipps, Klarna and Bring | from 150,000 NOK |
| Mid-size project | + Custom design, ERP connection, advanced shipping setup | from 250,000 NOK |
| Enterprise | + Large catalog, headless architecture, multiple countries, heavier integrations | from 400,000 NOK |
| Maintenance and SLA | Monitoring, security patching, updates and a guaranteed response time | from 5,000 NOK/mo |
Simple webshop (<500 products)
Standard theme plus Vipps, Klarna and Bring
from 150,000 NOKMid-size project
+ Custom design, ERP connection, advanced shipping setup
from 250,000 NOKEnterprise
+ Large catalog, headless architecture, multiple countries, heavier integrations
from 400,000 NOKMaintenance and SLA
Monitoring, security patching, updates and a guaranteed response time
from 5,000 NOK/moWebshop security
PCI DSS
HTTPS and SSL
Norwegian privacy regulations and GDPR
Two-factor authentication
The three-year math
A free plugin does not make a free webshop. Run the numbers across three years, though, and WooCommerce lands below Shopify for nearly any store with real volume.
The difference is structural. WooCommerce takes no 0.5–2% cut of every order, and there is no platform fee that climbs as your revenue grows.
Take a store at 5 million NOK in annual revenue. Its transaction fees on Shopify land at 25,000–100,000 NOK every single year, and the monthly subscription still comes on top of that. Three years of fees on that scale would cover a professional WooCommerce build outright, with a maintenance agreement included.
The pricing guide lays the whole calculation out, line by line.