Alright, so I am trying to persuade a client to switch to Craft Commerce for their bakery shop.
Thing is, their current setup is kinda messy, and I just cant figure out how to convert it properly to Craft.
Case: They have Cakes, Cakes comes in a multitude of sizes, with a lot of choices. Different types of cakes have different choices (Fill, jelly, nuts, colors, figures etc.)
All possible combinations of the choices results in a unique ID (EAN) for that cake, that the bakery can use in their system for production.
Thats ok, we can have product types and variants for all these. But here is the hard part: each bakery have their own set of choices, some bakeries dont have the same type of jelly, or the same colors for the toppings.
Each bakery choose what cakes they want to sell, and what kind of configurations they have.
When on their front page, you type inn your ZIP code and we use that to determine the closest bakery, based on that, we show that bakery's cakes, with their configurations.
Since there are about 10 bakeries, having a chocolate cake with custom variants per bakery will get really messy really fast, given how many cakes each bakery has. So I am trying to figure out how to separate each bakery and its product in the CP.
I toyed with the idea of creating one product type per bakery, and just having a generic "cake" model that can be built up however they like, but this seems very hard for both us and the client, they having to create the same options over and over, and us having to "magically" get all kinds of configurations from some kind of matrix field, creating choices based on this in the frontend, and sending those choices by mail when the order is complete.
Is there some kind of "hack" where I can have a separate product (database) tables per user group, or something like that? If bakery X logs on the CP, we show products from this table, if bakery Y, we show products form another table.
The rest of the site is going to be joint, about us, contact, articles etc are all the same across bakeries. So I would like to avoid having 10 licenses, 10 databases and 10 installs to cope with this.
Any other ideas are greatly appreciated, maybe I am looking at this the wrong way, but having 300 cakes, with 18 variants each is going to make it impossible for a specific bakery to maintain their cakes.