i think, the example with auto-parts is good to understand
only one single item - but i can use it on different pages.
maybe a screw in special format... normal way in bakery is one item per shop, attributes and item options possible. to spend some time, i can use the duplicate function, but then, i have a new item-id and if i sold in shop 1 all this items, shop 2 tells me, i have my complete stock there, but the stock is empty, sold in shop 1
my solution for the test - i add a category table with parent-cats and childs (if needed), a multi-choice category-selectbox for the item and the view / view_overview sort the items by cat-id. if i dont use categories, it works like the traditional bakery
advantage (in theory) : i have every item only one time in the backend and the stock administration works globale for this shop section
the other point: i'm not happy with the actual solution "one settings for all the shops" - in this project, i've at the moment 14 shops, but only one setting. Not possible, to build a shop with different settings, maybe delivery in special countrys, special payment-methods etc - from my view: good to have a global general setting, but it must be possible, to save here own settings for every shop, if i want
i addd there also the data proctection handling (on/off, page select like the global wb-options) and a link selectbox for required pages for informations about delivery time & cost
P.S.: what i need is a solution for absolute beginners in WB, not possible, to use own scripts, Droplet or something like this. the project owner has no experience with code. he sold on this page some very rare items for special collections. if he sold one of this item in this time and the same, duplicated item in the next five minutes, then there is trouble, some call it fraud then, because, he has only one of this item, but like to display it in more than one categories