Most webshops are built on a simple assumption. A customer adds a product to a cart, pays, and you ship a parcel. For a huge number of businesses, that is exactly right.
For Gressenteret, it was not. They sell ferdigplen and sedum, products where price, quantity, delivery, pickup, customer type, and invoicing all shape the order. A standard store could take the payment, but it could not run the business. So we rebuilt it.
What was the problem?
Gressenteret already had a working webshop. Product pages, cart, checkout, all functioning. But the actual operation lived around the site, not inside it.
Orders needed manual follow-up. Delivery details were handled by the office. Pricing was not a simple fixed number per item, it depended on quantity, customer type, and how the order was fulfilled. None of that fit a normal “add product, ship parcel” store, so the team filled the gap by hand, order after order.
That works until volume grows. Then every manual step becomes a place where time leaks and mistakes slip in.
Why doesn't a standard webshop work for this?
Because the product does not behave like a parcel.
Selling turf and sedum is an operational job, not just a transaction. An order might be picked up or delivered. The price depends on how much and for whom. A driver needs to know where to go and what to bring. The office needs to capture payment and raise an invoice. A generic store handles none of that. It handles the checkout and stops.
When the software stops at checkout, the rest of the work does not disappear. It just lands on a person.
What did we actually build?
We did not build another webshop. We built the store and the system that runs it, connected as one.
On the operational side there is a dashboard for the office and the drivers. It includes custom pricing rules, the ability to create and edit orders manually, pickup and delivery handling, a mobile view so drivers can work from a phone or tablet, delivery status tracking, a Klarna capture flow, Tripletex invoice drafts, and product and customer management. All of it in one place.
So the storefront takes the order, and the same system carries it all the way through to delivery and invoicing. Nothing falls into a spreadsheet or an inbox in between.
What changed for the team?
The clearest change is operational. Gressenteret went from handling orders across separate manual steps to running them from a single dashboard.
The office can see incoming orders, create and edit them, plan deliveries, and manage customers and products without leaving the system. Drivers work from mobile and mark deliveries done as they go. We do not have a hard time-saved number to quote yet, but the result is plain: fewer manual handoffs and far less admin around every order.
That is the real win. Not a prettier shop, but a business that runs on one system instead of a person stitching steps together.
When does a custom build make sense?
Not always. If you sell standard products and ship parcels, a good off-the-shelf store is the right call, and we will tell you so.
But if your product comes with rules, like variable pricing, delivery and pickup, different customer types, or invoicing that has to be exact, a standard store will only ever do half the job. The other half ends up as manual work. A custom build is worth it when that manual work is big enough to cost you real time.
Gressenteret was clearly on that side of the line. The store was never the hard part. Running the operation was.
If your online store stops at checkout and your team picks up everything after, that is worth a conversation. We are happy to look at how your orders actually flow and tell you honestly whether a custom build earns its keep.