Ecommerce for Business Central

Litium + BRC Connect

Swedish platform covering both B2B and B2C with a product information system built in. The integration to Business Central comes from BrightCom, part of Exsitec. We have not been able to document the connector's mechanics, so the solution carries low confidence.

Maker of the ecommerce solution
Litium AB
Maker of the integration
BrightCom Solutions (Exsitec)
Last verified
2026-08-20

What the solution is

Litium is a Swedish commerce platform that has been in the market for a long time and holds a solid position in the Swedish mid-market. The platform covers both business and consumer selling from the same installation, and a product information system is part of the product rather than an add-on.

The integration to Business Central is BRC Connect from BrightCom Solutions, today part of the Exsitec group. Exsitec is an established Nordic consultancy, which in itself signals that there is an organisation behind it rather than an individual. We have not, however, been able to find technical documentation for the connector.

How the integration works

We cannot describe it precisely. A connector of this type normally moves items, prices, stock, customers and orders between the platform and Business Central on a schedule or continuously, but we have not been able to confirm the directions, the interval or the error handling for BRC Connect specifically.

Those fields therefore stand as not stated in the table below. That is not a claim that the solution cannot. It is a statement that we have not found material a buyer can lean on, and that it is therefore something to settle directly with the vendor.

A connector from a consultancy is a different kind of product from an app on AppSource. It is often closer to your needs, because the same house also does the implementation, and it often lacks the same public version history. Ask to have it clarified whether BRC Connect is a product with releases or a delivery built per customer. That is the question deciding which cell the solution actually belongs in.

Prices, discounts and agreements

Litium has its own price engine with customer-specific prices and price lists, and it is used in B2B setups. The agreed price can therefore live in the platform, in Business Central or in both, and what actually happens depends on how the connector is configured.

We have recorded customer-specific prices as a transferred result, because that is the ordinary model for a connector of this type to a platform with its own price engine. The other price rows stand as not stated.

Campaigns and bundles belong in Litium. That gives the label for logic set up in two places, and it makes the division of labour the most important decision in the implementation. Decide whether the ERP or the platform owns the agreed price, and write it down.

The order and the finance function

The order is written to Business Central, and from there it runs in the ERP's own flow with shipping and invoicing. That is the core of the integration's value.

Error handling is not documented. With a connector from a consultancy it is often solved sensibly in practice, but that is not the same as being described, and it belongs in an operating agreement with a name and a response time.

VAT is decided by the platform for open selling. If you sell in several Nordic countries, the VAT setup has to be maintained in Litium and agree with Business Central's.

Who the solution fits

The solution can fit a Swedish or Nordic company selling both to business and to consumers, and which wants platform, product information and implementation from Nordic hands. The built-in product information system is a real argument when the item card in Business Central is thin.

It also fits if you already work with Exsitec. Then the connector is part of an existing relationship, and the risk from the missing public documentation becomes smaller because responsibility is placed.

The solution fits less well if you need to read your way to a decision without talking to a vendor. There the solutions in the catalogue with open documentation are a better starting point.

What to settle before you decide

Ask whether BRC Connect is a product or a delivery. If there are releases, version numbers and an upgrade path, the solution belongs in the cell with a finished integration. If it is built per customer, it belongs in the cell where the company owns the configuration, and that changes both price and risk.

Ask to have the pricing logic described field by field. That is the largest gap in our research, and it is also what matters most to a B2B buyer.

The catalogue also names Maksimer's standard integration and Toxic EntityFlow as alternative routes from Litium to Business Central. If the answers from BrightCom are unsatisfactory, those two are worth looking at before ruling Litium out.

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 solutionLitium
Maker of the ecommerce solutionLitium AB
Integration to Business CentralBRC Connect
Maker of the integrationBrightCom Solutions (Exsitec)
Solution typePlatform plus connector, two vendors
Where the storefront livesSeparate platform
HostingSaaS
Vendor's home countrySE
MarketEurope
Centre of gravitySweden and the 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 cellFlexible integration, configured by the company
Logic labelThe logic is set up in two places
Other integrations to the same platformMaksimer standard integration, Toxic EntityFlow
Primary sourcebrightcom.se
Status of this entryDraft
Last verified2026-08-20
Schema version1.3.0-udkast

Maintenance

Keeps up with Business Central's releasesThe implementation partner
Keeps up with the platform's APIThe implementation partner
The company's own configurationBuilt per customer
Derived matrix cellFlexible integration, configured by the company

Customisation

How far the solution can be stretchedFar-reaching
MethodsField mapping in the integration, The platform's API, Development at the partner
What it does to the commitmentThe customisations are yours and can break at a Business Central release

Sales model

Open storefrontYes
Customer portalYes
NoteThe platform covers both sales models. Where the agreed price lives is decided by the connector's setup.

Master data

ItemsSynchronised
CustomersSynchronised
InventoryNot stated
Product contentMaintained in the storefront
OrdersSynchronised
PricesSynchronised

Pricing logic and discounts

Customer-specific and agreed pricesThe result is transferred
Tiered volume discountsNot stated
Campaign prices with a validity periodSet up in the storefront
Discount groups and trade agreementsNot stated
Product bundles and kitsSet up in the storefront
Line and invoice discountNot stated
Prices per unit and per currencyNot stated
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 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 freightYes
VAT on the orderPartly
Error handlingA log
When the customer is chargedAt checkout
Drop shipping via a purchase orderNot stated
Stock per locationNot stated
Consumer customers in Business CentralConfigurable

Integration mechanics

MethodMixed
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 measureYes
AttributesYes, broadly covered
Multilingual product dataYes, broadly covered
Digital assetsYes, broadly covered
Structured classificationYes
Product configuratorPartly
PIM built inYes, broadly covered
Separate PIM requiredNo
Variants mapped to Business Central's variant codesNot stated
Bundles resolved into Business Central linesNot stated
Blocked items and replacementsNot stated
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
Sourcebrightcom.se

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, Litium's own licence, frontend development, payment fees
Small: Licence per yearEUR 20,000 to 60,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: SourceAssessed against comparable solutions
Medium: Licence per yearEUR 20,000 to 60,000
Medium: Implementation, one-offEUR 120,000 to 400,000
Medium: Maintenance per yearEUR 20,000 to 60,000
Medium: Time to go live6 to 12 months
Medium: Three-year cost of ownershipOver EUR 400,000
Medium: ConfidenceLow
Medium: SourceAssessed against comparable solutions
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: SourceAssessed against comparable solutions

Functional requirements

SEO and indexabilityYes
Design and theme controlYes, broadly covered
Content and landing pagesYes
Search and navigationYes
Ordering on the customer's behalfYes
Several storefronts from one Business CentralYes
Multilingual frontendYes, broadly covered
Openness and extensionsYes
AccessibilityPartly
Agent readabilityPartly
PerformanceYes
Bulk editing, import and exportYes, broadly covered
Change log in the backendYes
An external search engine can be attachedYes
Facets on Business Central fieldsNo
MCP serverNo
Agentic checkout protocolNo
Control over AI crawlersPartly
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
Campaigns set up in the storefrontYes, broadly covered
Shipping choice and pickup pointsYes
WishlistsYes
Product feedsYes
Cart abandonment and email flowsYes

Customer portal only

Account hierarchy with buyers and approversYes
Approval flow with amount limitsYes
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 storefrontNot stated
Several environments per storefrontNot stated
CurrenciesYes
Languages in the frontendYes, broadly covered
Tax engineNone
Named tax engines
E-invoicingNot stated
Data locationEU
Payment methods per marketYes
Who decides the VATThe storefront decides the VAT
Prices with and without VAT per customerYes
VAT OSS and IOSSNot stated
Source of the currencyFollows the storefront or the country

Vendor relationship and exit

Support languagessv, en
Support geographyeu
Partner coverageSE, NO, DK, FI
SLAContractual
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 geographyYes