Granted Claim 1 · Element F
Retailer-entered demographic specifications for preferred recipients
Not yet publicly established
Granted claim language
Verbatim · US12039568B2 · Claim 1send notifications to the one or more secondary user devices according to one or more specifications entered by the retailer regarding one or more demographics of the one or more consumers to which one or more notifications are preferred to be sent, wherein the one or more notifications are sent:
Claim requirement
Technical interpretation — not claim languageThe granted architecture introduces retailer-controlled criteria concerning the intended consumer recipients. The retailer, not only the system, specifies who should preferably receive a notification.
Publicly disclosed Woosmap functionality
The Woosmap Geofencing SDK documentation reviewed is directed to location events, assets, visits and Zones of Interest. Within that material, Woosmap does not publicly disclose a retailer-facing demographic or audience-segmentation configuration inside the Geofencing SDK itself. Retailer-side audience definition appears in the surrounding customer-engagement narrative rather than in the SDK reference. No source is asserted here beyond what that material supports.
Potential completion path
- 01Woosmap
- 02Location event
- 03Customer engagement / CRM
- 04Retailer segmentation
- 05Selected consumer communication
Public evidence
Woosmap (woosmap.com)
Woosmap Geofencing — commercial use case page
Commercial description of geofencing triggering events on device entry or exit of a monitored region; contextualisation of push notifications at the right time and in the right place; support for distance-based, time-based, ETA/isochrone and recurrent geofences; and retail, geomarketing and offer-targeting use cases including tailoring by where users live or work.
View original source ↗Woosmap (woosmap.com blog)
Click & Collect: why brands need it and how geofencing maximises the experience
Retail deployment narrative for ETA-based customer arrival detection, order-readiness workflows and curbside/click-and-collect notification sequences built on geofencing events.
View original source ↗Technical correspondence
Woosmap supplies the location-event layer consumed by broader marketing and engagement architectures. The demographic or audience parameters contemplated by this limitation would ordinarily be entered in that integrated layer rather than in the geofencing SDK.
Evidentiary status
Matters for further review
Specific retailer deployments should be investigated to determine whether retailer-entered demographic criteria govern the notifications triggered by Woosmap location events, and in which system those criteria are held.
Status
Not yet fully established from public Woosmap material. The evidence has not been shaped to fit the claim.