---
title: "Kortreistved: hyperlocal firewood marketplace where the nearest supplier delivers"
description: "Norwegian firewood marketplace by Bluepes. Coordinate-based supplier matching, Group Buy with 25–70% tiered discounts, B2B chain customers, EHF/PowerOffice, Flutter mobile app"
url: "https://bluepes.com/projects/kortreistved"
language: "en"
---

# Kortreistved: hyperlocal firewood marketplace where the nearest supplier delivers

## Project Overview

Location

Norway, Ukraine

Industries

- [Online marketplace](https://bluepes.com/e-commerce)

Hyperlocal delivery

Logistics

Expertise

- [Product development](https://bluepes.com/product-development)

Software engineering

- [QA](https://bluepes.com/roles/qa-engineer-specialist-role)
- [Mobile development](https://bluepes.com/development-services/mobile-app-development)

Team

7 people

Services

- [Dedicated Team](https://bluepes.com/dedicated-development-team)

Outsourcing Quality Assurance

Technologies

React, Tailwind CSS, JavaScript

PHP, Laravel, MySQL

Flutter, Dart

## At a glance

### What it is

A Norwegian online marketplace for buying firewood

- Buyers enter their delivery address
- The platform shows only products from suppliers who can deliver to that exact spot
- Standard, group, pre-order, and B2B order types

### How it works

Every order is matched by coordinates, not zip codes

- Neighbors can join group orders for a shared delivery
- Businesses with multiple shops order on invoice through a separate B2B flow
- Drivers run delivery routes from a mobile app

### What Bluepes does on this project

A dedicated team handles the full product cycle

- Analysis, design, development, QA, releases
- Embedded with the platform across multiple seasons
- Knows the business, not just the code

## About The Project

### Background

Kortreistved is a Norwegian online marketplace for buying and delivering firewood. The platform connects buyers with local suppliers based on the buyer's exact delivery address — the closer the supplier, the higher the priority. The business is highly seasonal: autumn and winter carry peak demand, while spring and summer are used for new feature development and platform improvements that would be too risky to release during peak.

The platform spans several connected surfaces — an admin panel, a supplier dashboard, a B2C webshop, a separate B2B webshop for chain customers, and a mobile app for suppliers and drivers. Most changes touch more than one surface, which shaped how the team organised delivery, testing, and releases.

### What Kortreistved Needed

The client needed an engineering partner who could take responsibility for the full product lifecycle — from analysing existing functionality and identifying bottlenecks, to delivering new features and maintaining a stable production environment during peak season. The geographic ordering logic that the business depends on required continuous iteration based on operational feedback from suppliers, drivers, and chain customers.

The engagement was framed around long-term iteration rather than a one-off rebuild, which is closer to the decision between a marketplace plugin and a purpose-built platform that most growing marketplaces eventually face. The roadmap evolves with the business, and the team participates in analysis, planning, design, implementation, QA, and release across every surface.

The platform connects local firewood suppliers with buyers and provides delivery nationwide.

## Our Approach

### Phase 1 — Discovery and analysis

We analyze the existing platform, identify bottlenecks, and propose solutions. Discovery covers the technical questions worth asking before scoping a marketplace build — even without a formal RFP — and aligns roadmap priorities with the client.

[Contact us](https://bluepes.com/contact)

### Phase 2 — Planning and design

Scrum-based planning, with architectural decisions reviewed jointly and estimates and risks discussed before any commitment.

### Phase 3 — Development with embedded QA

Engineers and QA work in the same sprint, with test cases written as features evolve and code quality held through reviews and agreed standards.

### Phase 4 — Release with seasonal awareness

Frontend deploys through Bitbucket Pipelines, with production validation and smoke testing, and peak-season freeze windows enforced.

### Phase 5 — Continuous improvement

Regular demos and retrospectives, platform-improvement proposals based on what the team sees during delivery, and long-term business knowledge preserved across team rotations.

## Why this project is engineering-complex

### Geographic-first matching

Every order depends on coordinates and a chain of conditions that decide which supplier can actually deliver

- Multi-condition supplier matching
- Address resolution with partial-match fallback
- Nearest-vendor tie-breaking rules
- Delivery radius and zone enforcement

### Five connected surfaces

Most product changes touch more than one surface. Coordinated releases and shared API contracts are not optional

- Admin panel (legacy + React)
- Supplier dashboard (React)
- B2C webshop (React)
- B2B chain-customer webshop
- Flutter mobile app for the field

### Seasonal load profile

Peak season is autumn and winter. Downtime during peak has a real cost, and release strategy is built around it

- Six-month peak window each year
- Feature freeze during peak season
- Hotfix-only release pattern in winter
- Heavier feature work in spring and summer

## Outcomes

### Performance gains

Specific engineering improvements with measurable before/after numbers

- Product availability: 3–5s → ~1s
- Route recalculation: 5–7s → <1s
- CRON-based WordPress recovery
- Stable peak-season releases

### Business features now live

Major marketplace capabilities delivered, refined, and operating in production

- Coordinate-based geographic matching
- Package products (80–85% of total sales)
- Group Buy with deadline and single-route logic
- Pre-orders with split-payment options
- B2B Chain Customers with EHF / PowerOffice

### Operational reliability

How the team and process protect the business across seasons

- Dedicated team embedded long-term
- Embedded QA with test-case documentation
- Seasonal release management protocol
- Multi-surface coordination across web and mobile

## Platform Architecture

### How the platform is built

In simple terms: one shared backend powers every part of the platform — admin panel, supplier dashboard, both webshops, and the mobile app. The same data drives every screen, so a change made by an admin appears for buyers, suppliers, and drivers without manual sync.

The platform runs on a Laravel backend with a single MySQL database. The backend exposes a REST API used by every client surface — the React supplier dashboard, the B2C webshop, the chain-customer webshop, the mobile app, and the Laravel Blade admin panel. The backend is moving gradually from a monolithic structure toward modular organisation by bounded domain — orders, products, users, logistics.

Architectural decisions that shape day-to-day delivery:

- Backend-level RBAC controls permissions across every client surface, so the same authorisation rules apply whether a request comes from the admin panel or the mobile app
- A layered Controller → Service → Repository pattern keeps business logic separated from transport and persistence
- API versioning protects backward compatibility, which matters particularly for the mobile app where users do not update on a predictable schedule
- The supplier dashboard and B2C webshop share a single frontend codebase. Build target flags produce different applications with their own UI configuration, branding, and enabled features
- Background queues and scheduled jobs handle imports, exports, notifications, and heavier calculations that should not block a user request

## Core marketplace features we delivered

### [Geographic ordering and supplier matching](https://bluepes.com/blog/geo-routing-marketplace-order-assignment)

- Coordinate-based, not postal-code-based
- Google autocomplete or manual map marker
- Partial-match handling with later validation
- Multi-condition product availability

### [Package products (composite bundles)](https://bluepes.com/blog/product-bundle-pricing-marketplace)

- Admin-only creation and pricing
- Fixed price across all vendors
- Order-time snapshotting protects history
- Approximately 80–85% of total sales

### [Group Buy (collective ordering)](https://bluepes.com/blog/group-buying-delivery-marketplaces)

- 350-metre radius around the initiator
- Tiered discounts from 25% up to 70%
- Group deadline and single-route enforcement
- Cashback returned after group completes

### [Pre-orders (future delivery dates)](https://bluepes.com/blog/preorder-ecommerce-architecture)

- Supplier-specific availability dates
- 10% / 90% split payment option
- Full prepayment with 5% discount option
- Cart-conflict rules across order types

### [Chain Customers (B2B flow)](https://bluepes.com/blog/b2b-b2c-hybrid-commerce-architecture)

- Parent → departments → managers hierarchy
- Negotiated pricing per department
- Invoice-based payment with EHF / PowerOffice
- Admin-only onboarding, Excel bulk import

### [Mobile app for suppliers and drivers](https://bluepes.com/blog/blog-supplier-mobile-app-marketplace)

- Flutter, shared Dart codebase
- Multi-brand runtime module selection
- Partial offline support via SQLite
- Google Maps / Apple Maps deep links

Six feature areas defined the bulk of the engineering work over the engagement. Each one has its own logic, edge cases, and operational constraints — and most touch more than one surface of the platform.

## Engineering challenges we solved

### Slow product availability queries

Product listings took 3–5 seconds to load because one query combined every availability condition at once

- Joined coordinates, supplier radius, zone pricing, stock, status, priorities
- Rewrote the query path and simplified redundant branches
- Added result caching for stable inputs
- Load time dropped from 3–5s to ~1s

### Slow route recalculation

Planning a route took 5–7 seconds every time an order was added or removed

- Every adjustment forced a full recalculation
- Reworked the routing algorithm
- Recalculation dropped from 5–7s to under 1s
- Route planner became usable as a live tool

### Releases during peak season

A broken release during autumn–winter peak has a direct revenue cost

- Only hotfixes, security, and business-critical changes in peak
- Larger feature work concentrated in spring and summer
- Smoke testing after every production release
- Six-month freeze window treated as normal

### Group Buy logic redesign

The first version let groups keep adding members after deliveries were already scheduled

- Broke the single shared-route assumption
- Added a group deadline and delivery-date inheritance
- Blocked delivery planning before the deadline closes
- Enforced one route across all members

### WordPress connectivity recovery

The marketing sites lost their database connection and broke the link to the webshop

- Affected the marketing sites that drive traffic to the webshop
- Failure required manual intervention to fix
- Built a CRON-driven detection and recovery process
- Connection now restores automatically

## Mobile app for suppliers and drivers

### The driver workflow

Drivers and suppliers use one Flutter app to run their workday in the field — picking up the day's route, navigating to each address, confirming each delivery with a proof photo, and submitting completed routes back to the platform. The same app works on iOS and Android.

### Cross-platform build

The app is built with Flutter on a shared Dart codebase. iOS 11 and above is supported; Android targets minSdk 21 and targetSdk 36. Kotlin and Swift are used only as thin bootstrap layers, not for business logic. Brand behaviour for the firewood and GardenBio modules is handled through runtime module selection rather than build flavours.

### Partial offline support

Offline support is partial. Delivery statuses and returns are stored locally in SQLite so the driver can keep working when connectivity drops. Sign-in, route refresh, photo upload, and route start/complete  still require a connection.

## Let’s have a talk

Get a first consultation on your project

[Contact us](https://bluepes.com/contact)

## Projects

We have completed an array of projects, each of them unique from the perspective of business logic and generally common in terms of technologies, and vice versa. Basically, there’s no possibility (and we mean no, zero, null, non c'è) chances that we’ll start a new project out of blue (pun intended).

- [Building a two-sided services marketplace MVP from scratch for the German-speaking market](https://bluepes.com/projects/service-marketplace-mvp)

[See all](https://bluepes.com/projects)

## FAQ

### How does the platform decide which supplier delivers an order?

Supplier selection runs on coordinates rather than postal codes. The buyer's address is geocoded through Google Maps or set with a map marker, and the platform filters suppliers by delivery radius, vendor zone, stock, vendor status, module, admin priorities, and any active group-buy or chain-customer rules. When several suppliers can deliver the same product, the nearest one wins.

### Why did you move away from postal-code-based matching?

Norwegian postal codes can cover large areas, and the centre of a postal code area can sit several kilometres from a buyer's actual address. That mismatch let buyers see products from suppliers who could not realistically deliver to them, produced incorrect delivery pricing, and broke route planning. Switching to coordinates removed the root cause.

### What is special about package products on Kortreistved?

Package products are bundles created and priced centrally by admins. Vendors cannot adjust package prices or component prices, so pricing is consistent across the platform. Package definitions are snapshotted into each order at creation, so future edits to a package do not retroactively change historical orders. Packages now account for the majority of platform sales.

### How does Group Buy actually work?

A buyer orders an eligible product and receives a group code by email. Other buyers within 350 metres of the initiator's address can join using that code. Once the group deadline closes, the platform schedules a single shared delivery route for all members, and the discount — between 25% and 70% depending on group size — is returned as cashback or a refund to the original payment method.

### How does the B2B chain customer flow differ from B2C?

Chain customers are organised in a parent-to-departments hierarchy with negotiated pricing, invoice-based payment, vendor restrictions, EHF invoicing, and PowerOffice integration. They cannot self-register; admins configure them because onboarding involves commercial and operational decisions that do not fit a self-service signup.

### What does the mobile app cover?

The Flutter app handles the supplier and driver workflow: login, route lists, route execution, turn-by-turn navigation through Google Maps or Apple Maps, delivery confirmation with proof photo, status updates, and submission of completed routes and returns. Partial offline support lets drivers continue updating delivery statuses when connectivity is intermittent.

### How does Bluepes handle releases during peak season?

During autumn and winter, non-critical changes are frozen and production releases are reserved for hotfixes, security updates, and business-critical functionality. Larger feature work is concentrated in spring and summer, with QA and stakeholder sign-off in pre-production before any production deployment.
