At a minimum here's some due diligence you could do:
1. Ask for references of companies who have used TEKOA's API with Sage 100.
2. Ask DreamingCode how many Sage 100 integrations they've implemented with TEKOA.
3. Ask DreamingCode if API supports UDFs assuming client requires writing to or reading from UDFs when say a web order creates a SO in Sage.
(maybe this is a non-customizable contract API which means the DreamingCode developers cannot change the contract to expose UDFs. Note SData uses a contract system too but whenever you add UDFs with UDF Maintenance, the contract file is updated making UDFs available to SData)
4. Ask if it's a cookie-cutter solution or if it can be customized.
(I worked for a company that made non-contract web service REST integrations for Sage 100 customers who were either B2B (where web order created SO in Sage) or inter-company situation where one division created a PO that sent data via API to the other for SO to got created there. EVERY SINGLE implementation was custom in some way to match the way they manually created SO's. Even if you explored say INSYNCH from ROI, for all the implementations they've done, I'll bet you very few are cookie-cutter.)
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Email:
alnoor@asifocus.comOrange County, CA
------------------------------