Ecommerce for Business Central

Centra + Junipeer connector

Swedish headless platform built for fashion brands, with a separate wholesale module alongside the consumer store. The integration is Junipeer's prebuilt flow to Business Central, which can be set up in a quarter of an hour and costs from 399 euro a month. The frontend has to be built.

Maker of the ecommerce solution
Centra AB
Maker of the integration
Junipeer
Last verified
2026-09-11

What the solution is

Centra is a Swedish commerce platform built for fashion and lifestyle brands. It is a headless platform, meaning it delivers data and commerce logic through APIs while the frontend the customer sees is built separately. Centra's hallmark is that consumer selling and wholesale are two sides of the same product, and that the wholesale part is built for the fashion industry's seasonal orders with showroom and order taking.

The integration to Business Central comes from Junipeer, a Nordic integration platform with prebuilt flows to a range of ERP systems. Other routes from Centra to Business Central exist, among them connect2Centra from Codeunit, Patchworks and HighCohesion, and Junipeer is chosen here as the most widely used one.

How the integration works

Junipeer is an integration platform with prebuilt flows rather than a tool you have to build in. Setup consists of field mapping and a test run, and the vendor states a quarter of an hour as the time it takes. That is a different kind of promise from the traditional iPaaS products, where the integration has to be built, and it is why the solution belongs in this catalogue.

The directions are documented and broad. From Business Central to Centra go orders, articles, prices, stock, customers, companies and shipments. From Centra to Business Central go articles, orders, refunds and customers. Synchronisation is described as near real time and continuous.

There is a middleware layer to operate, and that is the most important operational fact. Junipeer writes that logs can be reviewed before going live, but we have found no documentation of retry logic or of a monitoring view. Ask to see what happens to an order that fails at three in the morning. Only Business Central online is documented.

Prices, discounts and agreements

Prices are transferred from Business Central to Centra. The agreed price therefore comes from the ERP, and that is the mechanism this site measures. It is a transfer model, so the price is right until the next run.

Campaigns and bundles belong in Centra. For a fashion brand that is the right division of labour, because campaigns in that trade are visual and fast, and because they can rarely be expressed as a price in an ERP. It is at the same time the reason for the label about logic set up in two places.

The wholesale part is worth a closer look if you sell to retailers. Centra's wholesale module works with seasonal collections, pre-orders and delivery windows, and that is a logic Business Central has no concepts for. Ask to see how a pre-order with a delivery window ends up as a document in the ERP, because that is where this combination stands or falls.

The order and the finance function

The order is written to Business Central, and refunds come back through the same flow. That refunds are named explicitly in the integration is worth noting, because return rates in fashion are high, and a return that does not reach the accounts automatically quickly becomes a full-time job.

Shipments go from Business Central to Centra, so the customer can see what has been sent. That is the piece of information customer service otherwise spends the most time on.

VAT is decided by Centra. If you sell to consumers in several countries, it is Centra's VAT setup and possibly an external tax engine that has to carry it, not Business Central's setup.

Who the solution fits

The solution fits a fashion or lifestyle brand in the Nordics selling both direct to consumers and to retailers, and which has or can get a development team for the frontend. That is a narrow profile, but within it there are not many better choices.

It also fits if you want an integration that can be set up quickly without an integration project. Junipeer's promise of a quarter of an hour should probably be taken with a pinch of salt, but the distance to a traditional iPaaS project is real.

The solution does not fit if you want a finished store. Centra is headless, and the frontend is a development effort of its own with its own price and its own maintenance. That is the largest item in the budget, and it is not part of the platform's licence.

What to settle before you decide

Junipeer's price starts at 399 euro a month with no setup fee, and that figure is public. Centra's own licence is not, and the frontend development is the largest uncertainty. Our bands reflect all three items and carry low confidence.

Ask to have the frontend priced separately, both to build it and to maintain it. A headless platform moves work from licence to development, and that is a different kind of cost from a licence: it does not disappear when the project ends.

Settle how the wholesale part's seasonal orders should look in Business Central. That is the one question a feature list cannot answer, and it is worth spending half a meeting on with someone who knows both systems.

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 solutionCentra
Maker of the ecommerce solutionCentra 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 platformconnect2Centra (Codeunit AB), Patchworks, HighCohesion
Primary sourcejunipeer.io
Status of this entryDraft
Last verified2026-09-11
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
NoteThe wholesale module is built for seasonal orders and pre-orders rather than for ongoing repeat buying.

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, broadly covered
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 orderPartly
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 measurePartly
AttributesYes, broadly covered
Multilingual product dataYes, broadly covered
Digital assetsYes, broadly covered
Structured classificationPartly
Product configuratorNo
PIM built inYes
Separate PIM requiredNo
Variants mapped to Business Central's variant codesYes
Bundles resolved into Business Central linesPartly
Blocked items and replacementsPartly
The customer's own item numbersPartly

Limits

Max items
Max orders per day
Max concurrent users
Max customers times items
Max companies per storefront1
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, Centra's own licence, payment fees, an external tax engine
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 pagesPartly
Search and navigationYes
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, broadly covered
Bulk editing, import and exportYes
Change log in the backendPartly
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, broadly covered
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
WishlistsYes
Marketing platformYes
Product feedsYes
Right of withdrawal and returns portalYes, broadly covered
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 downloadYes
Sales rep viewYes, broadly covered
Reordering from order historyYes
Several delivery addressesYes

Geography and compliance

Business Central localisationsalle
Several companies per storefrontPartly
Several environments per storefrontNo
CurrenciesYes, broadly covered
Languages in the frontendYes, broadly covered
Tax engineNone
Named tax engines
E-invoicingNo
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, DK, NO, FI, UK
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