BluePes Blog: Insights & Trends

BluePes Blog: Insights & Trends

Code freeze: release management for seasonal peaks

Code freeze: release management for seasonal peaks

Two things tend to surprise teams new to this. First, for a seasonal business the freeze rarely fits in a long weekend around Black Friday; it can run for months, as long as the peak itself. Second, the freeze reshapes the roadmap, because anything large has to land before it starts. The examples here come from a seasonal firewood marketplace whose peak runs through autumn and winter, with the rest of the year reserved for the bigger work.

  • Jul 10, 2026
  • 16 min
Dynamic route optimization when indexes aren't enough

Dynamic route optimization when indexes aren't enough

This is an engineering case rather than a tutorial. It draws on a Norwegian firewood-delivery marketplace where route recalculation dropped from five-to-seven seconds to under one, and a multi-condition availability query fell from three-to-five seconds to about one. The numbers matter less than the reasoning behind them: how to tell when the answer is a better algorithm, when it is caching, and when it is simplifying the work itself.

  • Jul 03, 2026
  • 16 min
B2B B2C hybrid commerce without breaking B2C flows

B2B B2C hybrid commerce without breaking B2C flows

The build that follows draws on a Norwegian firewood marketplace that runs a consumer webshop and a chain-customer webshop on the same platform. By the end, you should be able to decide where chain hierarchies, per-account pricing, and invoice-based order lifecycles belong in your own system, and where bolting them onto consumer flows will cost you later.

  • Jun 28, 2026
  • 16 min
Separate storefronts or one platform on a shared backend

Separate storefronts or one platform on a shared backend

This piece is about that topology decision and the shared backend underneath it, not about how to model the B2B side once you have chosen — that modeling is its own subject, linked below. By the end you should have a decision framework you can apply to your own platform, a clear view of what the shared backend has to provide regardless of approach, and a sense of when neither option is worth building yet.

  • Jun 21, 2026
  • 16 min
Ecommerce scalability and performance for peak season

Ecommerce scalability and performance for peak season

Auto-scaling does not save you when the bottleneck has moved to a synchronous call that did not exist last year. Preparing a seasonal platform is less about handling load in the abstract and more about knowing where this year's stack will fail under concentrated demand, and testing for that specifically. The article walks through where seasonal platforms typically break, how to model peak traffic accurately during load testing, and how to design for scale-up and scale-down so you stop paying for January capacity in July.

  • Jun 12, 2026
  • 15 min
E-commerce RFP technical questions for vendor

E-commerce RFP technical questions vendors must answer

This article gives eight questions worth adding to an e-commerce development RFP and explains what a strong answer, a weak answer, and a direct Bluepes-style answer should look like.

  • May 29, 2026
  • 16 min
Marketplace vendor mobile app with push-based order management.

Supplier mobile app for marketplaces: a decision guide

For marketplace teams with a functioning supplier dashboard, the next decision is whether to extend it with a mobile experience and what shape that mobile product should take. The reader of this piece already has operational evidence on where vendors fall out of the flow. The question is whether a supplier mobile app for marketplaces is worth the engineering investment, and which architectural decisions matter most if the answer is yes.

  • May 28, 2026
  • 16 min
Blue route diagram showing hidden complexity in logistics routing decisions

Location-based order routing: where geo-routing breaks

Location-based order routing is an architectural choice that touches four systems at once — supplier registry, inventory visibility, pricing logic, and customer-facing UX. The routing algorithm itself is usually the smallest part of the work. Most marketplaces hit this point when delivery cost starts to dominate the customer's experience of the platform.

  • May 22, 2026
  • 15 min
Abstract marketplace architecture banner illustrating how platform structure limits marketplace scalability, with modular blocks and the text “Architecture sets the limit”

Marketplace plugin vs purpose-built platform: when to move

Marketplace plugin vs purpose-built platform is not a feature comparison. A plugin is an adapter over someone else's commerce architecture. At low volume the adapter holds. As the operating model grows — multi-jurisdiction payouts, custom routing, per-vendor pricing and inventory variation — the gap between what the plugin allows and what the business needs widens into operational cost. At that point the architecture decides the next eighteen months of the business, not the feature roadmap.

  • May 15, 2026
  • 15 min