WO2015195415A1 - Systèmes et procédés pour afficher l'emplacement d'un produit dans un point de vente au détail - Google Patents

Systèmes et procédés pour afficher l'emplacement d'un produit dans un point de vente au détail Download PDF

Info

Publication number
WO2015195415A1
WO2015195415A1 PCT/US2015/034919 US2015034919W WO2015195415A1 WO 2015195415 A1 WO2015195415 A1 WO 2015195415A1 US 2015034919 W US2015034919 W US 2015034919W WO 2015195415 A1 WO2015195415 A1 WO 2015195415A1
Authority
WO
WIPO (PCT)
Prior art keywords
location
product
data
map
user
Prior art date
Application number
PCT/US2015/034919
Other languages
English (en)
Inventor
Matthew Kulig
Nathan Pettyjohn
Ed Saunders
Niarcas Jeffrey
Dante Cannarozzi
Original Assignee
Aisle411, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/575,432 external-priority patent/US20150170256A1/en
Priority claimed from US14/632,832 external-priority patent/US20150170258A1/en
Application filed by Aisle411, Inc. filed Critical Aisle411, Inc.
Priority to SG11201610572RA priority Critical patent/SG11201610572RA/en
Publication of WO2015195415A1 publication Critical patent/WO2015195415A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • This disclosure is related to the field of indoor mapping and location, specifically to the use of mobile computing devices to display the indoor location of products based upon vendor-supplied product location and merchandizing fixture data.
  • Retail locations are generally organized by aisle, with related products stored in close physical proximity to one another. Signs are usually hung over the aisles indicating, in relatively broad categories, the type of products found in the aisle. While this provides consumers with some ability to navigate to the proper aisle, locating a particular product within an aisle may be a chore. This is particularly true where the category of products in the aisle includes a wide variety of different products densely packed together, such as "breakfast cereals" or "wine.” and picking through the many options to find one specific product may be time-consuming and laborious. Further, certain products could fall into several different categories and the categories on the overhead signs may not provide enough information for the consumer to detennine which aisle contains a desired product.
  • yogurt a section but generally do not know in advance which specific flavors of yogurt they plan to purchase. Instead, they peruse the available options once they find the yogurt section. Thus, if the user searches a product database for "yogurt,” dozens and possibly hundreds of results may be returned, when the user simply wishes to know generally where the yogurt is.
  • a method for displaying a location visualization to a user comprising: providing a server communicatively coupled to a non-transitory computer-readable server memory, the computer system being communicably coupled to a data network; providing a user device having a user device memory and being communicably coupled to the data network; receiving retailer data for a retail location, the retailer data comprising product data for a plurality of products offered for sale at the retail location; receiving planogram data for a retail location, the planogram data comprising: fixture location data indicative of the relative positions of and dimensions of a plurality of fixtures in the retail location; for each fixture in the plurality of fixtures, an indication of at least one product stocked on the each fixture, the at least one product being a product in the plurality of products in the retailer data; for each fixture in the plurality of fixtures, calculating a map point in the retail location, the calculated map point being determined least in part based upon the relative position of the each fixture in
  • the data network is the Internet.
  • the user device is a smart phone or tablet computer.
  • the unique identifier is a serial number.
  • the search criteria is a text string.
  • the search criteria is a product identification code.
  • the location visualization is a pindrop.
  • retailer data comprises, for each product, product name, product description, or product category.
  • planogram data is received from planogramming software.
  • each calculated map point is a relative position in the retail location with respect to a predefined origin point.
  • the each relative position for the plurality of fixtures is a relative position in the retail location with respect to a predefined origin point.
  • the user device determining the location of the user device in the retail location; the user device displaying on the displayed map image an indication of the position of the user device in the indoor location.
  • each database record for each product further comprises taxonomical data for the each product.
  • the search criteria comprises a synonym for the each product, phonetic data for the each product, and/or slang for the each product.
  • the location visualization further comprises user interface elements for a user to indicate whether the user found the desired product at the location in the store indicated by the location visualization.
  • FIGs. 1A and IB depict an embodiment of a fixture and planogram data pertaining thereto.
  • FIG. 2 depicts an embodiment of a retail location and fixtures, and certain planogram data pertaining thereto.
  • FIG. 3 depicts a schematic diagram of an embodiment of a system and method for providing in-store product location services to a user via a user device.
  • FIG. 4 depicts a flow chart of an embodiment of a system and method for providing in-store product location services to a user via a user device.
  • FIG. 5 depicts a schematic diagram of an embodiment of an augmented product location database.
  • FIG. 6 depicts a schematic diagram of an embodiment of a map point location and translation system used in a product location system and method.
  • the systems and methods described herein are generally implemented in a client- server architecture, with certain preprocessing conducted to set up the system.
  • This preprocessing generally includes creating store maps and a product location database for handling product searches, and a map point system for translating between the product location data and the store maps.
  • the client is typically implemented as a software application on a user device carried by the consumer while in the retail location.
  • the user device may be, but is not limited to, a smart phone, tablet PC, e-reader device, wearable technology, or any other type of mobile device capable of executing the described functions.
  • the user device is network-enabled and communicating with the server system over a network.
  • computer describes hardware which generally implements functionality provided by digital computing technology, particularly computing functionality associated with microprocessors.
  • the term “computer” is not intended to be limited to any specific type of computing device, but it is intended to be inclusive of all computational devices including, but not limited to: processing devices, microprocessors, personal computers, desktop computers, laptop computers, workstations, terminals, servers, clients, portable computers, handheld computers, smart phones, tablet computers, mobile devices, server farms, hardware appliances, minicomputers, mainframe computers, video game consoles, handheld video game products, and wearable computing devices including but not limited to eyewear, wristwear, pendants, and clip-on devices.
  • a "computer” is necessarily an abstraction of the functionality provided by a single computer device outfitted with the hardware and accessories typical of computers in a particular role.
  • the term “computer” in reference to a laptop computer would be understood by one of ordinary skill in the art to include the functionality provided by pointer-based input devices, such as a mouse or track pad, whereas the term “computer” used in reference to an enterprise-class server would be understood by one of ordinary skill in the art to include the functionality provided by redundant systems, such as RAID drives and dual power supplies.
  • ⁇ can refer to a single, standalone, self-contained device or to a plurality of machines working together or independently, including without limitation: a network server farm, "cloud” computing system, software-as-a-service, or other distributed or collaborative computer networks.
  • the term "software” refers to code objects, program logic, command structures, data stmctures and definitions, source code, executable and/or binary files, machine code, object code, compiled libraries, implementations, algorithms, libraries, or any instruction or set of instructions capable of being executed by a computer processor, or capable of being converted into a form capable of being executed by a computer processor, including without limitation virtual processors, or by the use of run-time environments, virtual machines, and/or interpreters.
  • software can be wired or embedded into hardware, including without limitation onto a microchip, and still be considered "software" within the meaning of this disclosure.
  • software includes without limitation: instructions stored or storable in RAM, ROM, flash memory BIOS, CMOS, mother and daughter board circuitry, hardware controllers, USB controllers or hosts, peripheral devices and controllers, video cards, audio controllers, network cards, Bluetooth® and other wireless communication devices, virtual memory, storage devices and associated controllers, firmware, and device drivers.
  • the systems and methods described here are contemplated to use computers and computer software typically stored in a computer- or machine-readable storage medium or memory.
  • terms used herein to describe or reference media holding software including without limitation terms such as “media,” “storage media,” and “memory,” may include or exclude transitory media such as signals and carrier waves.
  • web refers generally to computers programmed to communicate over a network using the HyperText Transfer Protocol (“HTTP"), and/or similar and/or related protocols including but not limited to HTTP Secure (“HTTPS”) and Secure Hypertext Transfer Protocol (“SHTP”).
  • HTTP HyperText Transfer Protocol
  • HTTPS HyperText Transfer Protocol
  • SHTP Secure Hypertext Transfer Protocol
  • a “web server” is a computer receiving and responding to HTTP requests
  • a “web client” is a computer having a user agent sending and receiving responses to HTTP requests.
  • the user agent is generally web browser software.
  • network generally refers to a voice, data, or other telecommunications network over which computers communicate with each other.
  • server generally refers to a computer providing a service over a network
  • client generally refers to a computer accessing or using a service provided by a server over a network.
  • server and “client” may refer to hardware, software, and/or a combination of hardware and software, depending on context.
  • server and “client” may refer to endpoints of a network communication or network connection, including but not necessarily limited to a network socket connection.
  • a "server” may comprise a plurality of software and/or hardware servers delivering a service or set of services.
  • host may, in noun form, refer to an endpoint of a network communication or network (e.g., "a remote host"), or may, in verb form, refer to a server providing a sendee over a network ("hosts a website"), or an access point for a service over a network.
  • fixture and “merchandizing fixture” generally refer to a structure or location within a retail location on which products are stored, kept, and/or displayed for sale.
  • Fixtures are generally physical structures, such as shelving units, end caps, window displays, display cabinets, point-of-sale displays, and gondolas. Fixtures may be attached to a building or structure, or may be freestanding or mobile. As used herein, the term “fixture” may, in certain contexts, refer to only part of a physical structure. A “fixture” may be an entire shelving unit (i.e., the shelves on both sides), only one side of a shelving unit, or only one section or region of a shelving unit.
  • an aisle fixture in a grocery store generally comprises a plurality of vertical stacks of adjustable-height shelving, each of which is chained together to form the length of the aisle.
  • Each such vertical shelving stack may be considered both a fixture unto itself, and a subfixture of a larger fixture (the aisle).
  • An embodiment of such a fixture (101) is depicted in FIG. 1A, which indicates a fixture (101) comprising three subfixures (103).
  • the term "fixture” is generally used herein to refer to both an entire shelving unit (101) or one or more subfixtures (103).
  • Fixture may in certain embodiments mean a location where products are stored or displayed for sale, even if a physical structure is not included.
  • a retail location may, as a marketing tactic, stack cases of soda or beer to form a local sports team logo in advance of a major game featuring that team, which display may not necessarily make use of any physical structures, but rather only the products themselves.
  • product generally refers to goods, services, materials, merchandise, or other tangible or intangible items of value offered by a retailer for sale, rental, lease, or other commercial use by a customer. It will be understood by one of ordinary skill in the art that “product” can refer to a general type or category of products (e.g., "soda”), a particular brand or type of product in such a category (e.g., "Coca-Cola®”), or a particular shipping or distribution configuration of such a product.
  • a two-liter bottle of a particular soda may be a different "product" from a twelve-pack of cans of the same soda, which both may be considered different "products” from twenty-ounce twist-top plastic bottles of the same soda. These may also be the same product, depending on how the term is used in context.
  • the term "retailer data” generally refers to data about product inventory at one or more retail locations.
  • this data typically includes information such as, but not necessarily limited to: product name; product description; product category; product category tier; product location; multimedia data (e.g., digitized photos, video, branding assets, audio, or other content pertaining to the product); one or more unique product identification codes or identifiers, such as but not limited to, universal product code ("UPC”) and/or stock keeping unit (“S U”); and, other product attributes.
  • UPC universal product code
  • S U stock keeping unit
  • product attributes may be any attribute for the product, such as (but not limited to) attributes that are primarily of interest to consumers in making the purchasing decision, such as low-sodium, gluten-free, made-in-America, organic, heart-healthy, union- built, fair trade, and the like.
  • attributes that are primarily of interest to consumers in making the purchasing decision, such as low-sodium, gluten-free, made-in-America, organic, heart-healthy, union- built, fair trade, and the like.
  • a product may have a plurality of product descriptions in the retailer data.
  • planogram is a term of art in the retail industry and generally refers to visual representations of the location, organization, layout, or placement of products and/or services offered by a retail location, generally with respect to a specific fixture.
  • a planogram is typically, but not necessarily, a two-dimensional or "flat" diagram or model showing the placement of products on the fixture. While planograms may be implemented using paper and other media, planograms are usually created using planogramming software products.
  • a planogram pertains to, describes, or is associated with a fixture (101) or subfixture (103), and includes data about the location and dimensions of one or more organizational dividers, such as shelving (105). Accordingly, a given fixture (101) may have a plurality of associated planograms. Planograms are also sometimes also referred to in the art as piano-grams, plan-o-grams, schematics, or POGs.
  • planogram data generally refers to planning and location data for a retail location, such as but not necessarily limited to fixture (101) location and size, shelf location and size within a fixture, and product stocking location and size within a fixture or shelf.
  • Planogram data for a particular retail location generally comprises data for the plurality of planograms which describe the inventory layout at that retail location. This data is typically organized hierarchically, and is stored, maintained, or organized in planogramming software or other inventory management systems, such as but not necessarily limited to JDA.
  • planogram and retailer data may be intermingled.
  • retailer data and planogram data are generally described and used herein to refer to two different sets of data, it will be understood by one of ordinary skill in the art that, in a particular embodiment, retailer data could include some or all of the data described herein as planogram data, and/or planogram data could include some or all of the data described herein as retailer data.
  • the term "image” generally refers to a data record or representation of visually perceptible information. It will be understood by one of ordinary skill in the art that this includes, but is not limited to, two-dimensional still images and digital photographs, as well as three-dimensional pictures, holograms, and video.
  • image generally refers to a data record or representation of visually perceptible information. It will be understood by one of ordinary skill in the art that this includes, but is not limited to, two-dimensional still images and digital photographs, as well as three-dimensional pictures, holograms, and video.
  • specific commercial or branded products may be described or identified as illustrative or exemplary embodiments of particular technologies.
  • MySQLTM is known in the art to be an implementation of a database. It will be understood by one of ordinary skill in the art that such products inherently or implicitly disclose the broader category of products of which they are representative.
  • MySQLTM further discloses any database implementation, such as but not limited to, Oracle®, PostgreSQLTM, and other database systems, whether or not tabular or
  • FIG. 3 depicts a general overview of an embodiment of the systems and methods described herein.
  • the depicted embodiment generally comprises accessing/receiving and analyzing/processing retailer data (31 1) and planogram data (313).
  • the data (311) and (313) is generally processed programmatically/procedurally, manually, or both. This processing generally initializes and populates a product location database (601 ) communicatively coupled to a server (309).
  • the product location database (601 ) generally comprises product information from retailer data (31 1) augmented with taxonomies and grammars, and, for each product, map point identifiers associated with a given location in the store where the product may be stocked.
  • the processing also generally produces a map bundle (315) comprising map images (317) of the retail location, and data (319) for translating map points to pixel locations on the map images (317) to facilitate location visualization on the user device (303).
  • the map images (317) are generally created by analyzing planogram data (313) and performing mathematical operations to determine the location of fixtures and possibly other features within the store, and generating map images (315) reflecting the relative locations of the identified features.
  • the system may further include application software (321), which may be a standalone application or a web browser accessing a web site, on a user device (303) for downloading and/or displaying the map images (315) and transmitting product search requests from the user (301) to the server (309), and displaying an indication of the returned product location data on the displayed map images.
  • application software (321)
  • the system generally further includes server (309) software for fielding user search requests.
  • a product location database (601) is created or, if such a database (601) already exists, updated.
  • FIGs. 3, 5, and 6 depict embodiments of such a database (601).
  • This database (601) when populated, generally comprises data about the products for sale in the retail location and associated locations of those products in the store.
  • This database (601) is preferably created programmatically, at least in part from retailer data (31 1) and/or planogram data (313). This is usually done by processing retailer data (31 1 ) and planogram data (313) to identify unique products in the data, and creating one or more rows in the product location database (601) for each product identified.
  • This database (601) is generally used for locating retail products in response to user (301) searches.
  • a common problem with retailer data (311) is that products may be identified in industry jargon and shorthand. For example, a twelve-pack of twelve-ounce Coca-Cola® soda cans may be identified in retailer data (311) in shorthand, such as "CK PK 120Z.” Thus, a user who provides "coke “ or "soda” as a search term will not match this product.
  • retailer data (31 1) may be augmented in the databae (601) by taxonomies and grammars, which may include phonetic data, synonyms, and/or slang.
  • An embodiment of such an augmented database (601) is depicted in FIG. 5.
  • product data for a carbonated beverage is augmented with phonetic data (503) ("coe cah coe la " '), a synonym (501) ("coca cola"), and a plurality of slang terms (505) ("coke,” “soda,” “pop).
  • phonetic data 503
  • 501 coca cola
  • slang terms 505
  • Augmenting the database (601) may be done automatically, manually, or both.
  • the product location database (601) can identitfy products at different levels of detail, precision, or granularity.
  • a user searching for "pop” or “soda” may be assumed to be interested in product location at the aisle level, whereas a user searching for "coke” or “pepsi” may be interested in product location at the brand (sub-aisle) level.
  • a user searching for "coke 20oz” may be interested in a very specific packaging configuration.
  • products may be organized into, or associated with, one or more category tiers or product taxonomies in the database (601 ), which may be used to estimate the desired precision level of the server response.
  • the database (601 ) is generally created, stored, maintained, and updated in memory, generally but not necessarily a non-volatile computer-readable storage medium.
  • the database (601) is generally communicatively coupled to the server (309).
  • the database (601) may be on storage within the same physical chassis as the location server, or on another server, such as but not limited to a cloud computing platform (not depicted).
  • map images are created or generated.
  • the map images are generated at least in part from planogram data, though map images may also be improved, augmented, or otherwise supplemented by other data sources as well, or manually edited.
  • the generated map images described herein indicate the overall layout of major store features, such as walls, entranceways, checkout counters, customer service counters, store departments, restrooms, and/or fixtures.
  • FIGs. 1A, IB, and 2 depict embodiments of a fixture and store layout, respectively, which may clarify the data and measurements described herein.
  • Fixtures (101) are identified in planogram data (and/or retailer data) by fixture location data.
  • Fixture location data generally comprises a relative location (203) of the fixture (101) in a store (201 ). This relative location (203) may indicated by, for example, a set of coordinates at which the fixture (101) is located (203) relative to a fixed origin point (205) in the store (201 ).
  • the coordinates may be two- or three-dimensional.
  • the retail location origin point (205) is the southwest corner of the retail location (201), and the fixture (101 ) is located ten feet east (207) and twenty feet north (209) of the store origin point (205).
  • the coordinates indicate the relative location (203) of a predefined point or element of the fixture (101).
  • the predefined point (21 1 ) on the fixture (101) located at these coordinates (207) and (209) is the bottom left corner (211).
  • fixture location data for this fixture (101) indicates that the fixture (101) has relative location (203) coordinates (207) and (209) of ⁇ 10' , 20' ⁇ .
  • Fixture location data may further comprise the dimensions (213) and (215) of the fixture (101). Although only two dimensions are depicted, three dimensions may be provided in fixture location data.
  • the combination of the relative location (203) of the fixture (101) and its dimensions (213) and (215) is generally sufficient to generate a map image (317) indicating the location and size of the fixture (101) with respect to the retail location (201).
  • map images (317) may be generated without other data, though other data is generally used to facilitate the product location systems and methods described herein.
  • a retail location (201) there generally will be a plurality of fixtures (101 ), and thus a plurality of fixture location data sets in the planogram data (313).
  • planogramming software creates one or more planograms.
  • a planogram (107) is created for a subfixture (103).
  • the scope and extent of a subfixture described by a given planogram may vary from retail location to retail location, and may vary from aisle to aisle within a retail location, as described elsewhere herein.
  • planograms (107) there may be one or more planograms (107) created.
  • the relative location (109A) on the fixture (101 ) described by the planogram (107) is also indicated in planogram data (313).
  • the relative locations (109A-B) are each a position relative to an origin point (11 1 ) on the fixture (101). This origin point (1 1 1) may be the same element of the fixture (101) as the point (21 1) used to determine the location of the fixture in the store (1 1 1), or may be a different point.
  • Planograms (107) are generally ordered for a given fixture (101) (e.g., there is a first, second, third, etc., planogram for Fixture A, and a first, second, third, etc., planogram for Fixture B, and so forth).
  • the origin point (1 1 1) for the fixture (101 ) for purposes of planogram relative locations (109A-B) is generally a known, pre-defined, or understood origin point (1 1 1 ).
  • the first planogram (107) for the depicted fixture of FIGs. 1A and I B may have an associated relative location (109 A) of two inches in from the bottom left corner (1 1 1) of the fixture (101 ) (as determined when facing the fixture).
  • a second planogram (not depicted) for the fixture (101) may have an associated relative location (109B) of five feet and two inches from the bottom left corner (1 1 1) of the fixture (101).
  • the planogram data (313) may further comprise the dimensions of the planogram, which are generally the dimensions of the subfixture (103) which the planogram (107) describes. Mathematical calculations may be performed to determine where in a retail location (201) the subfixture (103) or planogram (107) is located. Although individual subfixtures and planograms are generally not depicted on generated map images (317), the data described above is sufficient to do so and it is specifically contemplated that they could be.
  • planogram data (313) generally further comprises shelf location data. It is common that shelf (105) placement in a fixture (101) and (103) is adjustable, to accommodate the specific types of products to be stocked, and shelf (105) placement for a given fixture (101) and (103) may differ substantially from another, even if the fixtures are physically near each other in the store (201) (e.g., adjacent subfixtures (103) in an aisle). Shelf (105) location data is generally a relative location (113) of each shelf (105) described in a planogram (107) with respect to an origin point (1 15) in the planogram (107).
  • the planogram (107) depicts five shelves (105A-E) in a subfixture (103), the first shelf (105 A) being at the origin point (1 15) and having shelf (105) location coordinates of ⁇ 0, 0, 0 ⁇ .
  • the second depicted shelf (105B) may be, for example, two feet above the first shelf (105 A), and thus have a shelf location of ⁇ 0, 0, ⁇ .
  • Each shelf location data set may further comprise the dimensions of the shelf (105), such as the width, depth, and available stocking region height (i.e., the amount of vertical distance above the shelf available for storing products).
  • planogram data (313) further comprises stocking region data about one or more stocking regions for a shelf.
  • a stocking region is generally the physical space in a subsection of a shelf allocated for stocking a particular product (123).
  • stocking region data generally comprises a relative location (1 19) of the stocking region (117) with respect to an origin point (121) on the shelf (105B).
  • Each stocking region data set may further comprise the dimensions of the stocking region, such as the width, height, and original point
  • the dimensions of the stocking region such as the width, height, and original point
  • the products are jars (123), each having a diameter of four inches and a height of five inches, and the jars (123) are stocked three-across and one-high
  • the products have a stocking region (1 17) about twelve inches wide and about five inches tall.
  • the stocking region (1 17) size may be larger than the products to allow for spacing and padding.
  • Stocking regions may also have additional dimensions, such as depth into the shelving unit, but generally speaking this dimension is not used because products (123) are typically stocked in rows extending to the back of the shelf (105B).
  • Stocking region data may also comprise an indication of the specific product to be stocked in the stocking region.
  • This indication may be an index into other data, such as a unique index into retailer data (31 1).
  • Mathematical calculations may be performed to determine where in a retail location (201) a given stocking region (117) is located. Although individual stocking regions (1 17) are generally not depicted on generated map images (317), the data described above is sufficient to do so and it is specifically contemplated that they could be.
  • the location of the stocking region in the store is generally considered the location in the store of the product stocked in the stocking region.
  • planogram data (313) indicates the location of fixtures, subfixtures, planograms, shelves, and stocking regions using relative offsets with respect to an origin point in the hierarchy described herein, in certain alternative embodiments, coordinates or locations may be relative to other units of organization.
  • stocking regions could be provided with respect to the store, as opposed to the shelf on which the stocking region is located.
  • a location could be provided in absolute coordinates according to a general location system, such as GPS coordinates, rather than a relative offset in a hierarchy.
  • dimensions could be replaced by coordinates for an opposing corner of a fixture, planogram, shelf, or product stocking region, in which case the dimensions can be calculated.
  • planogram data (313) described above may optionally include a rotation angle. This is common for fixtures, but may be possible for any of the location data described. For example, aisles are generally assumed or defaulted to be oriented lengthwise from the front to the back of a retail location. However, certain fixtures, such as endcaps, are oriented at a right angle. For such fixtures, planogram data (313) for the fixture may further comprise orientation data indicating the angle of rotation (127) for the fixture (101) with respect to an origin plane or axis (125).
  • the planogram data (313) may assume that all fixtures, even if oriented lengthwise with respect to the store, are by default oriented in a particular fashion.
  • the system may assume that shelves open to the left as one faces the back of the store.
  • a rotation angle of 180 degrees (127) may be indicated in the planogram data (313) for that fixture (101).
  • orientations are 90 degrees, 180 degrees, or 270 degrees, but other orientations are possible. Rotation angles may also be applied to movable or temporary displays, which are more likely to be oriented at unusual angles.
  • planogram data (313) is used to generate map images (317) for the retail location. While the detail level of the generated map images (317) is generally not more granular than the fixture or subfixture level, the data above is sufficient to depict more granular detail in the map images (317), up to and including the stocking region level of detail. While this may be used in certain embodiments and use cases, such as administrative tools like a manual map editor, in the typical embodiment, additional detail results in a visually unappealing, cluttered map, particularly when viewed on the relatively small displays of handheld user devices.
  • the map images (317) are generally generated by creating raster images or other digitize images. This may be done by, for example, populating a pixel matrix in memory based upon the calculated position of the retail location's (201) major features and fixtures (101), and storing the matrix in a standard-compliant image format. Other techniques for generating map images (317) are known to those having ordinary skill in the art. Since the maps are generally used in consumer-grade applications, and are generally downloaded over wireless data networks, the format is preferably a lossless compressed format such as, but not necessarily limited to, the Portable Network Graphics (PNG) format. In an alternative embodiment, the map images (31 ) may be generated as vector graphics.
  • PNG Portable Network Graphics
  • the map images (317) are generally organized into a plurality of tiled image sets, wherein each one of the tiled image sets represents a complete map of the retail location (201) and its features and fixtures (101) at a particular view magnification level, or "zoom" level. In essence, this means each tiled image set is indicative of the same overall data (i.e., store layout with fixtures), but at differing map image resolutions. This technique is used to overcome the inherent limitations of raster images, which pixelate when scaled and thus give the appearance of quality degradation.
  • drawing instructions for procedurally generating one or more store maps may also be generated.
  • Such instructions generally comprise a plurality of polygon and/or line or vector definitions indicating the size, shape, placement, dimensions, and aesthetic attributes (e.g., color, borders, shading, gradients, shadows, etc.) of polygons and lines which appear on the map.
  • This data may be stored in any format, but in the prefen-ed embodiment, is encoded in a standardized markup language such as Extensible Markup Language (“XML").
  • XML Extensible Markup Language
  • Such data is generally included in a map bundle (315) for a particular store.
  • drawing instructions are encoded as Scalable Vector Graphics ("SVG").
  • map images (317) and drawing instructions are generally packaged into a downloadable compressed archive referred to as a map bundle (315). Generally, one such bundle is created for each retail location. As described elsewhere herein, the map bundle (315) will generally further comprise data for translating a map point to a pixel location on a map image.
  • margin of error should be anticipated at each level (i.e., fixture, piano gram, shelf, stocking region) because the actual location of fixtures, shelves, and stocking regions will usually vary at least slightly from that indicated in the data. As errors compound, the calculated product location will generally differ from the actual location. While it is often the case that the margin of error is a matter of inches, nearly undetectable by the user, larger margins are of course possible. This disclosure is no way depends upon or requires data to be completely accurate.
  • map points reduce redundant data and provide a clean, simple interface which provides the user with product location at the desired level of precision.
  • each map point is identified by a scalar numeric identifier, which is unique for at least a particular store, but a map point may be any type of identifier which can be uniquely indexed.
  • Map points are typically determined by calculating the midpoint of the physical region in the store to which they apply. Also, the corresponding location of that midpoint on the generated map images (317) is calculated, and translation data is calculated for inclusion in the map bundle (315) for the store. This allows the unique identifier for the map point to be translated to the calculated corresponding locations on the generated map images (317). Alternatively, they may be selected using a particular representative map point, such as a location associated with a particular representative product or a "best match " of available products.
  • the product location database (601) entries for those products include an indication of the unique identifier for the corresponding map point. For example, where a given map point corresponds to a subfixture as defined by a specific planogram, all products indicated in the planogram data (313) as being stocked on the subfixture described by the planogram will generally have their rows in the product location database (601) updated or modified to reference the map point for that subfixture. This allows a search for any of those products to return the same map point identifier, thereby guiding the user to the general area where the products are sought.
  • FIG. 6 depicts a schematic diagram of an illustrative example of the use of map points.
  • the server system (309) generally is communicably coupled to the product location database (601).
  • the depicted database (601) comprises a table (603) or other data structure which contains, among other things, product-to-map point associations.
  • the depicted embodiment seven entries (605A-G) are present and each table (603) entry (605A-G) has at least two data components: a product identifier (602) and a map point identifier (604).
  • the depicted map point identifiers (604) are positive integers, but other types of identifiers are possible.
  • the product identifier (602) is depicted only in retailer data (31 1) format, but as described elsewhere herein, this data is generally augmented with phonetics, slang, synonyms, and taxonomical data to improve product lookup accuracy and otherwise improve the usefulness of raw retailer data (31 1), such as depicted in FIG. 5.
  • the first four depicted table (603) rows (605A-D) are for Coca-Cola® products and each is associated in the table (603) with map point identifier (604) seven.
  • the next two depicted entries (605E-F) are for Dr. Pepper® products, and are associated in the table (603) with map point identifier (604) eight.
  • the last depicted entry (605G) is for a Pepsi® product, and is associated in the table (603) with map point identifier (604) nine.
  • Each of the map point identifiers (604) corresponds to a physical location (607A-C) in the retail location (201 ).
  • map point identifier (604) seven corresponds to a point (607A) generally at the middle of a specific subfixture (103, 609).
  • the location of map point (607 A-C) may be manually determined, but can also be programmatically calculated from planogram data (313).
  • planogram data (313) By way of example and not limitation, because the starting point and width of the subfixture (103) can be determined from the planogram data (313), a midpoint can be calculated by dividing the width in half and adding the quotient to the y-coordinate for the starting point of the subfixture (103). This midpoint can then be used as the map point (607 A) for the subfixture (103).
  • Using a midpoint is desirable because the map point ultimately is used to determine where on the map images (317) a location visualization will be displayed, and that point is where users are likely to visit. The use of a midpoint centers the user on the subfixture.
  • the system repeats the process, selecting a new unique map point identifier and calculating the location of the map point (607B) using the same technique described above.
  • the map point identifier (604) for the new map point (607B) is simply incremented (to eight) and products in the planogram for that subfixture (103, 61 1 ) are stored in the table (603) and associated with map point identifier (604) eight.
  • This process continues in like fashion through the planogram data (313) for other subfixtures (613) until all map points have been calculated and the applicable products (602) for each have been associated in the table (603) with the corresponding map point identifiers (604).
  • map point (607A-C) Once the location of a map point (607A-C) is known, the corresponding location of each map point (607A-C) on map images (317) can likewise be determined. Again, this may be done manually but is preferably done programmatically using mathematical techniques known in the art, including but not limited to basic ratio conversion techniques such as cross- multiplication.
  • the system can then generate translation data to programmatically translate a map point identifier (604) into a pixel location (617) on a map image.
  • XML data (615) may be generated which identifies the map point (607A) by its unique identifier (604), and provides the X- and Y-coordinates (617) for that map point (607A) on a particular map image.
  • map point seven (607A) is calculated as corresponding to the pixel located at ⁇ 100, 450 ⁇ on a particular map image, and thus the system generates XML data (615) indicating that the X- coordinate (617) for map point seven (607A) is 100, and the Y-coordinate (617) for map point seven is 450, for the particular map image.
  • this translation data (615) is packaged into the map bundle (315) for the retail location, along with the map images (317).
  • map points address the problem of broad search criteria returning multiple hits which, if all displayed, would clutter the screen.
  • any search for a Coke® product will match potentially dozens of different Coke® products in various packaging configurations, but since most of the products are stocked in the same general area of a typical store, most of the products will map in the database (601) to the same map point identifier.
  • the server will respond with the same map point and the user device (303) will display the location visualization in the same place on the map image. This improves searching and reduces redundancy and screen clutter.
  • the system can field product search requests from users.
  • An embodiment is depicted in FIGs. 3 and 4.
  • Product location searches and other user interactions with the server (309) system are generally carried out indirectly using end-user client software (321).
  • the software application is generally stored in the memory systems of the user device (303) and loaded and executed by a microprocessor on the user device (303), as is known in the art.
  • the software application may be a special-puipose application specifically designed for this purpose, such as but not necessarily limited to the aisle41 1 ® product location application, or may be an application or service delivered through an alternative or more general-purpose framework, such as a web browser.
  • a user (301) having a user device (303) enters a retail location (201) to use the application (321).
  • the user device (303) is a personal device (303) brought by the user into the retail location (201).
  • the user device (303) is generally communicating over a data network (305), such as the Internet.
  • the user device (303) typically includes geolocation technologies, such as a GPS receiver, which can use a geolocation system (307) to determine the approximate location of the device (303) on the Earth.
  • This location is then transmitted to a server system, which may be the same server (309) system used for product location services, or a different server system, over a telecommunications network (305).
  • the server then identifies and/or determines nearby stores for which map bundles (315) are available and transmits to the user device (303) an indication of such stores.
  • the user device (303) displays a visualization of the received store list to the user.
  • the user device (303) may display an outdoor map of the area in the vicinity of the detected user device (303) location and indicate on the displayed outdoor map stores for which the server system (309) has map bundles (315).
  • the user may then select the store (403) for which the user desires to use the product location services.
  • the server system (307) transmits or causes to be transmitted (407) to the user device (303) the map bundle (315) for the store (201) identified by the user.
  • the map bundle (315) is stored in local memory on the user device (303).
  • the server may then determine the same data with respect to the version of the map bundle (315) indicated as current in the server (309). If the data does not match, or otherwise is indicative that the server version of the map bundle (315) is newer, the server system transmits the newer map bundle (315) to the user device (303).
  • the user device (303) displays (41 1) one of the downloaded map image sets on a display of the user device (303).
  • the displayed image set is generally selected automatically based upon a default magnification level setting.
  • the software application In addition to map images (317), the software application generally presents graphical user interface elements for manipulating the interface.
  • One such element is an input element for the user to provide search criteria (413) indicative of a product the user wishes to locate in the store.
  • the input element may be a text input element, such as a text box, in which case the user may type the terms or speak the terms using an automatic voice recognition text-to- speech system.
  • the input element may be an audible input element.
  • the input element may be a visual input element, such as a photo capture or image capture element.
  • the search criteria may comprise a product identification code, such as a UPC or SKU. The search criteria provided by the user are transmitted to the server (415) over the network (305).
  • the server (309) receives and processes the search criteria, and attempts to locate a matching (417) product (or plurality of products) in the database (601). As described above, products in the database are generally associated with a map point identifier (604). If any matches are found (417), the server prepares a datagram comprising an indication of the corresponding map point identifier (or a plurality thereof, as applicable). The server may also include in the datagram other data about the matching products, such as data found in the retailer data (31 1). This data is then transmitted (421) to the client application (321). If no match is found, the server (309) indicates as such to the client application (321) over the network, which then notifies the user (419). The user may then enter alternative search criteria (413) and restart the search process.
  • the client device uses the map point translation data (319) in the map bundle (315) to determine (423) where on the currently displayed map image (317) to display a location visualization.
  • the application (321 ) displays a location visualization (425) at the determined location or locations.
  • the user may then enter different search criteria (413) as described previously to search for other or alternative products, or refine the prior search.
  • the location visualization (415) is a visual indication on the application (321) graphical user interface of where the searched-for product is located on the map image (317).
  • the location visualization (425) may be a "pindrop,” which is a graphical image of a pin overlayed on the map such that the point of the pin is at a location on the map image (317), generally corresponding to the location of the product in the store as defined in planogram data (313).
  • a map point may be correspond to a specific aisle, a sublocation within an aisle ⁇ e.g., one side of the aisle, or a subfixture within a side of an aisle), or a department in the retail location.
  • aisle-level data may be all that is available for certain products, such as seasonal items, in which case the entire seasonal aisle may correspond to a single map point which, as described elsewhere herein, is generally calculated to be the mid-point of the aisle for display and user orientation purposes.
  • no planogram data (313) is available due to the nature of the product.
  • produce in a grocery store generally has no corresponding planogram data (313).
  • a single map point may be detemiined for the produce department, and in the product location database (601), products with a "produce" category tier are associated with the produce department map point.
  • a search for any type of produce will yield, a minimum, the produce department as a location for the product.
  • the absence of data may be considered an indication that the store does not stock the product at all, and appropriate notification is provided to the user device (303).
  • the search criteria may be used to determine the level of location precision provided.
  • a given product may be associated in the product location database (601) with a plurality of map points, depending upon which layer of the taxonomy matched the user-supplied search criteria.
  • all carbonated beverages in the product location database (601) may have taxonomical data associating those products with a high-level product category tier for "soda.” Thus, when a user searches for "soda," all such products match.
  • the server may return a map point associated with the entire soda aisle because the search criteria provided was broad, even though more precise map points within the soda aisle are available for specific soda products.
  • the search criteria does not supply sufficient data to determine which specific soda products (and thus, which map point or points) are relevant to the user, aisle- level precision is provided.
  • a generic map point for the soda aisle is not returned, because it can be programmatically determined, based upon the specificity of the request that a more precise location is desired.
  • the categorical precision of the search term is used to determine the location precision of the server response. This is generally done by programmatically examining the level of the taxonomy which matched the search criteria.
  • This system has the advantage of not only providing product location services at a level of precision corresponding to the typical use case, but reducing the download size of the map bundle (315) and the amount of storage required on the end-user device (303). If the pinpoint location of every product in the store were provided, the map bundle (315) data could become prohibitively large, as it would include location data for tens of thousands of products, when the user likely is only interested in a few dozen.
  • Another advantage of the map point system is that updating the database (601) to account for changes in store layout, such as a reset, is simpler and faster. Rather than having to re-calculate and update the precise pixel location on each map for every product, the map point associated with the product merely changes.
  • the software application (321 ) is programmed to re-create a planogram for a fixture or subfixture.
  • the device (303) can then display the planogram to the user.
  • a particular product sought may be highlighted or otherwise indicated in the re-created planogram.
  • the client may request a re-created planogram from the server, which will re-create a planogram for a fixture or subfixture, and transmit the re-created planogram to the end-user device (303).
  • the user may indicate whether a sought product was in fact found at the location indicated by the system.
  • the system supports crowdsourcing.
  • User-provided data may then be incorporated into the server-side database (601) to flag potentially erroneous records for manual review.
  • users may be provided with feedback from prior users seeking the same products.
  • the interface on the end- device (303) application may indicate how many prior users searching for the same products reported that they were able to find the product at the indicated location. This data may help users assess the accuracy of the product location data, and correct user errors, such as going to the wrong aisle or selecting the wrong store.
  • map images (317) may be produced manually using map editing and creating software. This is particularly useful where planogram data is incomplete, inaccurate, or simply unavailable.
  • the map is created with reference to manually-captured measurements. For example, the actual distances and dimensions of fixtures and locations of products thereon may be manually determined.
  • planogram data (313) is manually generated for a store and used to generate map images (317). This process is time-consuming, and in an embodiment, may be augmented through the use of hand-held product identification scanners, such as a UPC scanner. Such handheld scanners may also interface with a user device to facilitate quick storage of the scanned information.
  • this may also be done using the user device (303) application (321), such as by imaging product identification codes using imaging hardware integrated into the user device (303).
  • the internal sensors of the user device may be used to detect the device's movement through the retail location, providing at least some automated location detection of products. That is, if a scanning session is begun and the device detects that the user has walked 10 feet, and then a product is scanned, the device can store in memory that the scan was conducted ten feet from the starting point.
  • internal device sensors can be used to detect changes in orientation, such as the user turning and changing direction.
  • a map may be hand-drawn on a device, such as a tablet PC, and edited using map editing software.
  • the systems and methods further integrate with inventory management or point of sale data to provide additional information, such as available quantities, prices, and other commercial data about the products.
  • This data may also be included in the product location database (601) for the products, and some or all of this data may be included in the datagram transmitted to the client application (321) in response to a search request, and some or all of such received data may be indicated or displayed to the user.
  • Retailer data (311) and/or planogram data (313) may occasionally be updated or altered.
  • the updated data (31 1) and (313) may indicate that some products have been discontinued, added, or restocked in a different location. Such data (311) and (313) may change on a regular schedule, such as a weekly or seasonal update.
  • the updated data (31 1) and (313) may also indicate relocated or changed fixture locations and/or dimensions, and/or changed shelf placement and/or stocking inventories.
  • the database (601 ) may be updated to reflect changes in such data (31 1 ) and (313). This may be done by identifying changes in the new data (31 1) and (313) as compared to the existing state of the database (601) and updating products for which location data has changed. However, it some circumstances it may be desirable to simply re-generate the database (601) and/or map bundles (315) from scratch based on the new data (31 1 ) and (313).
  • the application (321) may use indoor location technologies, whether now known or in the future developed in the art, to determine the location of the user device (303) in the store. Such technologies may include, without limitation, the use of beacons, inertial dead-reckoning, magnetic fingerprinting, Wi-Fi signal fingerprinting, and other Wi-Fi-based location technologies. By way of example and not limitation, one such technology is described in United States Utility Patent Application serial number 13/943,646, filed July 16, 2013, the entirety of which is incorporated herein by reference.
  • the application (321) may automatically detect available indoor location systems, and/or may query the server for a list of available indoor location systems available at the store. The user may then be provided a graphical user interface by which the user may select which indoor location systems the user wishes to use.
  • the application (321) allows the user to search for products without identifying a specific store.
  • the database (601) or a plurality of databases (601) may be consulted to determine all stores indicated in the database (601) to stock the matching product, and the user may be provided with a list of matching stores near the user based on the user's currently detected location.
  • the user's detected location is generally determined using integrated location technologies in the user device (303), such as a GPS receiver.
  • the systems and methods provide user analytics.
  • Such analytics may be developed based upon, among other things, user searches, user locations, and purchasing patterns.
  • a user is determined to have searched for a particular product, and sales data indicates a sale of the searched-for product
  • analytics may be developed concerning the relationship between searched-for products using the systems and methods and user purchasing decisions.
  • Such analytics may be then be used to refine, adjust, or supplement other components of the system, such as but not necessarily limited to: map generation; map point calculations; volume, prices, sales and related variables; and, search and matching algorithms.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne des systèmes et des procédés pour fournir une recherche de produit et des recherches d'emplacement à un utilisateur dans un point de vent au détail à l'aide d'un dispositif utilisateur personnel d'un tel utilisateur. Les systèmes et les procédés génèrent des cartes de magasin à partir de données de détail et de diagramme de planification, qui sont téléchargées sur le dispositif utilisateur, et l'emplacement de produits recherchés par l'utilisateur est indiqué sur la carte à l'aide d'une visualisation d'emplacement.
PCT/US2015/034919 2014-06-16 2015-06-09 Systèmes et procédés pour afficher l'emplacement d'un produit dans un point de vente au détail WO2015195415A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
SG11201610572RA SG11201610572RA (en) 2014-06-16 2015-06-09 Systems and methods for displaying the location of a product in a retail location

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US201462012882P 2014-06-16 2014-06-16
US62/012,882 2014-06-16
US201462017066P 2014-06-25 2014-06-25
US62/017,066 2014-06-25
US14/575,432 US20150170256A1 (en) 2008-06-05 2014-12-18 Systems and Methods for Presenting Information Associated With a Three-Dimensional Location on a Two-Dimensional Display
US14/575,432 2014-12-18
US14/632,832 2015-02-26
US14/632,832 US20150170258A1 (en) 2008-06-05 2015-02-26 Systems and Methods for Displaying the Location of a Product in a Retail Location

Publications (1)

Publication Number Publication Date
WO2015195415A1 true WO2015195415A1 (fr) 2015-12-23

Family

ID=54935982

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/034919 WO2015195415A1 (fr) 2014-06-16 2015-06-09 Systèmes et procédés pour afficher l'emplacement d'un produit dans un point de vente au détail

Country Status (2)

Country Link
SG (1) SG11201610572RA (fr)
WO (1) WO2015195415A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3236402A1 (fr) 2016-04-20 2017-10-25 Cefla Societa' Cooperativa Procédé pour l'implémentation correcte d'un diagramme de planification à l'intérieur d'un point de vente
EP3361430A1 (fr) * 2017-02-10 2018-08-15 Jeffrey Pike Procédé et appareil pour entrer dans l'ordinateur des produits dans un système logiciel de l'administration d'inventaire
CN110443662A (zh) * 2018-05-03 2019-11-12 阿里巴巴集团控股有限公司 商品信息处理方法、装置及电子设备
US10698966B2 (en) 2017-05-18 2020-06-30 International Business Machines Corporation Search result prioritization based on device location

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5887271A (en) * 1996-02-20 1999-03-23 Powell; Ken R. System and method for locating products in a retail system
US20030126044A1 (en) * 2001-12-28 2003-07-03 Brooks Lucas Stand-alone intranet search apparatus and system
US20090006418A1 (en) * 2002-12-10 2009-01-01 O'malley Matt Content creation, distribution, interaction, and monitoring system
US20120270573A1 (en) * 2011-04-20 2012-10-25 Point Inside, Inc. Positioning system and method for single and multilevel structures
KR20140024961A (ko) * 2011-06-23 2014-03-03 퀄컴 인코포레이티드 모바일 디바이스를 이용하는 강화된 상점 내 쇼핑 서비스들을 위한 장치 및 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5887271A (en) * 1996-02-20 1999-03-23 Powell; Ken R. System and method for locating products in a retail system
US20030126044A1 (en) * 2001-12-28 2003-07-03 Brooks Lucas Stand-alone intranet search apparatus and system
US20090006418A1 (en) * 2002-12-10 2009-01-01 O'malley Matt Content creation, distribution, interaction, and monitoring system
US20120270573A1 (en) * 2011-04-20 2012-10-25 Point Inside, Inc. Positioning system and method for single and multilevel structures
KR20140024961A (ko) * 2011-06-23 2014-03-03 퀄컴 인코포레이티드 모바일 디바이스를 이용하는 강화된 상점 내 쇼핑 서비스들을 위한 장치 및 방법

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3236402A1 (fr) 2016-04-20 2017-10-25 Cefla Societa' Cooperativa Procédé pour l'implémentation correcte d'un diagramme de planification à l'intérieur d'un point de vente
EP3361430A1 (fr) * 2017-02-10 2018-08-15 Jeffrey Pike Procédé et appareil pour entrer dans l'ordinateur des produits dans un système logiciel de l'administration d'inventaire
US10984374B2 (en) 2017-02-10 2021-04-20 Vocollect, Inc. Method and system for inputting products into an inventory system
US10698966B2 (en) 2017-05-18 2020-06-30 International Business Machines Corporation Search result prioritization based on device location
CN110443662A (zh) * 2018-05-03 2019-11-12 阿里巴巴集团控股有限公司 商品信息处理方法、装置及电子设备

Also Published As

Publication number Publication date
SG11201610572RA (en) 2017-01-27

Similar Documents

Publication Publication Date Title
US20150262120A1 (en) Systems and Methods for Displaying the Location of a Product in a Retail Location
US20150170258A1 (en) Systems and Methods for Displaying the Location of a Product in a Retail Location
US11854071B2 (en) In-store product detection system
US20190005569A1 (en) Methods and systems for automatically mapping a retail location
US10163146B2 (en) Method and system for displaying location based dining recommendation labels in a reduced image area of an interface
CN106165463B (zh) 选择与地理围栏相关的用户
US20150170256A1 (en) Systems and Methods for Presenting Information Associated With a Three-Dimensional Location on a Two-Dimensional Display
US8527348B2 (en) Short-range communication enabled location service
US20160093000A1 (en) Novel cloud-based art inventory management system, incorporating techniques, methods and devices
US20170337619A1 (en) Systems, methods, servers, and clients for inventory exchange
Rashid et al. Bringing online shopping experience to offline retail through augmented reality and RFID
US11205245B2 (en) Method of improving visual recognition of an item and item display system
WO2015195415A1 (fr) Systèmes et procédés pour afficher l'emplacement d'un produit dans un point de vente au détail
EP3832567A1 (fr) Système de gestion et procédé de gestion d'informations d'alcool
JP5244864B2 (ja) 商品識別装置、方法及びプログラム
US20190057430A1 (en) Method and system for clustering products in an electronic commerce environment
WO2015195413A1 (fr) Systèmes et procédés permettant de présenter des informations associées à un emplacement tridimensionnel sur un affichage bidimensionnel
WO2015191130A1 (fr) Systèmes, procédés, serveurs et clients pour échange d'inventaire
US20120290611A1 (en) Short-range communication enabled location service
EP3327652A1 (fr) Sélection automatique des éléments pour l'affichage informatisé d'une annonce publicitaire graphique en utilisant un espace de vecteurs multidimensionnel généré par ordinateur
CN104346732A (zh) 一种可以快速在网上发布商品信息和所在位置的整套装置
US10473748B2 (en) Method and system for determining position accuracy of a modular shelving
US20190355039A1 (en) Methods of managing and querying product inventory data and inventory management server
WO2016197034A1 (fr) Systèmes et procédés permettant d'afficher l'emplacement d'un produit dans un point de vente au détail
Khan et al. Smart store: the convergence of IKEA department store, augmented reality and RFID technology

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15809489

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15809489

Country of ref document: EP

Kind code of ref document: A1