Hey everyone, I'm running an online furniture business and I've got a bunch of suppliers providing data in various formats. Cleaning this data and uploading products to different platforms has been a real manual grind. Lately, I've started learning about automation and SQL, and I'm considering building a relational database to make everything more efficient.
Currently, if I list products on eBay, the data requirements differ from what I need for Amazon, for instance. I've downloaded listing templates for desks across platforms like eBay, Amazon, Temu, Wayfair, and Shopify, which have over 330 fields combined.
My vision is to create a database with a core table for essential product info (think SKU, color, size, weight, material, etc.), alongside category-specific tables—like one for desks that would include desk shape, features, and type. Once I have full product info, I want to explore creating views for each platform to streamline uploads.
This feels like a huge undertaking, especially with over 50 categories and thousands of products! I've started using scripts for some initial data population but I'm wondering if this is the best approach. Is there software I should try, or is there a simpler method I might be missing? I tried some Zapier automation but it got pricey. I'm also running a local LLM with my scripts, but I'd love to hear other suggestions or software that might help as I'm still a beginner in database design. Thanks!
4 Answers
Honestly, have you thought about handling this with Excel? It sounds like you've got a few thousand rows, but really wide data. Excel lets you create one main sheet and separate ones for each platform with formulas. Data entry will be way simpler there than in SQL.
Plus, you can add validation rules to manage your entries. If Excel slows down later, that's when SQL might make sense, but starting with something manageable could save you a headache!
Ultimately, whether you hire someone or tackle it yourself, know that the design aspect will take time. It’s all doable, but maintaining clarity on how you want to use the data will really save you in the long run.
Definitely simplify those features based on what each platform requires. Does eBay even need "desk shape"? If you can use key-value pairs, it might help reduce complexity and improve reuse across tables.
Consider trying out C# for a simple CRUD application; it’s pretty beginner-friendly. If your code gets too complicated, that’s a sign your database is probably over-complicated as well. So, keep it straightforward, and don’t stress about optimizing right away.
Look into database normalization processes. If you want to set things up correctly, forming your tables in normal forms is key. It’s achievable with some effort, and since you seem to have a grasp of the basics, I’d say go for it without hiring a developer.
Just know that there are no magical software fixes for your specific needs—it's best done by you to truly reflect what your business requires. Like you mentioned, this is a big project, so take your time to get the design right, or else you might find yourself regretting decisions down the line.
Definitely worth trying Excel first! It’ll give you some flexibility and a better sense of what your data structure should be before jumping into a full database.