Ecommerce for Business Central

Norce Commerce + Junipeer connector

Swedish composable commerce platform with one of the strongest product information systems in the Nordics built in. The integration is Junipeer's prebuilt flow to Business Central, where orders, customers, items and stock synchronise continuously. Prices are transferred, campaigns are set up in the platform.

Maker of the ecommerce solution
Norce AB
Maker of the integration
Junipeer
Last verified
2026-08-20

What the solution is

Norce Commerce is a Swedish commerce platform describing itself as composable, meaning built from services that can be combined rather than as a closed product. The platform is strong in the Nordic mid-market and is used by both retailers and manufacturers.

What separates Norce from the other Nordic platforms in the catalogue is the product information part. It is among the strongest in the Nordics, and for a company with many item numbers, many attributes and several languages it is often the argument that decides the choice. The item card in Business Central is thin, and here the answer is part of the platform rather than a separate purchase.

How the integration works

The integration comes from Junipeer, a Nordic integration platform with prebuilt flows. Junipeer synchronises items, customers, orders and stock balances between Norce and Business Central in real time, and the same platform also serves Fortnox, SAP Business One, Visma.net and a growing range of other ERP systems.

Setup consists of field mapping and a test run, and the vendor states a quarter of an hour as the time required. That is a marketing figure, but the distance to a traditional integration project is real, and it is why the solution belongs in this catalogue rather than on the list of rejected candidates.

There is a middleware layer to operate. We have found no documentation of retry logic on failure or of a monitoring view, and that is worth asking about. Only Business Central online is documented.

Prices, discounts and agreements

Prices come from Business Central and are transferred to Norce. The agreed price is therefore the ERP's, but it is not recalculated when the customer opens the page. It is a transfer model, and the scaling trap of customers times items applies.

Campaigns, quantity tiers and bundles belong in Norce. The platform has its own price engine, and for a retailer with a large assortment that is a strength rather than a gap. It is at the same time the reason for the label about logic set up in two places, and it makes the division of labour a decision to be made and written down.

If you have agreed prices on thousands of customers, it is worth asking for a figure on how many price rows Junipeer moves, and how long a full run takes. That is the one technical risk worth measuring before signing.

The order and the finance function

The order is written to Business Central as a sales order, and from there it runs in the ERP's own flow. Partial shipments, back orders and credit memos are therefore Business Central's responsibility.

Because there is an integration layer, there is a place outside both systems where an order can sit. Agree who checks, and what triggers a message. With the order volume a Nordic retailer typically has, an unnoticed failure becomes expensive within a day.

VAT is decided by Norce. If you sell to consumers in several countries, it is the platform's VAT setup that carries it, and OSS should have a concrete answer rather than an assumption.

Who the solution fits

The solution fits a Nordic retailer or manufacturer with a large and complex assortment, where product data is the heavy part of the job. Getting both a commerce platform and a product information system in the same licence saves a separate project with its own licence and its own implementation.

It also fits if you sell both to consumers and to business from the same catalogue. The platform covers both, and not everyone in the catalogue does that without add-ons.

The solution fits less well if you want a finished store without development work, or if the pricing logic has to come from Business Central in real time. In both cases other solutions in the catalogue sit closer to the wish.

What to settle before you decide

Junipeer's price starts at 399 euro a month and is public. Norce's own licence is not, and the frontend work is the largest uncertainty in the budget. Our bands carry low confidence and cover all three items.

Ask to have the product information part demonstrated on your own items, not on a demo catalogue. That is the part that is the main argument for the solution, and it is also the part hardest to judge from a feature list.

Ask for an answer on what happens to a failed order, and ask to see the monitoring. That is the weakest documented part of Junipeer, and it is the easiest to have explained.

All data on this solution

Every field in the schema, as it stands in the catalogue. A dash means we have no figure, which is not the same as a no.

Basics

Ecommerce solutionNorce Commerce
Maker of the ecommerce solutionNorce AB
Integration to Business CentralJunipeer Business Central connector
Maker of the integrationJunipeer
Solution typePlatform plus connector, two vendors
Where the storefront livesSeparate platform
HostingSaaS
Vendor's home countrySE
MarketEurope
Centre of gravityThe Nordics
How the integration is obtainedExternal platform
Supported Business Central deploymentsBusiness Central online
Works against on-premisesNo
Storefront included in the solutionYes
Storefront and integration are the same productNo
Matrix cellFinished integration to a separate storefront
Logic labelThe logic is set up in two places
Other integrations to the same platform
Primary sourcejunipeer.io
Status of this entryDraft
Last verified2026-08-20
Schema version1.3.0-udkast

Maintenance

Keeps up with Business Central's releasesThe vendor
Keeps up with the platform's APIThe vendor
The company's own configurationStandard setup
Derived matrix cellFinished integration to a separate storefront

Customisation

How far the solution can be stretchedFull
MethodsYour own frontend, headless, Field mapping in the integration, The platform's API
What it does to the commitmentThe customisations are yours and can break at a Business Central release

Sales model

Open storefrontYes
Customer portalYes
NoteBoth consumer selling and business selling from the same catalogue and the same product information section.

Master data

ItemsSynchronised
CustomersSynchronised
InventorySynchronised
Product contentMaintained in the storefront
OrdersSynchronised
PricesSynchronised

Pricing logic and discounts

Customer-specific and agreed pricesThe result is transferred
Tiered volume discountsSet up in the storefront
Campaign prices with a validity periodSet up in the storefront
Discount groups and trade agreementsSet up in the storefront
Product bundles and kitsSet up in the storefront
Line and invoice discountSet up in the storefront
Prices per unit and per currencyThe result is transferred
Customer-specific assortmentSet up in the storefront
Credit limit and payment termsNot stated
VAT and tax calculationSet up in the storefront
Stock availability and delivery dateThe result is transferred

Order flow

Document created in Business CentralSales order
Reserves stockNo
Partial shipmentsYes
Back ordersYes
Cancelled linesPartly
ReturnsYes
Credit memoYes
Reconciling the payment provider's settlementNo
Fees and freightYes
VAT on the orderPartly
Error handlingA log
When the customer is chargedAt checkout
Drop shipping via a purchase orderYes
Stock per locationYes
Consumer customers in Business CentralConfigurable

Integration mechanics

MethodMixed
Polling interval in minutes5
BatchingYes
Spread across several service principalsNo
CachingYes
Retry on a 429 responseNot stated
Throttling handlingNot mentioned
API surfaces in Business CentralStandard API v2, External middleware

Product data and PIM

VariantsYes, broadly covered
Max variants per item
Units of measureYes
AttributesYes, broadly covered
Multilingual product dataYes, broadly covered
Digital assetsYes, broadly covered
Structured classificationYes, broadly covered
Product configuratorYes
PIM built inYes, broadly covered
Separate PIM requiredNo
Variants mapped to Business Central's variant codesYes
Bundles resolved into Business Central linesPartly
Blocked items and replacementsYes
The customer's own item numbersYes

Limits

Max items
Max orders per day
Max concurrent users
Max customers times items
Max companies per storefront
Max storefronts
Nature of the limitsUnknown
Sourcejunipeer.io

Cost

The bands are set in euro and priced against three fixed reference scenarios. They cover licence, implementation and maintenance, and they do not cover your own time.

Pricing modelFixed price
Share of revenue in percent
Implementation modelTime and materials
Price per additional storefrontUnknown
Day-to-day work after go-liveLarge
Not included in the figuresinternal time, development and maintenance of the frontend, Norce's own licence, payment fees
Small: Licence per yearEUR 5,000 to 20,000
Small: Implementation, one-offEUR 40,000 to 120,000
Small: Maintenance per yearEUR 5,000 to 20,000
Small: Time to go live3 to 6 months
Small: Three-year cost of ownershipEUR 120,000 to 400,000
Small: ConfidenceLow
Small: Sourcejunipeer.io
Medium: Licence per yearEUR 20,000 to 60,000
Medium: Implementation, one-offEUR 40,000 to 120,000
Medium: Maintenance per yearEUR 5,000 to 20,000
Medium: Time to go live3 to 6 months
Medium: Three-year cost of ownershipEUR 120,000 to 400,000
Medium: ConfidenceLow
Medium: Sourcejunipeer.io
Large: Licence per yearEUR 60,000 to 150,000
Large: Implementation, one-offEUR 120,000 to 400,000
Large: Maintenance per yearEUR 20,000 to 60,000
Large: Time to go live6 to 12 months
Large: Three-year cost of ownershipOver EUR 400,000
Large: ConfidenceLow
Large: Sourcejunipeer.io

Functional requirements

SEO and indexabilityYes
Design and theme controlYes, broadly covered
Content and landing pagesYes
Search and navigationYes, broadly covered
Ordering on the customer's behalfYes
Several storefronts from one Business CentralYes, broadly covered
Multilingual frontendYes, broadly covered
Openness and extensionsYes, broadly covered
AccessibilityPartly
Agent readabilityYes
PerformanceYes
Bulk editing, import and exportYes, broadly covered
Change log in the backendYes
An external search engine can be attachedYes, broadly covered
Facets on Business Central fieldsNo
MCP serverNo
Agentic checkout protocolNo
Control over AI crawlersYes
Hosted card fields, PCI scope kept outYes
Strong customer authentication and fraud screeningYes
Consent managementYes
Data protection and processing agreementYes

Open storefront only

Guest checkoutYes
Card paymentYes, broadly covered
Buy now, pay laterYes, broadly covered
Campaigns set up in the storefrontYes, broadly covered
Shipping choice and pickup pointsYes, broadly covered
Gift cardsYes
Order status without an accountYes
Product reviewsYes
WishlistsYes
Marketing platformYes
RecommendationsYes
Product feedsYes, broadly covered
Right of withdrawal and returns portalYes
Cart abandonment and email flowsYes
Marketplace channelsYes

Customer portal only

Account hierarchy with buyers and approversYes
Approval flow with amount limitsPartly
Invoice payment and open entriesYes
Quotes and requestsYes
Price list for print and downloadPartly
Sales rep viewYes
Reordering from order historyYes
Several delivery addressesYes

Geography and compliance

Business Central localisationsalle
Several companies per storefrontYes
Several environments per storefrontPartly
CurrenciesYes, broadly covered
Languages in the frontendYes, broadly covered
Tax engineNone
Named tax engines
E-invoicingPartly
Data locationEU
Payment methods per marketYes, broadly covered
Who decides the VATThe storefront decides the VAT
Prices with and without VAT per customerYes
VAT OSS and IOSSYes
Source of the currencyFollows the storefront or the country

Vendor relationship and exit

Support languagesen, sv
Support geographyeu
Partner coverageSE, NO, DK, FI
SLAContractual
Data ownershipThe customer
Data can be exportedYes, broadly covered
The frontend can be taken along in a moveYes

Maturity

MaturityEstablished
A released version with version history within twelve monthsYes
Public documentation referencing a current Business Central versionNo
At least one named reference customerYes
A stated support channel with language and geographyYes