Home / News / Putting Sage 100 on the web without letting your data drift

Putting Sage 100 on the web without letting your data drift

2026-07-03

Putting Sage 100 on the web without letting your data drift

Your reps want the catalogue and stock at the customer's site. Your customers want to order online. Sage 100 stays on the office server. The question is not whether to open it, but how.

The wrong answer: copying

Duplicating items, customers and prices into a web database is easy to build and painful to live with. Every change made on one side must be replayed on the other. At the first network incident the two databases diverge, and nobody knows which one is right.

The right answer: one master, one door

Sage stays the system of record. The web application is a front door: it reads what it needs and returns what it produces. In practice, from Sage to the web travel items, customers, prices and stock; the other way, quotes, orders and deliveries.

Full or incremental sync

The first pass is necessarily full. After that, only rows created or changed since the last run should travel. On a 40,000-item file, that is the difference between a twenty-minute sync and a twenty-second one.

What to check before signing

Three points. Does the connector authenticate by something other than an IP address? What happens if the link drops mid-transfer? And how many extra Sage licences will your vendor bill for the web users? With us, the answer to the last one is: none.