Why You Shouldn't Use Spreadsheets As A Product Database

Поделиться
HTML-код
  • Опубликовано: 15 июл 2024
  • In this video, we go over the seven most common problems faced when building a database in spreadsheets. We also show how to overcome these problems with PIM software -an alternative option to spreadsheets for managing your product information.
    🚀 Get started with Product Information Management software for free! 👉🏼 www.plytix.com/lp/pim-softwar...
    📚 Learn how to merge multiple spreadsheets into one 👉🏼 www.plytix.com/blog/merge-pro...
    🎥 Learn how to have complete product listings with Plytix's completeness attributes 👉🏼 • How to Merge Spreadshe...
    00:00 Introduction: 7 typical spreadsheet problems
    00:23 Problems adding product information to your database
    01:01 Problems controlling access/permission levels in spreadsheets
    02:07 Spreadsheet collaboration issues
    02:59 Dealing with large numbers of SKUs in spreadsheets
    04:06 Problems managing product images in spreadsheets
    05:12 Problems checking data completeness in spreadsheets
    06:30 Problems sharing data with other software and platforms
    07:59 Spreadsheet alternatives

Комментарии • 3

  • @jorxcore
    @jorxcore 4 месяца назад

    Very relevant, glad for the yt recommendation.

  • @SolAngelucci
    @SolAngelucci 4 месяца назад

    more sheets more problems, couldn't agree more!

  • @bryang1
    @bryang1 4 месяца назад

    I dont disagree with your position fundamentally but many of the arguments you use to make your point arent completely true. For example, when saying that you would need mutiple sheets or workbooks of data to store mutiple versions of your data, implying that you would have to maintain all these sheets / workbooks separately isn't exactly true. If you are using excel you could very easily create a single table which is the "single source of truth" and use power query to read from that table data, transform it to the required output necessary for whatever system it needs to go to and then output it to a different sheet or workbook. This implementation would only require a single button click to refresh all the "other" sheets/workbooks and therefore you only have to maintain the original Table of data. Another example you use is when you said spreadsheets cannot export data in a different format that is required for other systems (ie shopify, amazon, etc..), which is also not completely true. If using google sheets you could, similarly to the power query implementation above, have a single table in your workbook with all your products and use google scripts to not only format the data but also send it to a systems REST api, using urlFetchApp for example.