3 ms·
I'm doing that with a team of 8 people and I do not recommend it. You'll find a bunch of small details that are pretty hard to find at hindsight. On a general
by ranguna 5y ago
I'm doing that with a team of 8 people and I do not recommend it.
You'll find a bunch of small details that are pretty hard to find at hindsight. On a general overview you'll be like "it's just a cart, all you need to do is create it and CRUD items in it, easy" it's not.
You'll start to go in details about which database to use, backup scheme, encryption for PII, scalability for your initial user base, details of crud etc
When adding an item with a sku that already exists, do we want to sum it up to the existing one or add a separate entry?
What if the existing item is on a different state? Is that even possible, the cart itself should be at different state.
What about tracking refunds, taxes, inventory checks, etc etc
What about managing product details and linking them with your orders?
What about detecting fraudulent payments?
Scratch that, what about handling payments? Payment details payment request, payment authorisation, payment capture, payment refunds etc
What about invoices and transactional email for order confirmations?
And logging all that for legal and debugging reasons?
And you'll also need to keep track of your customer accounts, are you planning on building a CRM as well? Even if it's just mvp, you're going to fall into the another rabbit whole.
There are teams of smart people out there, way smarter than you and me, that have went to the trouble of building these systems, now you just need to use them.
Shopify, stripe, commercetools and a few more. My recommendation is to use them if your main objective is relatively quick turnaround.