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: Provided are a system and method for determining a weight of an item for purchase, comprising determining from a digital image of an item generated by a single camera, a volume of the item, the single camera separated from the item at a distance in a horizontal and vertical direction established by a stationary rigid fixture; identifying the item; accessing a database to determine an average weight per volume measurement unit of the identified item; and calculating a weight of the item from the volume and the average weight per volume measurement unit.

Abstract: Provided are a system and method for determining a weight of an item for purchase, comprising determining from a digital image of an item generated by a single camera a volume of the item, the single camera separated from the item at a distance in a horizontal and vertical direction established by a stationary rigid fixture; identifying the item; accessing a database to determine an average weight per volume measurement unit of the identified item; and calculating a weight of the item from the volume and the average weight per volume measurement unit.

Abstract: Provided are a system and method for determining a weight of an item for purchase, comprising determining from a digital image of an item generated by a single camera a volume of the item, the single camera separated from the item at a distance in a horizontal and vertical direction established by a stationary rigid fixture; identifying the item; accessing a database to determine an average weight per volume measurement unit of the identified item; and calculating a weight of the item from the volume and the average weight per volume measurement unit.

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.