Ecommerce for Business Central

Gung B2B Ecommerce Portal

Swedish order portal for customers, sales reps and agents, with a certified app on AppSource. Stock figures and customer-specific prices are pulled from Business Central during the session, and the order is created in the ERP immediately. Campaigns and product data live in Gung's own PIM.

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

What the solution is

Gung AB is a Swedish house delivering a B2B order portal and a product information system, and the vendor states that more than two hundred and thirty small and mid-sized companies in Sweden use the solution. For Business Central there is a certified app on Microsoft AppSource supporting both Essentials and Premium.

The solution is an order portal and not an open storefront. The users are customers, sales reps, agents, distributors and customer service, meaning people with a login and an agreement. If you need to sell to anonymous consumers, a different solution belongs on the list.

How the integration works

The integration is two-way and continuous. Stock balances and customer-specific prices are pulled from Business Central during the session, and an order placed in the portal is created in the ERP immediately, with no waiting and no manual step.

Because the app is certified and obtained from AppSource, there is version history and a release track to follow. That is the main reason the solution sits in the cell with a finished integration: you do not have to build data mappings to go live.

Only Business Central online is documented. Gung also integrates with other Nordic business systems, among them Business NXT, so the technique is not tied to one platform, but the on-premises question lacks a written answer.

Prices, discounts and agreements

Customer-specific prices come from Business Central and are pulled per session. That is a good model for an order portal, where the customer logs in and stays a while, and it gives a price that is right for that customer at that time.

Campaigns are the most important exception. Gung's own product information system handles prices, discounts, campaigns and product data and distributes them to the sales channels. That is why the solution carries the label for logic set up in two places: the agreed price comes from the ERP, while the campaign may come from Gung.

That is not a weakness in itself, but it is a decision to be made deliberately. If campaigns are created in both places, the question of which one wins arises, and that question is more expensive to answer in production than in a design meeting. Product bundles we have not been able to document and have set as not stated.

The order and the finance function

The order is created as a sales order in Business Central immediately. There is therefore no intermediate state where the order exists in the portal but not in the accounts, and partial shipments, back orders and credit memos follow the ERP's own processes.

Quotes and delivery status are part of the portal. For a sales department that is the feature removing the most routine work: the customer can see where the order is and can ask for a quote themselves.

Because the product is also used by sales reps and agents, ordering on the customer's behalf is a core capability rather than an addition. That is worth noting for a company with an internal sales department, where it is often the feature deciding whether the system gets used.

Who the solution fits

The solution fits a Nordic wholesaler or manufacturer where selling goes through known customers, sales reps and agents, and where the most important thing is getting orders in without phone and email. The built-in product information system is part of the answer to the item card in Business Central being thin.

It also fits if you need support in Swedish. The vendor is Swedish and the customer base is Swedish, and that makes a difference in the implementation that does not show up on a feature list.

The solution fits less well for consumer selling, for a brand with large design ambitions, or for a company outside the Nordics. This is not a storefront platform but an order portal, and that is a different kind of product.

What to settle before you decide

Pricing is not public. Our bands are an estimate with low confidence. Ask for prices on both the portal and the product information part, because they are two products, and ask whether the price follows the number of users.

Settle the division of labour on campaigns and prices between Business Central and Gung's product information system, and write it down. That is the one decision that can produce disagreeing prices later, and it is free to get right now.

Finally, ask for an answer on on-premises and for a named reference customer outside Sweden if you sit in another country. Two hundred and thirty Swedish customers is a strong maturity signal in Sweden and a weaker one elsewhere.

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 solutionGung B2B Ecommerce Portal
Maker of the ecommerce solutionGung AB
Integration to Business CentralGung PIM and B2B Order Portal for Business Central
Maker of the integrationGung AB
Solution typeAll in one, the same vendor for all three elements
Where the storefront livesSeparate platform
HostingSaaS
Vendor's home countrySE
MarketEurope
Centre of gravitySweden and the Nordics
How the integration is obtainedMicrosoft AppSource
Supported Business Central deploymentsBusiness Central online
Works against on-premisesNo
Storefront included in the solutionYes
Storefront and integration are the same productYes
Matrix cellFinished integration to a separate storefront
Logic labelThe logic is set up in two places
Other integrations to the same platform
Primary sourcegung.se
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 stretchedBounded
MethodsConfiguration in the product's own backend, Themes and templates
What it does to the commitmentThe vendor still covers it, the customisations are not on your account

Sales model

Open storefrontNo
Customer portalYes
NoteAn order portal behind a login. The users are customers, sales reps, agents and customer service.

Master data

ItemsSynchronised
CustomersSynchronised
InventoryRead live from Business Central
Product contentMaintained in the storefront
OrdersRead live from Business Central
PricesRead live from Business Central

Pricing logic and discounts

Customer-specific and agreed pricesExecuted in Business Central
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 kitsNot stated
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 termsNot stated
VAT and tax calculationExecuted in Business Central
Stock availability and delivery dateExecuted in Business Central

Order flow

Document created in Business CentralConfigurable
Reserves stockPartly
Partial shipmentsYes
Back ordersYes
Cancelled linesPartly
ReturnsPartly
Credit memoYes
Reconciling the payment provider's settlementNo
Fees and freightYes
VAT on the orderYes
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 minutes15
BatchingYes
Spread across several service principalsNo
CachingYes
Retry on a 429 responsePartly
Throttling handlingNot mentioned
API surfaces in Business CentralStandard API v2, Custom API pages

Product data and PIM

VariantsYes
Max variants per item
Units of measureYes
AttributesYes, broadly covered
Multilingual product dataYes
Digital assetsYes, broadly covered
Structured classificationPartly
Product configuratorNo
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, broadly covered

Limits

Max items
Max orders per day
Max concurrent users
Max customers times items
Max companies per storefront1
Max storefronts
Nature of the limitsUnknown
Sourcegung.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 modelPer user
Share of revenue in percent
Implementation modelFixed price against a template
Price per additional storefrontUnknown
Day-to-day work after go-liveSmall
Not included in the figuresinternal time, the product information part as a separate licence, user licences in Business Central
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: ConfidenceLow
Small: SourceAssessed against comparable solutions
Medium: Licence per yearEUR 20,000 to 60,000
Medium: Implementation, one-offEUR 10,000 to 40,000
Medium: Maintenance per yearUnder EUR 5,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
Large: Licence per yearEUR 20,000 to 60,000
Large: Implementation, one-offEUR 40,000 to 120,000
Large: Maintenance per yearUnder EUR 5,000
Large: Time to go live3 to 6 months
Large: Three-year cost of ownershipEUR 120,000 to 400,000
Large: ConfidenceLow
Large: SourceAssessed against comparable solutions

Functional requirements

SEO and indexabilityNo
Design and theme controlPartly
Content and landing pagesNo
Search and navigationYes
Ordering on the customer's behalfYes, broadly covered
Several storefronts from one Business CentralPartly
Multilingual frontendYes
Openness and extensionsPartly
AccessibilityPartly
Agent readabilityNo
PerformanceYes
Bulk editing, import and exportYes, broadly covered
Change log in the backendYes
An external search engine can be attachedNo
Facets on Business Central fieldsYes
MCP serverNo
Agentic checkout protocolNo
Control over AI crawlersNo
Hosted card fields, PCI scope kept outYes
Strong customer authentication and fraud screeningPartly
Consent managementPartly
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, broadly covered
Price list for print and downloadYes
Sales rep viewYes, broadly covered
Reordering from order historyYes, broadly covered
Several delivery addressesYes

Geography and compliance

Business Central localisationsalle
Several companies per storefrontPartly
Several environments per storefrontNo
CurrenciesYes
Languages in the frontendYes
Tax engineBusiness Central's standard
Named tax engines
E-invoicingPartly
Data locationEU
Payment methods per marketPartly
Who decides the VATBusiness Central decides the VAT
Prices with and without VAT per customerYes
VAT OSS and IOSSNo
Source of the currencyFollows the customer in Business Central

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 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