14 lines
1.8 KiB
JSON
14 lines
1.8 KiB
JSON
{
|
||
"HubID": "2153",
|
||
"Date": "2/13/2023",
|
||
"HubTags": [
|
||
"External Platform Posts"
|
||
],
|
||
"Contacts": "",
|
||
"Companies": "Prada,Alo Yoga",
|
||
"File": "",
|
||
"Image": "",
|
||
"Summary": "A few recent market intelligence finds to note.",
|
||
"Notes": "<p>A few recent market intelligence finds to note.</p><p>Alo Yoga</p><p>The brand rolls out digital twins to accompany its premium ski collection.</p><p>This implementation does not appear to have a unique identifier on each apparel item, like an #nfc chip. Since this was a luxury collection sold direct-to-consumer, the company knows the buyers and is sending them emails to mint generic #nft tied to the product collection.</p><p>The learnings here for other #consumerbrands ?</p><p>* The implementation is making it seamless to mint an NFT by providing a wallet to the customer automatically and setting up integrations where it is easy to verify ownership via tokengating on the company’s website.</p><p>* This is the route consumer brands are going to avoid the current poor #ux of #web3 .</p><p>#prada</p><p>The brand offers NFTs retroactively to all Timecapsule customers. Timecapsules are released monthly as new physical product drops, which started June 2022.</p><p>Customers who bought Timecapsule pieces before they were attached to NFTs now have the chance to purchase an NFT this time around, to join the Prada Crypted community.</p><p>The learnings here for other consumer brands?</p><p>* The physical products have a unique serial number to identify them, so this makes those products web3 enabled because they can now be attached to an NFT. This is the perfect example for how to web3-enable existing #inventory without having to get technical with NFC chips, QR codes and other similar approaches.</p><p>#phygital</p>"
|
||
}
|