Build ecommerce around Briljant, not instead of it

Why Briljant needs a dedicated ecommerce strategy

Briljant is built to run the operational side of your business. It tracks inventory, manages purchase orders, handles invoicing, and keeps your financials in order. For many Swedish companies, it is the single source of truth for product data, pricing tiers, and customer records. That foundation matters when you build ecommerce on top of it.

The challenge begins when you need to expose that data to a public storefront. Briljant holds the information, but it does not structure it the way an online buyer expects to see it. Product descriptions, images, category trees, filtering attributes, and promotional pricing all require a layer of enrichment that sits outside the ERP. Without a clear plan for how data moves from Briljant to the storefront — and how orders flow back — you end up with manual processes, inconsistent stock levels, or pricing errors that erode customer trust.

That is why the ecommerce project is not just a technology decision. It is a business design exercise. You need to decide what data Briljant owns, what the ecommerce platform owns, and where the boundaries sit. Getting that right early saves months of rework later.

Choosing the right ecommerce platform for a Briljant setup

There is no single platform that fits every Briljant customer. Your choice depends on catalogue complexity, market scope, internal team capabilities, and how much control you want over the frontend experience. We work with four platforms that each bring distinct strengths to a Briljant-connected project.

Norce is a commerce engine built for the Nordic market. It handles complex product models, multi-market pricing, and B2B scenarios well. If your catalogue is large or your pricing logic involves customer-specific agreements, Norce gives you a structured way to manage that without bending the platform.

Shopware is an open-source platform with strong European roots. It offers deep flexibility for companies that want to own their codebase and tailor the buying experience closely. It suits teams that plan to invest in in-house development capacity over time.

Shopify is a managed platform that reduces operational overhead. It works well for companies that want to move quickly, keep infrastructure simple, and focus internal resources on marketing and merchandising rather than server management.

Magento with Hyvä gives you a mature, feature-rich commerce engine paired with a modern, lightweight frontend. It fits companies with complex requirements — multiple storefronts, advanced promotions, or deep integration needs — and teams comfortable with a more hands-on technical approach.

Each option is viable from day one. The right answer depends on your specific context, and part of our job is helping you evaluate that honestly before any commitment is made.

How data flows between Briljant and the storefront

The core of any Briljant ecommerce project is the data architecture. You need to define which records move in which direction, how often they sync, and what happens when something conflicts. Typical data flows include products, stock levels, and pricing moving from Briljant to the ecommerce platform, while orders, customer registrations, and payment confirmations flow back into the ERP.

For the integration layer, we use Junipeer to connect Briljant with your chosen ecommerce platform. Since Briljant does not have a pre-built connector in Junipeer's standard library, this is built as a project-specific connector scoped to your data model and business rules. That means the integration is designed around how your Briljant instance actually works — not a generic assumption about what fields exist or how pricing is structured.

A custom connector typically requires 1–2 months of dedicated integration work. But the integration itself is only one part of the delivery. Before that work begins, we need to assess data quality inside Briljant, define transformation rules for product content, agree on sync frequencies, and map error-handling scenarios. After the connector is built, there is QA, user acceptance testing, and a structured rollout plan. Skipping any of those steps creates risk that surfaces after launch.

Beyond integration: the work that makes it hold together

Many companies underestimate the non-integration work in an ecommerce project. The connector between Briljant and the storefront is critical, but it accounts for perhaps a quarter of the total effort. The rest covers areas that directly affect whether the store performs well commercially.

Platform configuration includes setting up tax rules, shipping methods, payment providers, and checkout flows. Content work means writing product descriptions, preparing images, building category structures, and creating landing pages that support both SEO and the buying journey. UX design ensures the storefront reflects how your specific customers actually shop — not just a template with your logo on it.

QA is another area that deserves real attention. Testing order flows end-to-end — from cart to Briljant — under realistic conditions catches issues that unit tests miss. Price rounding errors, stock discrepancies on high-volume items, and edge cases in customer-specific pricing all need to be verified before real orders start flowing.

Rollout planning rounds out the project. This includes deciding whether to launch with a full catalogue or a subset, how to handle the transition from any existing sales channel, and what monitoring to put in place during the first weeks after go-live.

What working with Nordic Web Team looks like

We are a Swedish ecommerce agency that works across platforms. We do not sell a single stack. Instead, we help you evaluate options based on your actual situation — your Briljant setup, your team, your catalogue, and your growth ambitions. The goal is an ecommerce operation that fits your business, not one that requires you to reshape your business around a platform vendor's assumptions.

Projects typically start with a discovery sprint where we map your current systems, data quality, and commercial goals. From there, we recommend a platform direction, define integration scope with Junipeer, and plan the build in phases that let you validate progress along the way. Every project includes platform configuration, integration design, content strategy guidance, QA, and rollout support. The scope scales based on complexity, from focused implementations to multi-market rollouts.

If you are running Briljant and considering ecommerce — or rethinking an existing setup — we are happy to walk through what a realistic project looks like for your situation.