Originally posted by vetran
View Post
The major SCO Providers all provide a defined SCO to POS interface and implementation of it so there is a decent starting point. The issue is that this is, in effect, a "new" thing to integrate to in the client pos.
Generally this will require change, potentially significant, to implement and the pos authors may be reluctant.
It is always doable, but generally messy.
An example may be a trigger for an item sale. The interface layer may need to reformat this to force it thru an rs232 emulator to look like its come from whatever scanner the pos is talking to. It may need to look at the RS232 display output, and or printer output to figure out what has happened and how to respond.
If you have access to the pos code, and are working with the sco provider it is just tedious and time consuming. If you need to "bolt on" to a broadly immutable system its harder.
Comment