Abstract: Some systems and methods are directed to a device agnostic architecture configured to control and/or manage the interactions between front end store systems (e.g., self checkout (SCO) systems) for capturing purchase items and backend systems (e.g., point of sale (POS) subsystems) for completing purchases. The device agnostic architecture can include a translation layer or translation component that mediates communications from and/or between the front end and backend systems. For example, the translation layer maps any commands received from any SCO and/or POS device into execution commands native to receiving systems. For example, back-end processing systems can be configured to control on-line identification of products and/or services for purchase, and manage execution of sales of any goods or services. The translation layer manages communication between SCO devices and the backend systems so each communicates with each other according to their respective formats (e.g.

Abstract: Some systems and methods are directed to a device agnostic architecture configured to control and/or manage the interactions between front end store systems (e.g., self checkout (SCO) systems) for capturing purchase items and backend systems (e.g., point of sale (POS) subsystems) for completing purchases. The device agnostic architecture can include a translation layer or translation component that mediates communications from and/or between the front end and backend systems. For example, the translation layer maps any commands received from any SCO and/or POS device into execution commands native to receiving systems. For example, back-end processing systems can be configured to control on-line identification of products and/or services for purchase, and manage execution of sales of any goods or services. The translation layer manages communication between SCO devices and the backend systems so each communicates with each other according to their respective formats (e.g.

Abstract: Some systems and methods are directed to a device agnostic architecture configured to control and/or manage the interactions between front end store systems (e.g., self checkout (SCO) systems) for capturing purchase items and backend systems (e.g., point of sale (POS) subsystems) for completing purchases. The device agnostic architecture can include a translation layer or translation component that mediates communications from and/or between the front end and backend systems. For example, the translation layer maps any commands received from any SCO and/or POS device into execution commands native to receiving systems. For example, back-end processing systems can be configured to control on-line identification of products and/or services for purchase, and manage execution of sales of any goods or services. The translation layer manages communication between SCO devices and the backend systems so each communicates with each other according to their respective formats (e.g.

Abstract: Some systems and methods are directed to a device agnostic architecture configured to control and/or manage the interactions between any front end store systems (e.g., self checkout (SCO) systems) for capturing purchase items and backend systems (e.g., point of sale (POS) subsystems) for completing purchase of the items. The device agnostic architecture can include a translation layer or translation component that mediates communications from and/or between the front end and backend systems. For example, the translation layer maps any commands received from any SCO and/or POS device into execution commands native to receiving systems. For example, back-end processing systems can be configured to control on-line identification of products and/or services for purchase, and manage execution of sales of any goods or services. The translation layer manages communication between SCO devices and the backend systems so each communicates with each other according to their respective formats (e.g.

Abstract: Some systems and methods are directed to a device agnostic architecture configured to control and/or manage the interactions between any front end store systems (e.g., self checkout (SCO) systems) for capturing purchase items and backend systems (e.g., point of sale (POS) subsystems) for completing purchase of the items. The device agnostic architecture can include a translation layer or translation component that mediates communications from and/or between the front end and backend systems. For example, the translation layer maps any commands received from any SCO and/or POS device into execution commands native to receiving systems. For example, back-end processing systems can be configured to control on-line identification of products and/or services for purchase, and manage execution of sales of any goods or services. The translation layer manages communication between SCO devices and the backend systems so each communicates with each other according to their respective formats (e.g.

Abstract: Some systems and methods are directed to a device agnostic architecture configured to control and/or manage the interactions between any front end store systems (e.g., self checkout (SCO) systems) for capturing purchase items and backend systems (e.g., point of sale (POS) subsystems) for completing purchase of the items. The device agnostic architecture can include a translation layer or translation component that mediates communications from and/or between the front end and backend systems. For example, the translation layer maps any commands received from any SCO and/or POS device into execution commands native to receiving systems. For example, back-end processing systems can be configured to control on-line identification of products and/or services for purchase, and manage execution of sales of any goods or services. The translation layer manages communication between SCO devices and the backend systems so each communicates with each other according to their respective formats (e.g.

Abstract: Some systems and methods are directed to a device agnostic architecture configured to control and/or manage the interactions between any front end store systems (e.g., self checkout (SCO) systems) for capturing purchase items and backend systems (e.g., point of sale (POS) subsystems) for completing purchase of the items. The device agnostic architecture can include a translation layer or translation component that mediates communications from and/or between the front end and backend systems. For example, the translation layer maps any commands received from any SCO and/or POS device into execution commands native to receiving systems. For example, back-end processing systems can be configured to control on-line identification of products and/or services for purchase, and manage execution of sales of any goods or services. The translation layer manages communication between SCO devices and the backend systems so each communicates with each other according to their respective formats (e.g.

Abstract: A method for purchasing an item using a mobile device is provided. The method includes but is not limited to inputting identification information into the mobile device which identifies the item for purchase and generating an order for the item identified by the identification information. The method also includes but is not limited to displaying on a display of the mobile device an optical machine-readable representation of the order.