Skip to content
5.0 Upwork, 100+ reviews Adobe Certified since 2021 New: become your own Magento developer Learn more →
Hire me
Toggle Nav
My Cart
Adobe Certified freelancer · Stores selling in NOK

Magento developer in Norway, working from Ahmedabad

I’m Kishan, an Adobe Certified Magento developer for Norway based in Ahmedabad, India. Norway trips up a lot of Magento setups because it sits in the EEA but outside the EU, so EU VAT rules do not carry over. I set up Vipps at checkout, prices in NOK with 25% MVA, and the VOEC flow for low-value parcels coming in from abroad.

  • Your 09:00 in Oslo is 13:30 in Ahmedabad in winter, 12:30 in summer
  • Vipps first, then Klarna and card payments for everyone else
  • Org.nr checks and EHF invoices for Norwegian business buyers
Reserve my slot Get a quote
Free 30-minute call, no obligation Written quote within 24 hours
Magento developer in Norway, working from Ahmedabad

Your morning is my afternoon

09:00Oslo 13:30Ahmedabad

Standard time. I work 10 AM to 7 PM IST, Monday to Saturday.

Norway at a glance, for your store

  • Vipps The payment people expect

    Norwegian shoppers look for the orange Vipps button. I add it next to Klarna and cards, and I test it on a real phone, not just in the sandbox.

  • MVA 25% Three rates, not one

    Most goods carry 25% MVA, food 15%, and a few services 12%. I map each product to the right tax class so the totals on the invoice match what your accountant expects.

  • EEA, not EU VOEC and customs

    Norway is outside the EU VAT area. For items under NOK 3,000 a VOEC-registered seller charges MVA at checkout; above that the parcel goes through customs. I set Magento up for both cases.

  • 4h30 Ahead of Oslo in winter

    When it is 09:00 in Oslo it is 13:30 in Ahmedabad (12:30 in summer), so your whole morning overlaps with my working afternoon.

What you get

What I set up for stores selling in Norway

Most of the Norway-specific work in Magento is about money and borders: how people pay, how MVA is charged, and what happens when a parcel crosses into Norway from the EU. These are the parts I check on every Norwegian store before touching anything else.

  • Vipps at checkout, done properly

    Vipps merged with Denmark’s MobilePay, but in Norway people still know it as Vipps. I install the official Magento module, turn on express checkout where it makes sense, and check that refunds from the Magento admin actually reach the customer’s app.

  • Klarna, cards and a fallback for tourists

    Not every buyer has Vipps. Klarna covers invoice and part payment, and a card gateway such as Nets Easy or Stripe handles Visa and Mastercard with 3D Secure. I keep the payment step short so the extra options do not slow anyone down.

  • Org.nr checks for business customers

    If you sell to Norwegian companies, I add a field for the 9-digit organisasjonsnummer and look it up in the Brønnøysund register, so a typo is caught before the order goes through, not when the invoice bounces.

  • EHF invoices for public and B2B buyers

    Norwegian public bodies expect invoices in the EHF format over the Peppol network, and many larger companies ask for the same. I connect Magento orders to your accounting system or a Peppol access point so you do not retype invoices by hand.

  • Selling into Norway from the EU

    This is where most EU stores get it wrong. Under the VOEC scheme you charge Norwegian MVA at checkout for items under NOK 3,000; heavier orders need a customs declaration. I set the tax rules and the checkout messages so customers are not surprised by a fee at the door.

  • Posten, Bring and price feeds

    Most parcels in Norway go with Posten and Bring, often to a pickup point at the local shop. I add those delivery options, show prices in NOK, and set up product feeds for price comparison sites like Prisjakt.

How I work

Five steps from booking to live

My working day starts a few hours before Oslo’s, so when you open your laptop at 09:00 (13:30 for me in winter, 12:30 in summer) my morning’s work is already on staging for you to check. We usually talk mid-morning your time, and I plan the go-live for a quiet early-morning hour in Norway.

Daily overlap, standard time, in Oslo time
Your day 09:00 to 18:00
My hours 05:30 to 14:30
  1. 01

    Audit

    Free 30-min audit of your Norwegian store, Vipps MobilePay + BankAxept + Klarna integration, EHF / Peppol pipeline, Org.nr validation, MVA + VOEC setup, Core Web Vitals. Booked in a CET-friendly slot.

    Day 1
  2. 02

    Quote

    Fixed-price written quote in USD with the NOK figure alongside. Reserved start date, risk register, written project plan. You sign, I book the slot.

    Day 2
  3. 03

    Build

    Daily review at 10 AM CET typical, right inside your Oslo / Bergen working day. Staging access from day 3 with a real Norwegian postnummer + Vipps + BankAxept test cart.

    Days 3-14
  4. 04

    Deploy

    Blue-green cutover scheduled for off-peak (3 AM CET typical, lowest NO traffic). Old release stays warm for 72 hours so rollback is one DNS flip.

    Launch night
  5. 05

    Stabilise

    14 days of post-launch coverage in CET business hours. Anything that breaks because of the cutover gets fixed at no extra charge, EHF submissions + VOEC reports monitored daily.

    Days 14-28

Your quote

Get a fixed quote for your project

Send your store URL and describe what you want to change. We can review the requirements and agree a written scope, quote and timeline before work starts.

  • Free first call
  • Written scope, price and timeline
  • You approve every change
Hire on Upwork
What clients say

What clients say about working with me

Reviews from store owners I have worked with on Upwork, Clutch and through direct referrals.

Magento work and feedback View Upwork profile

  • Illustration of Magento 2 development work for a sports footwear and hockey shop
    Sports footwear and hockey shop, Netherlands
  • Illustration of Magento 2 development work for a photo printing supplies wholesaler
    Photo printing supplies wholesaler, Netherlands
  • Illustration of Magento 2 development work for an educational toys and books shop
    Educational toys and books shop

  • Kishan has done an excellent job in a timely manner. He is very knowledgeable, has a very positive attitude, easy to communicate.

    Z. K.Magento 2 client

  • He is technically strong, approaches problems thoughtfully, and focuses on stable, long-term solutions.

    E. H.Magento 2 client

  • Kishan was a pleasure to work with! He is highly skilled, professional, and delivered outstanding results on time.

    M.Magento 2 client
Read all reviews
FAQ

Honest answers to the questions every Norwegian merchant asks

Magento vs Shopify Plus vs Mystore for the Norwegian market, which fits?

Three real options Norwegian merchants weigh, and they fit different shapes:

  • Mystore, Oslo-built SaaS, native Vipps + BankAxept + EHF, ideal for NOK 2-20M Norwegian-only stores that just want to ship fast in Bokmål. Limited cross-border and weak B2B catalogues.
  • Shopify Plus, great DTC speed, strong checkout, but Vipps MobilePay support is via apps (decent but not as deep as native), EHF e-invoice needs a third-party app, and you pay platform fees on every NOK transacted.
  • Magento 2 / Adobe Commerce, the right pick if you need: multi-store (NO + DK + SE + FI on one backend), full B2B (Org.nr-gated catalogues, Net-30/60, quotes), EHF native via mature modules, deep ERP integration (Tripletex, PowerOffice Go, Visma, SAP), and ownership of the checkout. No per-transaction platform fee.

Rule of thumb: under NOK 20M and Norway-only, Mystore or Shopify is fine. NOK 20M+, multi-country Nordic, real B2B, or ERP-integrated, Magento wins. We migrate from all three.

How does Vipps MobilePay integration work in Magento 2?

Vipps MobilePay is Norway’s dominant mobile-pay rail, ~70% adult adoption, merged with Danish MobilePay in 2022. If you sell to Norwegians and don’t offer Vipps, you lose real revenue. The official Vipps Magento 2 module covers four flows:

  • Vipps eCom, standard checkout payment. Customer enters phone number, approves in the Vipps app, order completes. Works on desktop + mobile.
  • Vipps Hurtigkasse (Express Checkout), one-tap from cart, Vipps returns shipping address + email + phone. Cuts checkout to ~10 seconds on mobile, massive conversion win.
  • Vipps Login, passwordless social login using Vipps identity.
  • Vipps Recurring, subscription billing, agreement-based, customer approves recurring charge once.

We wire all four, configure 3DS2 + SCA, integrate Vipps Browser-Redirect vs Native-App-Switch (faster on mobile), and verify with Vipps’ sandbox test MSISDNs. Webhook reconciliation against sales_order_payment handles partial captures + refunds.

What’s the right Norwegian payment stack, Klarna, BankAxept, Nets Easy, Stripe?

Norwegian shoppers expect multiple rails at checkout. The right mix for a typical NO Magento store:

  • Vipps MobilePay, always. ~70% of Norwegian adults have it. Single biggest conversion lever for mobile checkout.
  • BankAxept, the Norwegian national debit-card scheme. Co-badges on most Norwegian-issued cards (BankAxept + Visa or Mastercard). Lower fees than international card rails when the customer routes domestically, PSPs like Nets Easy, Stripe NO, Klarna, and Adyen all support BankAxept routing.
  • Klarna, the dominant Nordic BNPL. Pay Later, Pay in 3, Pay Now (direct debit). ~40-60% of Norwegian DTC checkout uses Klarna, especially fashion / outdoor / electronics.
  • Nets Easy (Easy), Nordic-region PSP, strong on Visa/Mastercard + BankAxept + Vipps inside a single hosted page. Popular alternative to Stripe in Nordic stores.
  • Stripe NO, modern API, good for international card rails + Klarna + Apple/Google Pay. Easier integration than Nets for dev-led teams.
  • PayPal, long tail of international customers, low domestic share in NO.

We typically ship Vipps + Klarna + Nets Easy (or Stripe NO) on day one. BankAxept routes through whichever PSP you pick.

How do I validate Org.nr (Brønnøysund) + VIES at Magento B2B checkout?

Two B2B identifiers for Norwegian Magento stores, two different validators:

  • Org.nr (Organisasjonsnummer), 9-digit Norwegian company ID. Issued + maintained by Brønnøysund Register Centre (Brønnøysundregistrene). Free public API returns company name, address, NACE industry code, MVA-registration status, bankruptcy status. Validate at registration; reject closed / dissolved companies.
  • VIES VAT, format NO + 9-digit Org.nr + MVA (e.g. NO123456789MVA). Validated via the EU VIES service. Required for cross-border zero-rated B2B sales to EU customers.

For Magento B2B we:

  1. Add Org.nr + VAT-number fields to the customer entity (or B2B company on Adobe Commerce).
  2. Validate Org.nr against Brønnøysund API on registration, auto-fills company name + address.
  3. Validate the VAT-number against VIES for EU cross-border B2B sales.
  4. Apply correct MVA: 25% standard for NO B2C + NO→NO B2B; 0% with reverse-charge for NO→EU B2B with valid VIES VAT.
  5. Cache validations 30 days, re-validate on any address change.
What’s EHF and when do I need it in my Magento checkout?

EHF (Elektronisk Handelsformat) is Norway’s national e-invoice standard, a Peppol BIS-based XML format. It’s mandatory for B2G (business-to-government) since 2012, and is increasingly required in B2B sectors (especially construction, healthcare, energy, large enterprises).

The flow in Magento:

  1. Order placed in Magento, tax + shipping + line items finalised.
  2. On invoice generation, an EHF XML document is built (UBL 2.1 schema, Peppol BIS Billing 3.0 profile).
  3. EHF XML is routed through a Peppol Access Point, certified service providers like Tickstar (Pagero), Visma, Unifiedpost, or Storecove.
  4. Peppol Access Point delivers the invoice to the buyer’s ERP (PowerOffice Go, Tripletex, Visma, SAP, Dynamics) via the Peppol network.
  5. Status callbacks update Magento sales_invoice.

If you sell to Norwegian public bodies (kommuner, fylkeskommuner, staten, helseforetak) you must ship EHF. For B2B-only DTC selling to small Norwegian businesses, EHF is optional but appreciated. We wire the full pipeline.

What’s VOEC and how does EEA-not-EU affect my Norwegian store?

Norway is in the EEA (European Economic Area) but not the EU. That has two big checkout implications:

  • VOEC scheme (VAT On E-Commerce), foreign sellers (e.g. EU stores shipping into Norway) must register with the Norwegian Tax Administration and collect 25% MVA at checkout on consumer goods under NOK 3,000. The package then crosses the border tax-paid, no customs delay. Above NOK 3,000, full customs declaration + duties apply (slow, expensive, customer-paid).
  • Customs declaration above NOK 3,000, shipper must lodge a customs declaration; carrier (Posten / Bring / DHL) handles clearance and charges customs fees to the buyer. Often surprises customers with NOK 200-400 extra fees at the door, a common abandonment trigger.

For Magento stores selling into Norway from abroad: register for VOEC, collect MVA at checkout on items ≤NOK 3,000, ship VOEC-marked. For stores based in Norway selling abroad: collect EU VAT via IOSS (under €150) or distance-selling thresholds. We configure both flows in tax_zone rules + customer-group logic.

Can I run a single Magento for NO + DK + SE + FI cross-border Nordic?

Yes, Magento’s multi-store architecture handles the Nordic cluster well. Four countries, three currencies + EUR, shared catalogue:

  • One Magento backend, 4 stores, one each for NO (NOK / Bokmål + EN), DK (DKK / Danish + EN), SE (SEK / Swedish + EN), FI (EUR / Finnish + Swedish + EN). Country selector or country-detected redirect at .com.
  • Per-store VAT, NO MVA 25%, DK 25%, SE 25%, FI 24%. Each with reduced rates. Magento tax_zone rules per store.
  • Per-store payment methods, NO adds Vipps MobilePay + BankAxept; DK adds MobilePay + Dankort; SE adds Swish + Klarna-dominant; FI adds MobilePay + Klarna. Klarna runs across all four.
  • Per-store shipping, Posten / Bring NO, PostNord DK, PostNord SE, Posti FI. Cross-border via Bring (which spans all four).
  • EEA-vs-EU split, NO is EEA-not-EU (VOEC scheme for inbound, customs above NOK 3,000); DK/SE/FI are EU (intra-EU OSS thresholds). Tax + customs logic forks at the storefront level.
  • EHF in NO + Peppol BIS in DK/SE/FI, same Peppol network, slightly different national profiles. Same Access Point covers all.

Architecture decided in audit step.

How do I feed Magento products to Finn.no, Komplett, and Elkjøp?

Norwegian marketplaces are a real channel, not an afterthought. The three that matter:

  • Finn.no, Norway’s biggest classifieds + new-goods site (Schibsted-owned). Owns the Norwegian buyer-search habit the way eBay owns DE / UK. Feed via Finn Torget API or merchant-shop integration. Mandatory for Norway-only DTC discovery.
  • Komplett, Norway’s #1 electronics marketplace. Marketplace model where third-party sellers list under Komplett Markedsplass. Feed via Channable / Feedonomics or direct API.
  • Elkjøp, the dominant electronics + white-goods retailer (also Curry’s parent). Operates an emerging marketplace for select third-party sellers.
  • Amazon.no, launched 2020-2021, growing but still small in NO vs Amazon.se / .de. Feed via Channable.

Magento side: we wire Channable or Feedonomics as the feed manager, daily product / price / stock sync, per-marketplace mappings (Finn category trees differ from Magento), order-import back into Magento for unified fulfilment + return handling.

How does Datatilsynet + Norwegian GDPR + cookie banner work in Magento?

Norway adopted GDPR via the EEA agreement, the regulation is the same as EU GDPR, transposed nationally as Personopplysningsloven (the Personal Data Act, 2018) and enforced by Datatilsynet (the Norwegian DPA).

What that means for Magento:

  • Cookie consent, granular, per-purpose opt-in. No pre-ticked checkboxes. “Reject all” must be as easy as “Accept all”. Same standard as the rest of EEA, enforcement is solid but slightly less aggressive than CNIL (FR).
  • Lovlig grunnlag (legal basis), for every data process you need a documented legal basis: consent, contract, legitimate interest, etc. Magento’s customer_log, quote, sales_order retentions need explicit retention periods.
  • DSAR support, Norwegian customers can request access, deletion, portability. We wire Magento customer export + anonymisation workflows.
  • Hosting / data residency, Datatilsynet accepts EEA-region hosting (including AWS Stockholm, GreenMountain NO, Hetzner DE). Cross-border to non-EEA (e.g. US-region AWS) needs Standard Contractual Clauses + Transfer Impact Assessment post-Schrems II.

We ship Cookiebot / OneTrust / Coi (a Norwegian-native option) banner wired into Magento’s cookie API, banner copy reviewed against Datatilsynet guidance.

Do I need both Bokmål and Nynorsk on my Magento storefront?

Norwegian has two official written languages: Bokmål (used by ~85-90% of writers; close to Danish; default in Oslo, eastern + northern Norway) and Nynorsk (used by ~10-15%; Vestlandet / western Norway; based on rural dialects).

For most Magento stores: Bokmål is enough. It covers the Oslo + Bergen + Stavanger urban markets, and Nynorsk readers are bilingual in Bokmål. You’d add Nynorsk if:

  • You sell heavily into Vestlandet (Sogn og Fjordane, Møre og Romsdal, Hordaland) where Nynorsk is the schooled written form.
  • You sell to the public sector, the Mållova (Language Act) requires public bodies to use both languages, and your storefront / invoicing may need to mirror this for B2G procurement.
  • Brand positioning, some outdoor / heritage / regional brands deliberately ship Nynorsk to signal authenticity.

Magento side: each language is a store_view, full content translation. Cost roughly doubles the i18n effort vs Bokmål-only. We usually launch Bokmål-only on day one and add Nynorsk in Phase 2 if the data supports it.

How much does this cost, how long does it take, and what credentials do you have?

Two fixed price points + one custom:

  • Every project gets a fixed written quote. Send a short brief on WhatsApp and I reply within one working day with scope, price and timeline. Full Vipps + BankAxept + EHF + MVA + VOEC + Datatilsynet audit on your live store. Written remediation roadmap with hour estimates. Useful if you suspect issues but don’t know the scope.
  • Contact me for a quote. Full Magento 2 build or platform migration (Shopify / Mystore / Mageone → M2) for a Norwegian store. Vipps + BankAxept + Klarna + Nets + Stripe NO checkout, EHF / Peppol pipeline, Org.nr validation, MVA + VOEC config, Bokmål + English bilingual, hosting setup, 14 days post-launch coverage.
  • Enterprise (custom), quoted. Multi-country Nordic (NO + DK + SE + FI), Hyvä rebuild, full ERP integration (Tripletex / PowerOffice Go / Visma / SAP), B2B with deep Org.nr-gated catalogues.

Credentials: Adobe-Certified Magento 2 Developer + Adobe Certified Solution Specialist. 10+ years building Magento, 200+ stores shipped, Top-Rated Plus on Upwork, including Nordic DTC + B2B stores in NO + DK + SE. Net-30 invoicing available for established Norwegian AS / ENK businesses with valid Org.nr.

What’s different for an Oslo fashion boutique vs an outdoor retailer vs a seafood B2B exporter?

The Norwegian Magento build varies a lot by sector. Three real examples:

  • Oslo fashion boutique (NOK 5-50M DTC), Bokmål-only storefront, Vipps + Klarna + Stripe NO checkout (Klarna BNPL is 40-60% of fashion checkout), mobile-first Hyvä theme, Posten Bring home delivery + pickup-points, IG / TikTok-driven traffic. Marketplace feed to Finn.no + Amazon.no. Audit-tier or Build-tier project.
  • XXL / Sport 1-style outdoor retailer (NOK 50M+ DTC + retail), Multi-store NO + DK + SE + FI, Vipps + MobilePay + Swish + Klarna across countries, complex configurable products (size + colour + technical spec), seasonal release calendars, ERP integration to PowerOffice / Visma. Strong B2B side (gyms, schools, kommuner) with Org.nr-gated pricing. Build or Enterprise tier.
  • Stavanger seafood B2B exporter (NOK 100M+ B2B-only), Magento B2B (Adobe Commerce), Org.nr-gated catalogues, customer-specific pricing tiers, Net-30/60 with bank-collection, EHF mandatory (B2G + large-customer B2B), full Peppol Access Point integration, multi-currency NOK / EUR / USD invoicing, cold-chain shipping integrations to DHL Cold + Bring Frigo. Always Enterprise tier.

The audit step nails down which shape you fit and what the priorities are.

Reserve your slot

Tell me about your Norwegian Magento store

Send me a short WhatsApp message about the project. I reply within 24 business hours with a written quote in USD, a rough NOK figure, and a short note on what your Vipps, MVA and VOEC setup needs.

Message me on WhatsApp

No form to fill. Send me a quick message. I reply during 10 AM to 7 PM IST, Monday to Saturday.

Helpful to mention

  • Company
  • Current platform
  • Store URL
  • Annual GMV (NOK)
  • Category
  • Compliance focus

These are already in the message for you. Just add your answers.

Message me on WhatsApp

Or save my number: +91 84012 70422

Your hours, my overlap Online 10 AM to 7 PM IST Get my quote