Coming soon
The platform we build your integrations on.
Martin and Associates has spent years connecting these systems one client at a time. ERP to storefront, CRM to ERP, an order feed to a warehouse and the shipment back again. SConnect is the platform we build that work on. We write the code and we run it, so what you get is a working integration rather than a toolkit to learn.
Tell us what you are connecting The Sage 100 API is live now
The expertise is the part you cannot download
Moving a record between two systems is the easy half. The half that takes the years is knowing what a credit memo does to inventory, which field the ERP will silently refuse, whether that order already arrived under a different number, and what should happen at 4am when one side is down and the other keeps sending.
That judgement is what Martin and Associates sells today, and it is what the platform is being built to carry. It is the same reason the Sage 100 API writes through Sage’s own business objects rather than around them. The rules belong to the ERP, and an integration that skips them is a data-repair project with a delivery date.
What it connects
Integration work is rarely about one system. It is about a pair, and then the third one that turns up six months later. These are the categories the projects keep landing between.
ERP
Sage 100, Acumatica, Sage Intacct and Dynamics GP. We implement and integrate all four today. Sage 100 is also the one you can call yourself, through our Sage 100 API.
Ecommerce
Storefronts and marketplaces: orders in, stock and pricing out, shipments and tracking back. The integration everyone wants first and underestimates most.
CRM
Customers, quotes and opportunities that agree with what accounting believes, so that nobody is quoting from a spreadsheet that was right last Tuesday.
Sales and order entry
Field sales tools, point of sale, EDI, and the order feed that arrives as a file at 2am from a trading partner who will not be changing their format for you.
Warehouse and shipping
Picks, shipments, rates and labels. Systems that need to hear about a document the moment it exists rather than in tomorrow morning’s batch.
Reporting and analytics
A read surface something else can point at, so the monthly number stops being produced by exporting a table and emailing it around.
What this is not, yet
Same rule as the product pages: the edges belong on the page rather than in a conversation three weeks in.
- There is no date on this page
- Deliberately. A date here would be a promise written by whoever edits this file and kept by whoever writes the code, and those are different problems. When a piece of this becomes something you can use directly, it gets its own page and a chip that says Available now, the way the two APIs did.
- The list above is where the work has been, not a menu
- None of those categories is a finished connector sitting on a shelf. They are the shapes these projects keep taking, and they are what the platform is being built out of.
- It is not a toolkit you operate
- We write the code and we run it. The platform is how Martin and Associates builds and hosts your integration, not a builder you are handed a login to and left alone with. If self-serve is what you are after, that is what the two APIs are for.
- Two things are already callable
- The Sage 100 API and the Alerts API exist, are documented, and are not waiting on any of this. If your problem is one of those, skip the roadmap.
Available today, while this is being built
Sage 100 API
Read and write Sage 100 over HTTP. 47 readable entities, durable writes, and a connector that dials out from your own Sage box. No inbound firewall rule and no VPN.
Alerts API
Transactional email and a structured log store behind one API key, for the jobs that run with nobody watching. Registration is self-serve.
Tell us what you are connecting
This is the useful thing you can do with this page. What we build support for next is decided by which pairs of systems people keep asking for, so naming yours is worth more to us than a mailing list signup. It also means we can tell you whether the Sage 100 API already covers it, which for a surprising number of cases it does.
Built and supported by Martin and Associates.