Centralizing Product Data Management via Salsify PIM

https://www.figma.com/board/FwlOKQio0bWrif0POZRADo/product-attribution-and-feeds?node-id=0-1&p=f&t=M9uqySVIaP6T6aNE-0

The current product data ecosystem is fragmented across PLM, PIM, Salsify, and manual documents such as the MPK, and the Shoe Finder document, maybe more.. This fragmentation leads to inefficiencies, redundant manual work, and inconsistent data flow. The proposal aims to cut out the middleman work and streamline information inputs, by making Salsify the central hub for all product information, copy information, etc. which in turn feeds to our Website (PLPs, PDPs), Dynamic Yield Content, Shoe Finder Tool, Chatbots, etc.

The proposed solution is to make Salsify the central PIM hub for all product information aka attributes/properties, copy, etc. and eliminate manual documents like MPK, Shoe Finder Doc, copy docs, etc.

This includes:

• Collaborating to ensure Salsify includes all SFCC attributes/properties (currently most attributes/properties are in Salsify but there are additional ones in SFCC that need to be added)

  • This includes identifying missing fields in the Shoe Finder document and integrating them into Salsify and SFCC to retire the manual docs

• Auditing syndication/replication timings (including Feedonomics)

• Ensure Salsify is compatible with future initiatives like HOKA 3.0 and Headless (if we go Headless, we are missing properties in Salsify, there are additional SFCC attributes that are visible and currently used onsite)

This initiative will require cross-functional support from:

• Global Technical Architects

• SFCC Product Owners

• Salsify Technical Support

• Cartful Team

• Product Teams and Copy Teams (to adopt new processes)

• Regional eCommerce Teams (for testing and feedback)

Note: this proposal is mandatory to win .NEXT initiatives (i.e. with HOKA 3.0, any Global Code Base design relies on attribution from the PIM)