Browse Business Software Categories

Close  

CRM

Ecommerce

ERP

Sage 100 Integrations: Ecommerce, EDI, CRM and Payments

Sage 100 Integrations: Ecommerce, EDI, CRM and Payments

Last updated: November 3, 2026 · Independent guide · We do not sell rankings or coverage.

Sage 100 integration runs through four native routes: the Business Object Interface (BOI) for writes that respect Sage 100’s business rules, the ODBC driver for read-only reporting and extracts, Visual Integrator for scheduled file imports and exports, and eBusiness Web Services for SOAP access to customers and sales orders. Sage 100 has no native REST API, so most ecommerce, EDI, CRM and payment connectors are third-party products that sit on top of one of those routes. The steps below enable each route in the order an administrator would, then cover common connectors and their published costs.

Before you start

  • Version and bitness. Sage 100 2026 is a 64-bit only application, and a 32-bit Sage 100 2021–2025 installation on the same server stops working after you install it (Sage 100 2026 Installation Guide, February 23, 2026).
  • Edition. Sage 100 installs as Standard, Advanced (client/server) or Premium (Microsoft SQL Server), three installation types that Sage has sold as one product since version 2023 (Sage 100 2026 Installation Guide). Several ODBC steps below differ by edition.
  • Modules. Visual Integrator, Credit Card Processing and Customer Relationship Management are separate modules. You can only import into a task whose module is installed (Sage 100 Help, Create an Import Job).
  • Activation. Sage states that BOI is “automatically provided as part of your Sage 100 activation,” while eBusiness Web Services needs an activation key that enables it (Sage 100 Help, BOI FAQs; Sage 100 2024 Web Services Guide).
  • Licenses. In Sage’s community forum, a reply marked as the verified answer says a BOI session consumes a Sage 100 user license unless it attaches to a running Sage 100 process, and another reply says ODBC does not use a license (Sage Community Hub). Confirm license use with your partner before adding an always-on connector.
  • A test company and a backup of every destination data file before any import.

Step 1: Pick the method for each data flow

Decide the route for each flow first; each has its own security settings.

Method Read or write Typical use Main limitation
Business Object Interface (COM) Read and write, through Sage 100’s business objects Real-time order, customer and inventory sync used by most connectors Needs COM programming; Sage support is limited to certified developers
ODBC driver (SOTAMAS90) Read only Reporting, BI and extracts Cannot write back to Sage 100
Visual Integrator Import and export Batch loads of orders, invoices and master data from files Batch only; jobs need testing and monitoring
eBusiness Web Services (SOAP) Read, create, update, delete Web storefronts posting customers and sales orders Covers sales orders, customers, contacts and credit card vaulting only

The ODBC read-only point comes from Sage’s community forum, where experienced users state that none of the shipped ODBC drivers are read/write (Sage Community Hub).

Step 2: Create a dedicated integration role and user

Give every connector its own Sage 100 user. On non-subscription installs, go to Library Master Security menu > Role Maintenance. On the Tasks tab, select only the modules and tasks the connector needs; on the Security Events tab, enable only the events it needs; on the Module Options tab, clear options you do not want enabled. Then assign the role in User Maintenance (Sage 100 Help, Define Roles).

Visual Integrator import and export rights sit on the Module Options tab for each module (Sage 100 Help, Role Maintenance fields). For Web Services, Sage’s guide says to grant each operation on the Tasks tab, such as Accounts Receivable > Main > Customer Maintenance > Create for customer creation.

Step 3: Allow external access for the company

Go to Library Master Main menu > Company Maintenance, select the company, and open the 3. Preferences tab. Select Allow External Access, which Sage describes as allowing “the company to be accessed externally through the company’s objects” (Sage 100 Help, Company Maintenance fields). Select it for every company a connector or script will use.

If you will use eBusiness Web Services, select Enable Web Services on the same tab. Sage’s guide also requires it in Library Master Setup menu > System Configuration and on each user, plus IIS with a server certificate.

Step 4: Set up ODBC for read-only reporting

On Sage 100 Advanced, run the client/server ODBC driver on the server. Sage’s install guide says to run pvxiosvr.exe from the Home folder inside MAS90 as an application, or with the -i parameter as a service set to Automatic under a domain administrator-level account (Sage 100 Help, Configuring the Client/Server ODBC Driver).

In Library Master Setup menu > System Configuration, ODBC section, select Enable C/S ODBC Driver, enter the server port (blank uses the default, 20222, per the install guide) and choose whether to enable it for all users. To restrict tables and fields by role, select Enable ODBC Security within Role Maintenance in the Security section; Sage notes this option is not available for Premium (Sage 100 Help 2026, System Configuration fields). Test the SOTAMAS90 data source in Windows ODBC Data Source Administrator.

Sage’s knowledgebase says Sage 100 2025 installs both 32-bit and 64-bit ODBC connections and 2026 is 64-bit only (Sage KB, 64-bit ODBC driver, July 3, 2026). On Premium, still write through business objects rather than SQL updates.

Step 5: Build Visual Integrator jobs for batch loads

Go to Visual Integrator Main menu > Import Job Maintenance. Enter a job name and table name, set the File Type and Import File on the Configuration tab, select fields on the Data tab and record filters on the Select tab, then accept and compile. Choose Test before you run it for real (Sage 100 Help, Create an Import Job).

Many file-based EDI and iPaaS tools post data this way. DBSync’s documentation says its Sage 100 connector moves data in and out through Visual Integrator and requires an ODBC bridge on the Sage 100 server (DBSync docs, July 28, 2017). If your EDI provider delivers 850 files, our guide to the EDI 850 purchase order explains the segments you will map into Sales Order fields.

Step 6: Connect payments

Sage 100’s native card and ACH processing uses Paya, formerly Sage Payment Solutions. Install Paya Connect Desktop on each workstation from the Autorun program in the Wksetup folder inside MAS90, add www.sageexchange.com to trusted sites, then go to Accounts Receivable > Setup > Payment Setup Wizard with your Paya merchant ID and merchant key (Sage 100 Install Guide 2023, Credit Card and ACH Processing).

Company-level settings such as Enable Payments and Enable Payments for eInvoices sit in Company Maintenance, on a tab Sage 100 2026 renamed from Payments to Integrations (Sage 100 Help, Company Maintenance fields; Sage 100 2026 What’s New, July 8, 2026). Paya requires Sage 100 2013 or later and a Paya merchant account (Paya help center). Neither Sage nor Paya publishes processing rates on these pages.

Step 7: Connect Sage CRM (if you use it)

Install Sage CRM on a separate server with full SQL Server, set up the Customer Relationship Management module’s CRM Server Options and CRM Company Options, then run Integrate Sage CRM Installation with Sage 100 2026 from the Autorun screen. Set the Sage 100 Integration Engine service to Automatic and create a matching Sage CRM user for every Sage 100 user who creates quotes or orders (Sage 100 2026 Installation Guide). Quick Order Entry from CRM works only on Advanced and Premium.

Step 8: Test in a copy, then reconcile after go-live

Run every flow against a test company first, including refunds, partial shipments and credit holds. After go-live, reconcile order counts and totals, and cash receipts against processor settlements, daily for the first weeks. Our guide to ERP data integration covers the ownership rules that keep two systems from overwriting each other.

Common mistakes and how to fix them

  • A 32-bit connector after a 2026 upgrade. 32-bit components can stop working when you move to 64-bit only Sage 100 2026. Ask each vendor for written 2026 support before you schedule the upgrade.
  • Writing through ODBC or SQL. Direct writes skip validation and audit logic. Route writes through BOI, Visual Integrator or Web Services.
  • Connectors running on an employee’s login. The sync stops when that person leaves. Use the dedicated role from Step 2.
  • Allow External Access left clear in a new company. The setting is per company, so check it on every new company before you point a connector at it.
  • Running untested Visual Integrator jobs on live data. Back up first and use the Test button.

Limitations of the native tools

Sage 100 has no native REST API. Its own interfaces are COM (BOI) and SOAP (Web Services), and DSD Business Systems (which sells the IN-SYNCH connector) says Sage 100 “does not have an API built into the system” for custom integrations (DSD, July 27, 2026). Web Services covers only customers, contacts, sales orders and credit card vaulting, Visual Integrator is batch-based, BOI needs COM programming, and ODBC cannot write. None of these speaks X12 EDI or the Shopify or Salesforce APIs, so you still need a translator or connector for those systems.

When companies add a third-party tool

Companies usually buy a prebuilt connector once they need real-time ecommerce orders, retailer EDI or two-way CRM sync. We checked each vendor page on November 3, 2026; every vendor named sells the product described.

Need Connector Published cost How it connects (vendor’s description)
Ecommerce Clarity Connect (Shopify and others) $599 per month, billed annually, one integration pair iPaaS; Shopify webhooks create Sage 100 sales orders
Ecommerce, CRM APPSeCONNECT From $99 per month BOI and web services
Ecommerce, marketplaces IN-SYNCH (DSD) Projects from about $10,000, mostly one-time, small annual fees Runs on the Sage 100 server, no inbound ports
EDI TrueCommerce Plans shown from $99 per month on an undated pricing page; setup not published Native Sage business objects
EDI SPS Commerce Fulfillment Not published Mapadoc, embedded in the Sage 100 interface
CRM (HubSpot) Commercient SYNC From $900 per month plus scoped onboarding (HubSpot listing, updated August 24, 2026) Syncs customers, items, orders and invoices to CRM objects
Payments Paya (native), REPAY, Paystand Rates not published on the pages we reviewed Paya through the Credit Card Processing module; REPAY works inside Sage 100, and Paystand syncs with it

When you compare quotes, check the fee model. Clarity says its plan includes unlimited transactions within fair-use limits, and DSD says it charges no per-transaction or volume fees, while Commercient describes its pricing as metered to run. SPS Commerce says its team handles map updates and trading-partner testing; see our EDI 856 ship notice guide for what retailers check.

How we researched this

We read Sage’s own help, install guides, Web Services guide and knowledgebase for each setup step, and used only menu paths those documents state. Where Sage’s documentation is silent, such as ODBC write access and BOI license use, we cite Sage’s community forum and say so. Connector costs come from each vendor’s own published pages, checked on November 3, 2026. We also reviewed the ranking pages from DSD, Hyperbots, DCKAP and TrueCommerce.

Related guides

Frequently asked questions

Does Sage 100 have an API?

Sage 100 has no native REST API. It offers the Business Object Interface, a COM interface for reading and writing through Sage 100’s business logic, and eBusiness Web Services, a SOAP interface for customers, contacts and sales orders.

Can I write data to Sage 100 through ODBC?

No. Experienced users in Sage’s community forum state that the ODBC drivers shipped with Sage 100 are read-only. Use BOI, Visual Integrator or eBusiness Web Services to write data so Sage 100’s validation and audit logic runs.

Will my integrations still work on Sage 100 2026?

Only if they are 64-bit compatible. Sage states that Sage 100 2026 is a 64-bit only application and that a 32-bit 2021–2025 installation on the same server stops working. Get written confirmation of 2026 support from each connector vendor before you upgrade.

How much does a Shopify or EDI connector for Sage 100 cost?

Published prices we found run from APPSeCONNECT at $99 per month to Clarity Connect at $599 per month billed annually, and DSD quotes IN-SYNCH projects from about $10,000. SPS Commerce does not publish EDI pricing.

Sources

  • Sage, Sage 100 2026 Installation and System Administrator’s Guide, February 23, 2026. docs.sage.com
  • Sage, Sage 100 2026 What’s New Guide, July 8, 2026. docs.sage.com
  • Sage, Sage 100 2024 Web Services Guide, March 7, 2024. docs.sage.com
  • Sage, How to install the 64-bit ODBC driver in Sage 100, knowledgebase, last modified July 3, 2026. us-kb.sage.com
  • Sage 100 Help, Business Objects Interface FAQs (2016 help), no date shown. help-sage100.na.sage.com
  • Sage 100 Help, Create an Import Job (2020 help), no date shown. help-sage100.na.sage.com
  • Sage 100 Help, Define Roles (2024 help), no date shown. help-sage100.na.sage.com
  • Sage 100 Help, Role Maintenance fields (2024 help), no date shown. help-sage100.na.sage.com
  • Sage 100 Help, Company Maintenance fields (2025 help), no date shown. help-sage100.na.sage.com
  • Sage 100 Help, System Configuration fields (2026 help), no date shown. help-sage100.na.sage.com
  • Sage 100 Help, Configuring the Client/Server ODBC Driver (2021 install guide), no date shown. help-sage100.na.sage.com
  • Sage 100 Help, Setting Up Credit Card and ACH Payment Processing (2023 install guide), no date shown. help-sage100.na.sage.com
  • Sage Community Hub, BOI, ODBC and user licensing (community forum thread), no exact date shown. communityhub.sage.com
  • Sage Community Hub, Is there a 64-bit ODBC read/write driver available for Sage 100 2024? (community forum thread), no exact date shown. communityhub.sage.com
  • Paya, Getting to know Sage 100 ERP and Paya, no date shown. Paya sells payment processing. paya.helpjuice.com
  • DSD Business Systems, Sage 100 Integration FAQ, July 27, 2026. DSD sells IN-SYNCH. dsdinc.com
  • Clarity Ventures, Shopify and Sage 100 integration, no date shown (checked November 3, 2026). Clarity sells the connector. clarity-ventures.com
  • APPSeCONNECT, Sage 100 Integration and Automation, no date shown (checked November 3, 2026). APPSeCONNECT sells the connector. appseconnect.com
  • HubSpot Marketplace, Sage 100 SYNC by Commercient, pricing updated August 24, 2026. Commercient sells the connector. ecosystem.hubspot.com
  • TrueCommerce, EDI for Sage 100 ERP, last modified August 21, 2026. TrueCommerce sells EDI services. truecommerce.com
  • TrueCommerce, EDI software pricing, no date shown (checked November 3, 2026). learn.truecommerce.com
  • SPS Commerce, Sage 100 integration, last modified September 2, 2025. SPS sells EDI services. spscommerce.com
  • DBSync, Sage 100 Connector documentation, July 28, 2017. DBSync sells the connector. help.mydbsync.com
  • REPAY, Sage 100 payments integration, no date shown (checked November 3, 2026). REPAY sells payment processing. partners.repay.com
  • Paystand, How to Choose the Right Sage 100 Integrated Payment Solution, December 16, 2024. Paystand sells payment processing. paystand.com

Sherman Hsieh

CEO & Editor-in-Chief, Business-Software.com
Independent analysis of enterprise software — ERP, CRM and more
Sherman Hsieh is the founder, CEO, and editor-in-chief of Business-Software.com. He leads the site's independent, buyer-focused coverage of ERP, CRM, and other business systems, including vendor-neutral comparisons, pricing analysis, and implementation guidance. Before founding Business-Software.com, Sherman was an executive at Siebel ...