Ecommerce for Business Central

OpenCart + Business Central connector

Open source storefront with marginal reach in the northern European market, connected to Business Central by a connector from OpenCart's own marketplace. We have been able to document neither the mechanics, the version history nor a reference customer. The solution is in the catalogue for completeness.

Maker of the ecommerce solution
OpenCart Ltd.
Maker of the integration
opencartcity
Last verified
2026-08-20

What the solution is

OpenCart is an open source commerce platform that has existed for a long time and is easy to get started with. It is widespread in parts of Asia and eastern Europe, while its reach in northern Europe is marginal, which in practice means there are few local agencies and few local developers to get help from.

The integration to Business Central is a connector from OpenCart's own marketplace, published by a single publisher. We have not been able to find technical documentation, a version history, a support channel with a stated language or a named reference customer. None of the four maturity signs this catalogue measures could be verified.

How the integration works

We cannot describe it, and we will not guess. A connector of this type normally works against Business Central's standard API from the outside and moves items, customers and orders on a schedule, but none of that is confirmed for this product specifically.

Almost all mechanics fields in the table below therefore stand as not stated. That is not a judgement on the product. It is a statement that not enough public material exists to give an assessment a buyer can lean on.

It is at the same time the most important fact on this page. An integration between storefront and accounts has to be maintainable when Business Central ships twice a year. Without a version history and a support channel, nobody has taken on that responsibility, and that is a risk larger than a missing feature.

Prices, discounts and agreements

OpenCart has customer groups with their own prices, and the pricing logic lives in the storefront. We have found no documentation that agreed prices are fetched from Business Central, and the solution therefore carries the label for logic set up in two places.

There is no customer portal in the sense this catalogue uses the word. Customer groups are not the same as agreements, credit limits and approval flows, and if you need to sell to business on agreed terms, this is not the solution.

For a pure consumer store with one price list the limitation is of no practical significance, and there OpenCart can be a sensible and cheap choice.

The order and the finance function

The purpose of the integration is getting orders into Business Central automatically. That is the value worth paying for, and it is what a demo has to show.

Everything after the order is handled in Business Central. We have not been able to document whether partial shipments, returns or credit memos are reflected back into the store, and they therefore stand as not stated.

VAT is decided by the storefront, and a multi-country VAT setup has to be maintained there.

Who the solution fits

The solution can fit a company already running OpenCart with a development team able to take responsibility for the integration itself. If the source code is available and the skills are there, that is a viable route.

It can also fit as a first step for a very small store where the alternative is keying orders in by hand and the budget does not stretch further.

The solution does not fit if you are choosing a platform from scratch. With marginal reach in northern Europe, no verified maturity signs and no documentation of the integration, there is no argument for choosing it over the other solutions in the catalogue.

What to settle before you decide

Ask for the four things the catalogue measures maturity on: a released version with history, documentation naming a current Business Central version, a named reference customer, and a support channel with a language and a time zone. If those four cannot be delivered, the answer is probably given.

Our medium and large scenarios stand as not served for the large one and with low confidence for the medium one. We cannot defend pricing a setup with ten thousand items and fifteen hundred customers on a foundation we do not know.

Consider spending the time on a different solution. That is an unusual thing to write on a product page, but the catalogue exists to help with a decision, and here our research points in one direction.

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 solutionOpenCart
Maker of the ecommerce solutionOpenCart Ltd.
Integration to Business CentralOpenCart Business Central Connector
Maker of the integrationopencartcity
Solution typePlatform plus connector, two vendors
Where the storefront livesSeparate platform
HostingSelf-hosted
Vendor's home countryGB
MarketEurope, USA
Centre of gravity
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 sourceopencart.com
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
MethodsPlugins and modules for the platform, Access to the source code
What it does to the commitmentThe customisations are yours and can break at a Business Central release

Sales model

Open storefrontYes
Customer portalNo
NoteCustomer groups exist, but not a portal with agreements, credit limits and approvals.

Master data

ItemsSynchronised
CustomersNot stated
InventoryNot stated
Product contentMaintained in the storefront
OrdersSynchronised
PricesMaintained in the storefront

Pricing logic and discounts

Customer-specific and agreed pricesSet up in the storefront
Tiered volume discountsSet up in the storefront
Campaign prices with a validity periodSet up in the storefront
Discount groups and trade agreementsNot stated
Product bundles and kitsNot stated
Line and invoice discountNot stated
Prices per unit and per currencyNot stated
Customer-specific assortmentNot stated
Credit limit and payment termsNot supported
VAT and tax calculationSet up in the storefront
Stock availability and delivery dateNot stated

Order flow

Document created in Business CentralSales order
Reserves stockNo
Partial shipmentsNot stated
Back ordersNot stated
Cancelled linesNot stated
ReturnsNot stated
Credit memoNot stated
Reconciling the payment provider's settlementNo
Fees and freightNot stated
VAT on the orderNot stated
Error handlingA log
When the customer is chargedAt checkout
Drop shipping via a purchase orderNo
Stock per locationNot stated
Consumer customers in Business CentralA single collective customer

Integration mechanics

MethodPolling
Polling interval in minutes
BatchingNot stated
Spread across several service principalsNo
CachingNot stated
Retry on a 429 responseNot stated
Throttling handlingNot mentioned
API surfaces in Business CentralStandard API v2

Product data and PIM

VariantsYes
Max variants per item
Units of measureNo
AttributesYes
Multilingual product dataYes
Digital assetsPartly
Structured classificationNo
Product configuratorNo
PIM built inNo
Separate PIM requiredRecommended
Variants mapped to Business Central's variant codesNot stated
Bundles resolved into Business Central linesNo
Blocked items and replacementsNot stated
The customer's own item numbersNo

Limits

Max items
Max orders per day
Max concurrent users
Max customers times items
Max companies per storefront1
Max storefronts1
Nature of the limitsUnknown
Sourceopencart.com

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 storefrontIncluded
Day-to-day work after go-liveLarge
Not included in the figuresinternal time, hosting and operations, security updates, maintenance of the integration
Small: Licence per yearUnder EUR 5,000
Small: Implementation, one-offEUR 10,000 to 40,000
Small: Maintenance per yearUnder EUR 5,000
Small: Time to go live1 to 3 months
Small: Three-year cost of ownershipEUR 40,000 to 120,000
Small: ConfidenceLow
Small: SourceAssessed against comparable solutions
Medium: Licence per yearUnder EUR 5,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: SourceAssessed against comparable solutions
Scenario: LargeThe solution does not serve this scenario

Functional requirements

SEO and indexabilityPartly
Design and theme controlYes
Content and landing pagesPartly
Search and navigationPartly
Ordering on the customer's behalfNo
Several storefronts from one Business CentralYes
Multilingual frontendYes
Openness and extensionsYes
AccessibilityNo
Agent readabilityNo
PerformancePartly
Bulk editing, import and exportPartly
Change log in the backendNo
An external search engine can be attachedNo
Facets on Business Central fieldsNo
MCP serverNo
Agentic checkout protocolNo
Control over AI crawlersNo
Hosted card fields, PCI scope kept outPartly
Strong customer authentication and fraud screeningPartly
Consent managementPartly
Data protection and processing agreementPartly

Open storefront only

Guest checkoutYes
Card paymentYes
Campaigns set up in the storefrontYes
Gift cardsYes
Product reviewsYes
WishlistsYes

Customer portal only

Not relevant. This solution has no customer portal.

Geography and compliance

Business Central localisationsalle
Several companies per storefrontNo
Several environments per storefrontNo
CurrenciesYes
Languages in the frontendYes
Tax engineNone
Named tax engines
E-invoicingNo
Data locationChosen at setup
Payment methods per marketPartly
Who decides the VATThe storefront decides the VAT
Prices with and without VAT per customerPartly
VAT OSS and IOSSNo
Source of the currencyFollows the storefront or the country

Vendor relationship and exit

Support languagesen
Support geographyglobal
Partner coverage
SLANone
Data ownershipThe customer
Data can be exportedYes
The frontend can be taken along in a moveYes

Maturity

MaturityUnverified
A released version with version history within twelve monthsNo
Public documentation referencing a current Business Central versionNo
At least one named reference customerNo
A stated support channel with language and geographyNo