We are building a storefront for consumers that like to shop for fresh fruit and vegetables at farmers markets. We have build a basic react store with signup functionality so far. Our strategy is to onboard customers with an app that allows them to buy produce and collect it from these farmers markets. Having consumed related forum posts, I still have some questions about the best architecture. The overarching question is, “should we use a single or multistore approach?”. Clearly marketplaces are single stores with vendor IDs and carts
First, some answers to decision tree questions posted elsewhere by @ajsturrock :
- Can an end user add products from multiple vendors (farmers) into the same cart together? No
- Are you holding and fulfilling stock from physical locations? Stock is sold and collected from farmer’s markets.
- Are you shipping orders to the farmer’s markets from a single distribution point? No. Many farmers (stores) will bring produce.
I want to check if this is the best solution, and thank the community and Moltin in advance for the support:
- A multi-store setup. Sync product data across stores. Stock levels managed for each store inside each individual store.
- Lookup table used to switch between stores. User should be able to look at multiple vendors products.
- Each store would use flows to integrate the physical locations of all farmer’s markets (collection points) that customers can select (or based on the closest physical location to the customers location if you have that data to hand).
- Create a custom order status attribute so that when stock is added to a given farmer’s market Twilio or Sendgrid notify customers in the area
Alternatively, we could treat each farmer’s market as a marketplace with multiple vendors in one Moltin store.