hundred/ for Sage 100

Comparison · Sage 100 integration, 2026

Connecting Sage 100 in 2026: every option, honestly compared

Checked against Sage 100 help, the Sage knowledge base and Microsoft documentation on 2026-10-06.

Short answer: Sage 100 has no built-in REST API: sData, the old web interface, was removed in version 2025.1 Every way in runs on the Windows side, next to Sage 100: the ODBC driver to read, the Business Object Interface (BOI) to write, Sage's SOAP web services for a narrow set of records, Visual Integrator for file imports, or a third-party product that wraps one of these. Sage 100 2026 is 64-bit only, and Sage says "All integrations, add-ons, and custom solutions must be 64-bit compatible to work with Sage 100 2026."3

The options side by side

OptionRead / writeSage 100 2026 (64-bit only)Where it runsSkill neededTypical costPick it when
ODBC driver (SOTAMAS90)Guides 02, 06 Read only: SELECT over the Sage 100 data files. On Sage 100 Premium the data is in SQL Server, so reads can query the company database instead. Works from a 64-bit program. A 32-bit program (32-bit Excel or Python, an x86 build) cannot see 64-bit drivers and DSNs.2,11 A Windows machine with the Sage 100 ODBC driver and access to the Sage 100 data folder. SQL and an ODBC client: Excel, Power BI, Python, .NET. The driver's SQL dialect is older and has quirks. The driver ships with Sage 100. Your cost is the time to write and maintain the queries. Reports, BI dashboards, or a one-way sync of customers, orders, items or stock out of Sage 100.
Business Object Interface (BOI)Guides 03, 05 Read and write, through the same business objects the Sage 100 screens use: Sage's own validation, numbering, pricing and tax apply. Your program must run as 64-bit; a 32-bit program fails to create the objects. In .NET that means platform target x64.3,12 Windows, on a machine with the Sage 100 workstation installed (a COM interface, not a web API).4 A developer who knows COM (Python, .NET or VBScript) and Sage 100's business objects. Sage does not debug programs it did not write.4 Included in your Sage 100 activation.4 Plan for a connected session to take a Sage 100 user license seat. Development and upkeep are the real cost. You need to create or change orders, customers or invoices, with logic no packaged product covers, and you have a developer.
eBusiness Web ServicesSOAP over HTTPS · Guide 04 Read, create, update and delete, but only for sales orders, customers and customer contacts.5 Documented for 2026 (Sage guide published April 1, 2026). It runs inside IIS on the Sage server, and Sage sets no language or operating system requirement for the calling program.5 IIS on the same machine as Sage 100, with a server certificate. Your app calls that server over HTTPS, so it must be reachable from where your app runs.6 Sage's guide "is written for the experienced Microsoft Internet Information Services (IIS) Administrator", plus a developer who can call SOAP.5 Needs an activation key with eBusiness Web Services enabled.6 Ask your Sage partner what that costs on your license. Plus IIS setup and upkeep. A web shop or portal needs orders, customers and contacts only, and the client's IT already runs IIS and accepts inbound HTTPS to the Sage server.
File import (Visual Integrator)Guide 01 Write by import jobs, read by export jobs. Imports from files or from an ODBC source.7,10 Not for CRM data.7 A Sage 100 module, documented in the 2026 help.7 Inside Sage 100. Repeating runs ("cycles") work only when the job is started from a shortcut or command line.8 A Sage partner or power user who builds import jobs. Sage support does not help with custom jobs.9 A Sage 100 module: ask your Sage partner whether it is on your license and what it costs. Plus the time to build each job. Batch loads where hourly or nightly is fast enough: web orders from a CSV export, price lists, opening data.
Packaged connector or REST bridgeThird-party · Guides 01, 04 Depends on the product. Commerce connectors sync orders in and stock out;13 REST bridges offer read and write endpoints.14 Ask the vendor for a 64-bit build tested on 2026. Sage requires it of every add-on.3 The vendor's service, plus a component on the Windows side next to Sage 100 that uses ODBC, BOI or file imports. Setup and field mapping, often done by the vendor or your Sage partner. A subscription; most vendors quote on request. One public price: sage100restapi.com lists $2,700 a year, plus $360 a year per extra company code (checked 2026-10-06).14 A standard case a product already covers, such as Shopify orders into Sales Order, and a budget for a subscription.
sDataRemoved · Guide 04 Gone. The Native SData Provider is no longer an install option from version 2025.1 Not available in 2025 or 2026.1 Only on Sage 100 2024 or earlier. n/a n/a Never for new work. If an integration still uses it, move it to one of the routes above before the upgrade to 2025 or later.
HundredREST API for Sage 100Planned Planned: reads, and writes through Sage 100's business objects. Not built yet; nothing is callable today. Not built yet. Planned: a small Windows service at each client company, outbound HTTPS only, and one HTTPS endpoint for your code. Planned: any language that can call a JSON API over HTTPS. Planned: $99 a month per connected Sage 100 company. Nothing is sold and no payment is taken. Not today. If you connect many client companies and want one API for all of them, join early access and tell us what you need.

Each option name links to the guide that covers it in detail, with code and sources. All guides: hundredapi.com/guides.

How to choose

Only need to read data?
Use ODBC, or SQL directly on Sage 100 Premium. It is included and the fastest to start.
Need to create orders or customers?
Build on BOI if you have a developer, or buy a connector that already covers your case.
A web app must call Sage 100 over HTTPS?
eBusiness Web Services if orders, customers and contacts are enough and IIS is acceptable. Otherwise a service on BOI, or a third-party REST bridge.
A file once a night is enough?
Visual Integrator import jobs, if the module is on your license.
Still on sData?
It does not exist in 2025 or 2026. Plan the replacement before you upgrade.
Upgrading to 2026?
List every program, script and scheduled job that touches Sage 100 and confirm each is 64-bit. What breaks and how to fix it

Sources

  1. Sage 100 2025 Upgrade Guide: What's New (sData removal)
  2. Sage KB: 64-bit ODBC driver
  3. Sage KB: Sage 100 2026 64-Bit Only FAQ
  4. Sage 100 2026 help: Business Objects Interface FAQs
  5. Sage 100 2026 eBusiness Web Services guide: Introduction
  6. Sage 100 2026 eBusiness Web Services guide: Getting Started
  7. Sage 100 2026 help: Visual Integrator, Create an Import Job
  8. Sage 100 2026 help: Visual Integrator, Set Up Cycles for a Job
  9. Sage KB: Visual Integrator resources and help
  10. Acute Data (Sage partner): Visual Integrator module
  11. Microsoft: ODBC Data Source Administrator (32-bit and 64-bit)
  12. Microsoft: C# compiler options, PlatformTarget
  13. Shopify community: Shopify integration with Sage 100
  14. sage100restapi.com: public pricing, checked 2026-10-06

Something here out of date for your version? The guides list the date each fact was checked; Sage 100 ships a major release each April.

Online, with links to every source and guide: https://hundredapi.com/sage-100-integration-options.html · checked 2026-10-06

Hundred is a planned REST API for Sage 100: one HTTPS endpoint for your code, and a connector at each client that would carry the call into their Sage 100. It is not built yet. Planned price: $99/month per connected Sage 100 company; nothing is sold and no payment is taken.

Join early access