Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
other_stuff:virtual_stores [2025/05/07 03:19] – [Address details] Gary Willetts | other_stuff:virtual_stores [2025/08/10 23:33] (current) – [Threshold for understock] Mark Glover | ||
---|---|---|---|
Line 58: | Line 58: | ||
As noted above, in a syncing system you must be logged into the central server to create a new store - it will be synced to any site where it is visible to any stores active on that site (which will also include the supplying store). When a store is created, it is made active on the central server by default - see [[synchronisation: | As noted above, in a syncing system you must be logged into the central server to create a new store - it will be synced to any site where it is visible to any stores active on that site (which will also include the supplying store). When a store is created, it is made active on the central server by default - see [[synchronisation: | ||
- | </ | ||
- | |||
- | <WRAP center round alert 90%> | ||
- | <wrap em>After creating the new store, you will not be able to immediately log in to it.</ | ||
</ | </ | ||
Line 121: | Line 117: | ||
* for controlling some customisation features. | * for controlling some customisation features. | ||
* for reporting to group stores together. | * for reporting to group stores together. | ||
- | * | + | |
This area shows the tags that the store currently has. To add a tag, simply click into the area and type the tag's name. When you have finished typing the tag's name then press the Tab or Space keys on the keyboard (not Enter or return, that will close the window!). You know when you have done it right because the tag will appear in its own little box with an ' | This area shows the tags that the store currently has. To add a tag, simply click into the area and type the tag's name. When you have finished typing the tag's name then press the Tab or Space keys on the keyboard (not Enter or return, that will close the window!). You know when you have done it right because the tag will appear in its own little box with an ' | ||
Line 134: | Line 131: | ||
* Set the [[other_stuff: | * Set the [[other_stuff: | ||
* Set the store' | * Set the store' | ||
- | * Set the [[other_stuff: | + | * Set the [[other_stuff: |
+ | For any system bigger than the most basic operation, you will likely want to use [[items: | ||
+ | </ | ||
* Setup any [[other_stuff: | * Setup any [[other_stuff: | ||
- | * Set the master lists used by the store (a convenient method for controlling item visibility). | ||
Line 211: | Line 210: | ||
== Threshold for overstock == | == Threshold for overstock == | ||
- | The minimum | + | The months of stock of an item for it to be considered as overstocked. |
- | This value should | + | Clearly, the Threshold for overstock must be more than the [[other_stuff:virtual_stores#threshold_for_understock|Threshold for understock]]. The default |
</ | </ | ||
== Threshold for understock == | == Threshold for understock == | ||
- | Also called <wrap em> | + | Also called <wrap em> |
- | This alert should only be triggered when your stock levels fall below your buffer stock levels. | + | This alert should only be triggered when your stock levels fall below your buffer stock levels. |
</ | </ | ||
Line 313: | Line 312: | ||
If you have lots of stores in your data file, managing item visibility can turn into a difficult task. Thankfully, mSupply has some helpful tools to make it simple! There are 2 ways to manage item visibility and you use one or the other, not both: | If you have lots of stores in your data file, managing item visibility can turn into a difficult task. Thankfully, mSupply has some helpful tools to make it simple! There are 2 ways to manage item visibility and you use one or the other, not both: | ||
- | - automatically using the Master lists tab or | + | - automatically using the Master lists tab (recommended!) |
- manually using the Visibility tab | - manually using the Visibility tab | ||
Line 322: | Line 321: | ||
If you have a lot of stores in mSupply, and especially in a syncing system, we recommend that you use master lists to control item visibility, because it means that the visibility of newly created items will be automatically handled correctly. The visibility of items in a store whose visibility is controlled by master lists is immediately updated if any changes are made to any of the master lists. For instance, if a new item is added to a master list controlling visibility then that new item is made visible in all stores that use the master list. And any items deleted from the master list are made invisible in any store using that list. | If you have a lot of stores in mSupply, and especially in a syncing system, we recommend that you use master lists to control item visibility, because it means that the visibility of newly created items will be automatically handled correctly. The visibility of items in a store whose visibility is controlled by master lists is immediately updated if any changes are made to any of the master lists. For instance, if a new item is added to a master list controlling visibility then that new item is made visible in all stores that use the master list. And any items deleted from the master list are made invisible in any store using that list. | ||
- | The first thing to do is to turn on the preference to make master lists control item visibility in stores. Do that in **File > Preferences...** on the //Item// tab - see [[preferences: | + | The first thing to do is to make sure that you have turned |
The next thing to do is to create the master list(s) that will control item visibility. See [[items: | The next thing to do is to create the master list(s) that will control item visibility. See [[items: | ||
Line 408: | Line 407: | ||
==== Deleting a store ==== | ==== Deleting a store ==== | ||
- | To delete a store, click on the //Delete// button in the View stores window. **Note:** deletion of a store is a serious thing to do and is only possible when that store contains zero stock and there have been no transactions recorded. mSupply will check and tell you that deletion is not possible if these criteria are not met. If you can't meet these criteria and you still want to stop people using the store then you can [[other_stuff: | + | To delete a store, click on the //Delete// button in the View stores window. **Note:** deletion of a store is a serious thing to do and is only possible when that store contains zero stock and there have been no transactions recorded. |
- | <WRAP center round alert 60%> | + | <WRAP center round important |
If the store is **Active** on another site, then this process will not delete the site. | If the store is **Active** on another site, then this process will not delete the site. | ||
</ | </ | ||
+ | |||
+ | ==== Merging stores ==== | ||
+ | |||
+ | Circumstances change, and you may find yourself in a position where you want to merge two stores. | ||
+ | |||
+ | <WRAP center round alert 60%> | ||
+ | Merging stores is not reversible. | ||
+ | </ | ||
+ | |||
+ | |||
+ | <WRAP center round important 60%> | ||
+ | The merge store feature has only recently been developed (2025). | ||
+ | |||
+ | Please email [[support@msupply.foundation]] so that the support team can test and see if you will encounter any issues, and then, in consultation with you, carry it out on your Central server for you. | ||
+ | </ | ||
+ | |||
+ | |||
Line 422: | Line 438: | ||
* The recommended :-D method: | * The recommended :-D method: | ||
- | <WRAP center round important | + | <WRAP center round alert 90%> |
**Whichever method is used, this is difficult to reverse. | **Whichever method is used, this is difficult to reverse. | ||
</ | </ | ||
Line 446: | Line 462: | ||
- | <WRAP center round alert 60%> | + | <WRAP center round info 60%> |
- | If the name is not visible to the store that you are logged in to, this method will not work! First make the name visible, then start this process... | + | This method will only work if you are logged in to a store that is visible to the customer. |
</ | </ | ||
+ | <WRAP center round important 60%> | ||
+ | * The new store will be made visible to all stores that the original customer was visible to. | ||
+ | * The new store will have the same User and group permissions as the store you are logged in to | ||
+ | * The only user who will be configured to be able to //login// to the new store is the user who created the store. | ||
+ | </ | ||
- | + | | |
- | | + | - Is visible to the customer that is to be converted to a store |
- | - **Customer > Show customers...** to find the customer that you want to convert into a store and copy the Name. This will ensure that you are converting the correct | + | - Has similar |
- | - **Special > Show stores... > New Store** | + | - **Customer > Show customers...** to find the customer that you want to convert into a store and copy the name. This will ensure that you are converting the correct |
+ | - **Special > Show stores... > New Store** | ||
- Click on the **Turn an existing customer into a store** checkbox | - Click on the **Turn an existing customer into a store** checkbox | ||
- | - Enter the existing customer name into the **Name** field. | + | - Enter the existing customer name into the **customer** field. |
+ | If you do not see the store code field getting populated, then the existing customer has not been recognised - try again. | ||
+ | </ | ||
- Populate the [[other_stuff: | - Populate the [[other_stuff: | ||
- Click **OK** | - Click **OK** |