Sage 100 add-ons vs. custom automation

The question behind the search

If your company runs Sage 100 (the product once called MAS 90 and MAS 200), you've probably been pitched both. A reseller shows you a catalog of add-ons. Someone else says they can build what you need around Sage. Both can be right. This guide sorts out which fits which job, using Sage's own documentation and the add-on vendors' own pages, checked on Oct. 29, 2026. We don't resell Sage or any add-on.

Where Sage 100 stands in 2026

The current version is Sage 100 2026, and its latest update is 2026.1. Sage's What's New guide says it is now a 64-bit only application, and that older 32-bit versions on the same server stop working once it's installed. That matters for add-ons: every one of them has to work with 64-bit.

On AI, the guide lists one new feature: an AI-powered help assistant that points users to the right page in Sage 100's help. In 2026.1 it was renamed Search help. Nothing in the guide describes AI that enters orders or bills.

Sage supports the current version and the two before it, as reported by ERP Research and resellers such as SWK Technologies. On that schedule, 2024 retires with the 2027 release. We couldn't open Sage's own supported-versions article, so treat those dates as reported, and confirm yours with your partner.

What Sage 100 gives you to connect to

Any add-on or custom tool has to get data in and out through one of these doors:

• BOI comes with every Sage 100 activation. Sage's FAQ says its support covers the interface itself and Sage's own programs, not code written by others.
• VI import jobs run through Sage's business objects and expect structured files. Sage recommends CSV over older spreadsheet formats. VI is great for clean data. It doesn't read a customer's PDF or an email.
• ODBC: users and experts on Sage's Community Hub say the bundled drivers are read-only, and that writes should go through the business objects so Sage's checks and audit trail stay intact. That's a forum, not official documentation.
• Web services. Sage's eBusiness Web Services guide describes a SOAP interface for sales orders, customers and customer contacts only. The older SData interface is deprecated, according to a verified answer on the Community Hub. By contrast, Sage's cloud product, Sage Intacct, has a REST API.

What add-ons do well

The Sage 100 add-on market is mature, and for some jobs it's the obvious answer.

• EDI. SPS Commerce embeds its Mapadoc EDI inside Sage 100 for orders, invoices and ship notices, says it has more than 2,400 Sage 100 EDI customers, and handles map updates when trading partners change rules. TrueCommerce turns inbound 850 purchase orders into sales orders and sends invoices (810), ship notices (856) and inventory reports (846). Retailer EDI rules change often. Paying someone to keep up is a good trade.
• Warehouse and barcode. Products like Endpoint (scanco.com's Sage 100 pages now point there) add warehouse execution, multi-bin and license plate tracking. Hardware, scanners and floor workflows are a product problem, not a custom one.
• Screen and logic changes. Developers like DSD Business Systems sell enhancements that change how Sage screens and modules behave. For a small, common change, a catalog enhancement is usually cheaper than anything custom.

One more to know about: SPS also offers a PDF order automation product for orders that don't come by EDI. If your emailed orders are fairly uniform, look at it before you build.

The add-on question is really an upgrade question. Every piece you add is a piece you test next spring.

The cost that shows up at upgrade time

Sage's own 2026 upgrade checklist tells you to talk to your business partner or developer before upgrading if you have custom modules or modifications. It also says to update customized screens, test custom reports and forms, and compare form definitions, because default forms may be erased in the upgrade.

Add-ons that change Sage's modules carry extra work. DSD's own manual for one enhancement says that if you reinstall or upgrade the related Sage modules, you must reinstall the enhancement too, and module levels must match. It also warns: "Enhancements from different Sage Developers are generally not designed to work together." Three or four of these from different developers, and every upgrade becomes a project.

The 2026 move to 64-bit made this sharper. SWK's checklist says integrations must be 64-bit compatible and that older third-party add-ons and heavily customized reports can make the upgrade more complex.

Custom automation isn't free of this either. A tool that writes through BOI still has to be tested against each new version. The difference is where it lives: a tool that sits outside Sage and writes through its business objects or a VI import doesn't change Sage's program files, so there's less to reinstall. That's our reading of Sage's and DSD's documents, not a promise from Sage.

When custom automation is the better fit

• The input is messy. Forty customers email POs, each in their own layout and with their own part numbers. VI can't read them, and a template-based tool breaks when a customer changes their PDF.
• The rules are yours. Which customers get which price breaks, which items substitute, which orders need a credit check. No catalog add-on knows those.
• The work crosses systems. The order is in email, the price is in Sage, the lead time is in a supplier's portal and the approval is in Teams.
• You want a person approving. A review screen where your team checks each draft before it posts to Sage, built around how they already work.

If none of those are true, buy the add-on.

Questions to ask before you buy any add-on

1. Is it certified for Sage 100 2026 and 64-bit? Ask for the version list in writing.
2. Does it change Sage's own modules, or sit outside them? Changes inside Sage mean a reinstall at each upgrade.
3. Who tests it at upgrade time, and how soon after a Sage release? A vendor that lags by months holds your upgrade back.
4. Does it work with the other add-ons you already run? DSD's own manual warns that enhancements from different developers can conflict.
5. What happens to your data if you stop paying? Make sure records stay in Sage, not only in the add-on.

What to automate and what to keep with a person

• Automate: reading emailed orders and bills, matching customers and items, filling in Sage 100 through BOI or a VI import, and flagging anything that doesn't match.
• Keep with a person: approving each order before it posts, price disputes, new customers and items, substitutions, and every upgrade test.

For the payables side, see our guide to Sage 100 AP automation.

How Peekgentic does it

We build the reading, matching and checking around the order desk's inbox and post draft orders into the ERP for a person to approve. Nothing is installed inside Sage's own modules. See our order processing build for how it works, step by step.