How does ConneX obtain data from different POS terminals?
In general, ConneX gets data from the client POS and pushes it into the application database (EMW & NC), but the process varies from POS system to POS system. Below is a breakdown of how ConneX receives data from each POS used by clients:
-
Agilysys: (FTP Based)
- Agilysys / ConneX integration is an FTP-based relationship where ConneX obtains files from the FTP site:
- https://portal.ftp.infogenesisasp.com
- The integration that creates the files and moves them to a specified folder in the FTP site was created and is supported by Agilysys.
- Additionally, the FTP site itself is owned by Agilysys.
- Agilysys / ConneX integration is an FTP-based relationship where ConneX obtains files from the FTP site:
-
Aloha: - (On-Premise Based)
- Aloha is an On-premise-based integration in which the POS creates DBF files within the terminal; ConneX pulls data from those files to create a file that is then pushed into Net-Chef. The creation of the DBF files is an Aloha process, so in the event the data is missing, the client will need to work with Aloha to get it recreated so the ConneX integration can then access it.
-
Brink: - (Cloud Based)
- The Brink / ConneX integration is cloud-based, where ConneX pulls from a single API for all locations.
-
Micros: - (On-Premise Based)
- The Micros / ConneX integration is an On-Premise setup where the ConneX Client queries the POS tables to obtain data that it then pushes into Net-Chef.
-
Micros Symphony: - (Cloud Based)
- The Micros Symphony / ConneX integration is cloud-based, where ConneX pulls from a single API for all locations.
-
Nextep: - (Cloud Based)
- The Nextep / ConneX integration is cloud-based, where ConneX pulls from a single API for all locations.
-
Positouch: - (On-Premise Based)
- Positouch is considered "On-Premise" as far as the POS / ConneX integration goes. First, Positouch creates an XML file in a specified drive within the terminal. This file is then cloned; the original is sent to an archive folder and the clone is sent to the AWS (Amazon Web Services) where ConneX acquires it.
- Discussions with Positouch confirmed this was the most dependable way to get accurate information to ConneX.
- The XML writer was developed by Positouch and is also supported by them.
- Positouch is considered "On-Premise" as far as the POS / ConneX integration goes. First, Positouch creates an XML file in a specified drive within the terminal. This file is then cloned; the original is sent to an archive folder and the clone is sent to the AWS (Amazon Web Services) where ConneX acquires it.
-
Revel: - (Cloud Based)
- This integration is still in Development.**
-
Sicom: - (Cloud Based)
- Sicom is an API (Cloud Based) POS, which ConneX pulls from. Each location has a unique API (which is not as common as one API for all locations).
-
Stratex:
- Stratex is an HR system that some clients use for their employees. It is a cloud-based API; ConneX pulls employee data from it, which is then pushed into Net-Chef to be used for scheduling and labor.
-
Toast: - (Cloud Based)
- The Toast / ConneX integration is cloud-based where ConneX pulls from a single API for all locations.
-
Xpient: - (On-Premise Based)
- The Xpient / ConneX integration is an On-Premise setup where the ConneX Client will query the POS tables to obtain data that it then pushes into Net-Chef.
Comments
0 comments
Please sign in to leave a comment.