Connections
Every buyer system we deliver to.
A connection is one buyer receiving your catalog in its own system. The channel is whatever that system accepts: an SFTP drop, an API, a PunchOut or OCI catalog, an EDI feed or a file in the buyer's template. We set up every connection, map your catalog to the buyer's template and test the first delivery with you.
SAP AribacXML
CoupaCSV, API
JaggaercXML, SFTP
Oracle FusioncXML, API
SAP S/4HANAOCI, file
Ivaluafile, API
Zycusfile, API
GEP SMARTfile, API
ZipAPI
ProcurifyAPI
BirchStreetCSV, SFTP
Procure WizardExcel, SFTP
FutureLogfile, API
Agilysysfile
Purchase Warriorfile
Purchase Plusfile
ReecoAPI
Apicbasefile, API
MarketManfile, API
Jellyfile
Any buyer systemfile, API or their own protocol
Some of your buyers still want a price list by email.
Not every buyer runs a system. Tell us how those buyers receive your prices today and we will show you how SupplierForge can handle them.
Your buyer is not listed?
Tell us which system it is and how it accepts catalogs. If it takes a file or an API call, we build the template with you at setup.