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/08/10 05:53] – [Merging a store] Mark Glover | other_stuff:virtual_stores [2026/01/05 09:59] (current) – [Preferences tab] Gary Willetts | ||
|---|---|---|---|
| Line 158: | Line 158: | ||
| |<100% 40%>| | |<100% 40%>| | ||
| + | ^ Preference | ||
| ^ Sort available batches by VVM status rather than Expiry | When issuing stock, this will sort the list of available batches by vaccine status first, then by expiry date rather than by expiry date first (e.g. [[issuing_goods: | ^ Sort available batches by VVM status rather than Expiry | When issuing stock, this will sort the list of available batches by vaccine status first, then by expiry date rather than by expiry date first (e.g. [[issuing_goods: | ||
| ^ Patients created in other stores not visible in this store| If this is checked, patients that are created in other stores across all sites will not be visible in this store. If it is **off**, all patients from all stores from all sites will be visible to this store. It is set to true by default when a store is created. **USE CAUTION:** Turning this **OFF** for many stores does not scale well and can overload the sync system. See the [[dispensing: | ^ Patients created in other stores not visible in this store| If this is checked, patients that are created in other stores across all sites will not be visible in this store. If it is **off**, all patients from all stores from all sites will be visible to this store. It is set to true by default when a store is created. **USE CAUTION:** Turning this **OFF** for many stores does not scale well and can overload the sync system. See the [[dispensing: | ||
| Line 179: | Line 180: | ||
| ^ Show item unit column when issuing| If checked, when goods are issued on a customer invoice or prescription, | ^ Show item unit column when issuing| If checked, when goods are issued on a customer invoice or prescription, | ||
| ^ Log transaction edit | | | ^ Log transaction edit | | | ||
| - | ^ Set pack to one for all visible items in this store| | | + | ^ Set pack to one for all visible items in this store| |
| ^ Use remote authorisation for response requisitions | Turns on remote authorisation for response requisitions. See [[other_stuff: | ^ Use remote authorisation for response requisitions | Turns on remote authorisation for response requisitions. See [[other_stuff: | ||
| ^ Include requisitions from this store in suppliers' | ^ Include requisitions from this store in suppliers' | ||
| Line 205: | Line 206: | ||
| ^ Pickface replenishments must be authorised | If checked, pickface replenishments in this store must be authorised by a user who has permission to authorise them before they can be finalised. See the [[items: | ^ Pickface replenishments must be authorised | If checked, pickface replenishments in this store must be authorised by a user who has permission to authorise them before they can be finalised. See the [[items: | ||
| ^ Able to specify VVM status when receiving items | If checked then a new **VVM status** field will be available on a supplier invoice for the user to select the current VVM status of the batch when it is received on a supplier invoice or inventory adjustment. See the [[receiving_goods: | ^ Able to specify VVM status when receiving items | If checked then a new **VVM status** field will be available on a supplier invoice for the user to select the current VVM status of the batch when it is received on a supplier invoice or inventory adjustment. See the [[receiving_goods: | ||
| + | ^ Finalise stock transfer supplier invoice automatically | If this is checked, supplier invoices that are created in **this store** as the receiving side of a stock transfer are automatically received into stock and finalised. This is set in the **receiving** store. Only users who have the //Edit store details// permission set can set this preference (see the [[admin: | ||
| === Notification preferences === | === Notification preferences === | ||
| These are used by the notification/ | These are used by the notification/ | ||
| Line 210: | Line 212: | ||
| == 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 248: | Line 250: | ||
| How you set this preference is determined by how separate your goods receiving and finance sections are. If they are not in the same building, you might want to use the " | How you set this preference is determined by how separate your goods receiving and finance sections are. If they are not in the same building, you might want to use the " | ||
| - | === For stock transfers, the supplier invoice in the receiving store should be...=== | + | table at the to=== For stock transfers, the supplier invoice in the receiving store should be...=== |
| <WRAP center round important 60%> | <WRAP center round important 60%> | ||
| This option applies to all stores that this store transfers stock **to**. | This option applies to all stores that this store transfers stock **to**. | ||
| </ | </ | ||
| - | This option is used to determine whether stock transferred from one store to another is received to a destination store and automatically introduced to stock or not. The **On hold** option prevents stock from being introduced, while the **Finalised** option automatically makes the stock available for use in the destination store - //**without the receiving store having the opportunity to amend the Goods Receipt**// | + | This option is used to determine whether stock transferred from this store (the sender) |
| * Choose **Finalised** if there is no need to check / alter the quantity received compared to what was sent. | * Choose **Finalised** if there is no need to check / alter the quantity received compared to what was sent. | ||
| * Choose **On hold** if the store is being used by mSupply mobile, and the goods receipt needs to be confirmed before receiving. | * Choose **On hold** if the store is being used by mSupply mobile, and the goods receipt needs to be confirmed before receiving. | ||
| + | |||
| + | This preference is set in the **sending** store. There is another preference that can be set in the **recipient** store that will do the same thing but from the recipient' | ||
| === Location code pattern === | === Location code pattern === | ||
| Line 427: | Line 431: | ||
| 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. | 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. | ||
| </ | </ | ||
| + | |||
| + | <WRAP center round info 60%> | ||
| + | In order to merge stores, both of them need to be: | ||
| + | |||
| + | - Active on the Central server | ||
| + | - Not disabled (Special > Show stores) | ||
| + | |||
| + | It is OK if one or both of the stores are: | ||
| + | * Not visible to each other | ||
| + | * Not visible to the store that the user is logged in to when carrying out the merge | ||
| + | * On Hold (Customer > Show Customer) | ||
| + | </ | ||
| + | |||
| Line 436: | Line 453: | ||
| * The ' | * The ' | ||
| - | * The recommended :-D method: | + | * The recommended :-D method: |
| <WRAP center round alert 90%> | <WRAP center round alert 90%> | ||
| Line 475: | Line 492: | ||
| - Is visible to the customer that is to be converted to a store | - Is visible to the customer that is to be converted to a store | ||
| - Has similar //user and group permissions// | - Has similar //user and group permissions// | ||
| - | - **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 customer into a store - see warning below! | + | - **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 customer into a store - see warning below! |
| + | Step 5 below will be easier and more reliable if you copy the name into the clipboard: | ||
| + | - Click in the Name field | ||
| + | - Select all (Ctrl+a) | ||
| + | - Copy (Ctrl+c) | ||
| + | </ | ||
| - **Special > Show stores... > New Store** | - **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 | ||