Multi-tenancy e-commerce setup and pricing

Taun

5 months ago

10

• 

  noheadphones

  5 months ago

  1. that seems like the case to me tbh...basically you can assign your own domain to your payload instance

  
  
  

  2. you want to have a user collection for your tenants that they can login with and you attach all the other information to their collection there..in your frontend create an onboarding process where you gather all the data you need so you can spin up a stripe account for them...look into

  https://stripe.com/en-gb-th/connect
  
  

  i assume you're using stripe but the same principle would apply to other payment providers

• 

  Taun

  5 months ago

  Thanks @noheadphones .

  
  
  

  This is a reply to a previous thread: "In my mind, you would configure each user to have a relationship to a business domain, then use access control that references this."

  
  
  

  Another response:

  
  

  "You can achieve multi-tenancy in Payload using role-based access control. There are many topics around this, a quick search using those keywords should get you pretty far. Essentially, you'd have an organizations or similar collection for each of your clients. Then, every piece of content is assigned to an organization using a basic relationship field. This way each time a request is made for content you check the content ownership and control access based on whether the user is a pat of that organization. Here are the docs around access control:

  https://payloadcms.com/docs/access-control/overview

  . In your case though, you may want to take this a step further so that your access control also checks domain origins off the request.

  
  

  As of today the "pro" plan only supports up to three custom domains, though. But you'll still be able to achieve your multi-tenancy setup just the same with the only exception being that the API url won't be unique across each client."

  
  
  

  What does it mean that the API URL won't be unique across each client and what are the limitations in the case I mentioned?

• 

  noheadphones

  5 months ago

  i can reply in full later

  
  
  

  but to answer your last question, it just means that with payload cloud type of hosting you will need to point all frontends to the same API endpoint...so you cant have

  api.CLIENT.domain.com

  you'll have

  api.domain.com

  if you want and then

  CLIENT.domain.com

  and

  CLIENT2.domain.com

  can both talk to the same API and you handle your permission logic there

  
  

  
  

  this is how i understand it

• 

  Taun

  5 months ago

  I'm too much of a noob to fully understand what you're referring to, though I assume this is refering to the case where each client has a unique custom domain and not myecommerceplatform.com/tenant1 , myecommerceplatform.com/tenant2 . For this case I'd like the platform to host their vendor profiles like that, and not tenant1.myecommerceplatform.com as I assume that will ramp up costs and setup complexity as that falls into creating a 'custom domain' per tenant territory?

• 

  noheadphones

  5 months ago

  Im back, yes you're right

  
  

  
  

  have you built an information architecture diagram for this?

• 

  Taun

  5 months ago

  Thanks Paul. Not yet, at this stage I'm doing a profit analysis. I'll make diagrams later, thanks for the tip. Any software you recommend for that?

• 

  noheadphones

  5 months ago

  Miro/figjam work fine for this...it just helps a lot with planning and feasibility if you have a stronger idea of what you're building and how it's all gonna work together

  
  

  
  

  from there I always find it much easier to estimate the work and anticipate complexities