Being able to filter based on manufacturer specific data (such as vendor ID and product ID) will enable e.g. manufacturer.example.com to configure/select only its own Bluetooth devices and present them to users, instead of showing unrelated Bluetooth devices in the browser picker.
Today, developers can prompt users through a browser picker to select a nearby Bluetooth device that matches their advertised name and services. However it’s not possible for them to filter nearby Bluetooth devices based on advertised manufacturer specific data, used in advertising packets to add custom data (always starting with a Bluetooth company identifier). Being able to filter based on manufacturer specific data (such as vendor ID and product ID) will enable e.g. manufacturer.example.com to configure/select only its own Bluetooth devices and present them to users, instead of showing unrelated Bluetooth devices in the browser picker. The Web Bluetooth spec always had manufacturer data filter support but it wasn’t implemented due to the lack of developer need when it shipped. This is no longer the case. See the “Web / Framework developers” signal section.
Docs: https://web.dev/bluetooth/#manufacturer-data-filter
Samples: https://googlechrome.github.io/samples/web-bluetooth/manufacturer-data-filter.html
Explainers: https://github.com/WebBluetoothCG/web-bluetooth/blob/main/data-filters-explainer.md