Ecommerce for Business Central

SparkLayer B2B + Tinx SparkLayer Connector

A B2B layer placed on top of a Shopify store, connected to Business Central by Tinx-IT. The customer's agreed prices and terms come from the ERP, stock figures update within a minute, and the order is assigned to the correct existing B2B customer. The connector price is public.

Maker of the ecommerce solution
SparkLayer Ltd.
Maker of the integration
Tinx-IT B.V.
Last verified
2026-08-20

What the solution is

SparkLayer is not a storefront platform. It is a B2B layer placed on top of a store you already have, most often a Shopify store, giving it the features a business customer needs: login, their own prices, quantity entry, reordering and payment terms.

That makes the solution an unusual construction in the catalogue. You have three layers that have to fit together: the storefront, the B2B layer and Business Central. In return it solves a concrete and common problem, namely that Shopify is an excellent consumer store and a mediocre B2B portal, and that Shopify's own B2B requires the Plus subscription.

The integration is the Tinx SparkLayer Connector from Tinx-IT in the Netherlands, obtained from Microsoft AppSource. The same house stands behind the WooCommerce connector in this catalogue.

How the integration works

Product information synchronises automatically from Business Central to the storefront, and stock figures update within one minute. That last part is a concrete figure rather than a promise of real time, and it is worth noting: one minute is good enough for most B2B situations and documented enough to be held up against reality.

B2B orders from the storefront are imported automatically into Business Central and assigned to the correct existing B2B customer. That is the mechanism that most often fails in a Shopify setup, where a business order ends up as a new anonymous customer, and it is a real reason to choose this route over Shopify's own connector.

Like Tinx's other apps, the connector runs inside Business Central with no external servers. Only Business Central online is documented. Note that the Shopify side still has the documented limit of one store per Business Central company if you use Microsoft's connector alongside.

Prices, discounts and agreements

This is where the solution earns its place. Customer-specific price agreements and terms come from Business Central and are shown in the SparkLayer layer. The business customer sees their own price, and that price is the ERP's.

It is a transfer model, so the price is right until the next run, and the scaling trap of customers times items applies in principle. With an update interval of minutes, the risk of an outdated price is small in practice.

Campaigns and bundles belong in Shopify. That is the reason for the label about logic set up in two places, and for most it is an advantage: consumer campaigns can be run freely in Shopify while the business price comes from the ERP. It is a tidy division of labour if it has been decided.

The order and the finance function

The order is created in Business Central on the correct customer, and from there it runs in the ERP's own flow. Because the customer is right from the outset, credit limits, payment terms and statements work as they should, and that is often what a sales department misses in a pure Shopify setup.

Partial shipments, back orders and credit memos are handled in Business Central. VAT is decided by Shopify on open selling, and for business selling it should be settled concretely how VAT exemption on export is handled.

Reconciling the Shopify Payments settlement against the general ledger is still a separate job.

Who the solution fits

The solution fits a company that already has a Shopify store for consumers and needs to add business selling with agreed prices without changing platform. That is a very common situation, and it is what this combination is built for.

It also fits if the alternative is Shopify Plus. Plus costs considerably more per year than SparkLayer and the Tinx connector combined, and if B2B is the only thing you need from Plus, the calculation is worth doing.

The solution fits less well if you want as few vendors as possible. There are three parties in this setup, and three parties means three contracts, three support channels and three places a change can break something.

What to settle before you decide

Tinx's prices are public and fixed, starting around three hundred euro a month for the connector line and with no per-transaction or per-user fee. Ask to have that confirmed for the SparkLayer edition specifically, because the public figures cover the Shopify connector.

Count SparkLayer's own subscription and Shopify's subscription as well. The connector is the smallest of the three items, and a comparison looking only at it comes out wrong.

Ask to see a business order go all the way: from login in SparkLayer through a price from Business Central to a sales order on the correct customer with the correct credit limit. If that can be demonstrated in half an hour, the solution has shown what it needs to.

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 solutionSparkLayer B2B
Maker of the ecommerce solutionSparkLayer Ltd.
Integration to Business CentralTinx SparkLayer Connector
Maker of the integrationTinx-IT B.V.
Solution typeA B2B layer on top of a platform, plus a connector
Where the storefront livesSeparate platform
HostingSaaS
Vendor's home countryGB
MarketEurope, USA
Centre of gravity
How the integration is obtainedMicrosoft AppSource
Supported Business Central deploymentsBusiness Central online
Works against on-premisesNo
Storefront included in the solutionNo
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 sourcetinx-it.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 stretchedFar-reaching
MethodsConfiguration in the product's own backend, Themes and templates, Field mapping in the integration
What it does to the commitmentThe customisations are yours and can break at a Business Central release

Sales model

Open storefrontNo
Customer portalYes
NoteSparkLayer delivers the B2B side. The open webshop comes from the underlying platform and is not part of this solution.

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 discountsThe result is transferred
Campaign prices with a validity periodSet up in the storefront
Discount groups and trade agreementsThe result is transferred
Product bundles and kitsSet up in the storefront
Line and invoice discountThe result is transferred
Prices per unit and per currencyThe result is transferred
Customer-specific assortmentThe result is transferred
Credit limit and payment termsThe result is transferred
VAT and tax calculationSet up in the storefront
Stock availability and delivery dateThe result is transferred

Order flow

Document created in Business CentralConfigurable
Reserves stockNo
Partial shipmentsYes
Back ordersYes
Cancelled linesPartly
ReturnsPartly
Credit memoYes
Reconciling the payment provider's settlementNo
Fees and freightYes
VAT on the orderPartly
Error handlingQueue with a notification to a person
When the customer is chargedOn shipment
Drop shipping via a purchase orderPartly
Stock per locationYes
Consumer customers in Business CentralOne customer card per person

Integration mechanics

MethodMixed
Polling interval in minutes1
BatchingYes
Spread across several service principalsNo
CachingPartly
Retry on a 429 responseYes
Throttling handlingMentioned
API surfaces in Business CentralStandard API v2, Custom API pages

Product data and PIM

VariantsYes
Max variants per item2,048
Units of measureYes
AttributesYes
Multilingual product dataPartly
Digital assetsYes, broadly covered
Structured classificationNo
Product configuratorNo
PIM built inPartly
Separate PIM requiredRecommended
Variants mapped to Business Central's variant codesYes
Bundles resolved into Business Central linesPartly
Blocked items and replacementsPartly
The customer's own item numbersYes

Limits

Max items
Max orders per day
Max concurrent users
Max customers times items
Max companies per storefront1
Max storefronts1
Nature of the limitsVendor statement
Sourcetinx-it.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 modelFixed price against a template
Price per additional storefrontExtra licence per storefront
Day-to-day work after go-liveMedium
Not included in the figuresinternal time, SparkLayer's own subscription, Shopify's subscription, payment fees, reconciliation of payment settlements
Small: Licence per yearEUR 5,000 to 20,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: ConfidenceMedium
Small: Sourcetinx-it.com
Medium: Licence per yearEUR 20,000 to 60,000
Medium: Implementation, one-offEUR 10,000 to 40,000
Medium: Maintenance per yearEUR 5,000 to 20,000
Medium: Time to go live1 to 3 months
Medium: Three-year cost of ownershipEUR 120,000 to 400,000
Medium: ConfidenceMedium
Medium: Sourcetinx-it.com
Large: Licence per yearEUR 60,000 to 150,000
Large: Implementation, one-offEUR 40,000 to 120,000
Large: Maintenance per yearEUR 5,000 to 20,000
Large: Time to go live3 to 6 months
Large: Three-year cost of ownershipOver EUR 400,000
Large: ConfidenceLow
Large: Sourcetinx-it.com

Functional requirements

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

Open storefront only

Not relevant. This solution is not sold as an open storefront.

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
Reordering from order historyYes, broadly covered
Several delivery addressesYes

Geography and compliance

Business Central localisationsalle
Several companies per storefrontNo
Several environments per storefrontNo
CurrenciesYes, broadly covered
Languages in the frontendYes, broadly covered
Tax engineExternal tax engine
Named tax enginesShopify Tax, Avalara
E-invoicingNo
Data locationGlobal
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 customer in Business Central

Vendor relationship and exit

Support languagesen, nl
Support geographyeu, uk
Partner coverageNL, BE, DE, UK, DK
SLAContractual
Data ownershipThe customer
Data can be exportedYes, broadly covered
The frontend can be taken along in a moveNo

Maturity

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