Build your own marketplace from scratch using Medusa
ShippingOption
to make them relevant to a store. In fact, each vendor must be able to input its own shipping options, giving the customer choices for each vendors.
We’ll also extend the behavior of ShippingProfile
to link them to a store too, because the shopping cart currently allows for multiple shipping methods, but the current implementation only allows for one per shipping profile, so we’ll create one by default for each store, allowing for multiple shipping methods for a single cart.
1.2x.x
).ShippingOption
to be linked to a Store
ManyToOne
relationship above also means updating the Store
model:
yarn build
command and then run the npx medusa migrations run
command, as for our previous migrations to make the changes in your database :
ShippingOption
entity has been fully extended, we also need to extend the ShippingProfile
entity, almost like copying and pasting what we’ve done above.
In the same way :
shippingProfiles
property :
ShippingProfile
migration to apply our changes to the database :
ShippingProfileService
and ShippingOptionService
, and how/what we can override some of their functions. We’ll use the same reasoning as the ProductService
, where we made sure to fetch only the products associated with a Store or tie a new product to a specific store.