Websites11 min read

Syncing Sage 100 customer prices with a B2B portal: cost and pitfalls 2026

Mohamed Bah·Fondateur, Kolonell
October 15, 2026
Share:
Syncing Sage 100 customer prices with a B2B portal: cost and pitfalls 2026

Syncing Sage 100 customer prices with a B2B portal: cost and pitfalls 2026

Websites

The verdict in three sentences

If your customers buy at list price with a simple discount, an off-the-shelf Sage 100 connector (1,500 to 6,000 EUR plus 50 to 300 EUR per month) is enough. As soon as you manage price categories, family discounts, customer-specific prices and quantity breaks, a custom connector (8,000 to 25,000 EUR excl. VAT) becomes the only reliable option. The main pitfall is not technical: it is the quality of pricing data in Sage, which must be cleaned before the first sync.

What syncs, in which direction and how often

A B2B portal connected to Sage 100 exchanges four families of data. Each has its own direction and sensible frequency. Syncing everything in real time is pointless and loads Sage's SQL server; syncing once a night is not enough for stock.

DataDirectionRecommended frequencyRisk if mishandled
Items, families, pack sizesSage to portal1 to 4 times a dayOutdated product pages
Available stock (physical minus reserved)Sage to portalEvery 5 to 15 minutesSelling out-of-stock items
Customer prices and discountsSage to portalHourly or on changeWrong price displayed, customer dispute
Customer accounts, outstanding balance, credit limitSage to portalHourlyOrder accepted beyond credit limit
OrdersPortal to SageImmediate or every 5 minutesRe-keying, delayed picking
Order status, delivery notes, PDF invoicesSage to portalEvery 15 to 30 minutesCalls to customer service

Off-the-shelf or custom connector: the comparison

Sage 100 does not expose a full REST API in every version. Integrations go through Objets Métiers (Sage's SDK), reads on the SQL Server database, file imports or an intermediate API layer. The chosen method determines robustness.

CriterionOff-the-shelf connectorCustom connector
Upfront cost1,500 to 6,000 EUR8,000 to 25,000 EUR excl. VAT
Subscription or maintenance50 to 300 EUR per month10 to 15% of build per year
Project duration3 to 6 weeks2 to 4 months
Customer-item exception pricesOften partialComplete
Quantity breaks and cascading discountsVaries by vendorComplete
Supported portal platformsClosed list (Shopify, PrestaShop, WooCommerce)Any portal, including custom Next.js
Error log and retryBasicCustom, with e-mail alerts
3-year cost (order of magnitude)3,300 to 16,800 EUR11,000 to 36,000 EUR

For reference, Kolonell's 2026 grid places an ERP connector with portal among medium apps, 4,000,000 to 7,000,000 FCFA, i.e. 6,100 to 10,670 EUR, and among complex apps beyond that, 10,670 to 22,870+ EUR depending on the number of flows.

The five pitfalls that derail the project

The first pitfall is the price hierarchy. Sage 100 combines item selling price, customer price category, family discount, customer-item exception price and quantity break. If the portal recalculates prices with its own rules, it will diverge sooner or later. The right approach is to compute the net price in a dedicated layer that reproduces Sage's logic exactly, then test it on a sample of 200 to 500 customer-item pairs.

The second pitfall is available stock: physical stock minus reserved customer orders, possibly plus expected receipts. Showing raw physical stock leads to undeliverable sales. The third is order creation in Sage: document numbering, warehouse, sales rep, payment method, intra-EU VAT. The fourth concerns server load: heavy queries every minute on the SQL database slow down accounting users. The fifth is error recovery: an order rejected by Sage must raise an alert, not vanish.

PitfallSymptomRemedy and indicative cost
Diverging net priceCustomer invoiced differently from portalPrice engine tested on 500 pairs: 2,000 to 5,000 EUR
Raw stock displayedOut-of-stock ordersNet availability calculation: 1,000 to 2,500 EUR
Missing mandatory document fieldsOrder rejectedMapping table: 1,500 to 3,000 EUR
Heavy queries on SQL ServerSage slow for accountingDelta sync: 1,500 to 4,000 EUR
Silent errorsLost ordersLog and alerts: 1,000 to 2,500 EUR
Dirty pricing dataAbsurd prices onlinePrior clean-up: 3 to 10 internal days

Mini case study

Need a professional website?

Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.

Prefer a call back?

Leave your WhatsApp number and a Kolonell expert will get back to you within 1 business day. Free, no strings attached.

You are :

Illustrative scenario: Laurent, CIO of an industrial supplies distributor in Nantes, with 1,200 business customers and 9,000 SKUs in Sage 100. His sales team re-keys about 180 e-mailed orders a week, at 6 minutes each, i.e. 18 hours weekly. He chooses a custom connector at 18,000 EUR excl. VAT with a price engine faithful to exception prices, plus 2,200 EUR annual maintenance. If 60% of orders move to the portal in year one, he saves about 11 hours a week, nearly 500 hours a year. At 40 EUR per loaded hour, the gain is about 20,000 EUR a year, plus fewer pricing errors. Estimated payback: 12 to 14 months.

FAQ

How much does a Sage 100 to B2B portal connector cost in 2026?

An off-the-shelf connector costs 1,500 to 6,000 EUR plus 50 to 300 EUR per month. A custom connector runs 8,000 to 25,000 EUR excl. VAT depending on the number of flows and pricing complexity.

Can stock be synced in real time?

A 5 to 15 minute frequency is the right trade-off for most distributors. True real time requires database triggers and extra SQL Server load, rarely justified below 500 orders a day.

Does Sage 100 have an API?

Depending on the version, integration goes through Objets Métiers, the SQL Server database or an intermediate API layer built for the project. That layer often accounts for 20 to 30% of a custom connector budget.

How long does the project take?

Budget 2 to 4 months for a custom connector, including 3 to 4 weeks of pricing acceptance tests. Cleaning prices in Sage beforehand takes 3 to 10 days of internal work.

What happens if Sage is down?

The portal keeps accepting orders and queues them. They are pushed into Sage when the server is back, with an alert if a document is rejected.

Let's scope your project. Send us your Sage 100 version, your portal and your pricing rules: we will price the flows, give an indicative budget and a 2 to 4 month plan. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.

Tags:#Sage 100#API integration#B2B portal#ERP connector#stock sync#integration cost
Share:

Mohamed Bah

Fondateur, Kolonell

Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.