3. Create the Store

After the sync sites have been set up, there are three approaches to creating and configuring the store that will be operated on that site.

• This can be done 'manually' as described in the first method below. This method is suitable if you are creating only a handful of stores.
• If you are creating a larger number of stores, then it is more appropriate to use one or both of the two footrunner code methods. As of 2019-10-24 there are two pieces of footrunner code that can expedite this process - see:
• Creating data files for multiple new remote sites. They can not be used together for the same store, but it may be appropriate to use
  • store_create_from_name for creation of one store, and then use
  • sync_clone_sync_site to create subsequent stores.

1. On mSupply desktop go to Special > Stores > New Store
2. Enter the Store Code and the Store Name

   • The Store Code can not include spaces
   • The Store Name needs to be something that users will recognise.
     Mobile Store 1 is not likely to be a good name to use.
3. Configure items visibility for the store
4. Configure synchronisation settings
5. Configure store visibility to other stores

This method is only useful if you already have a customer that you want to convert to a store.
We must first clone the existing customer then merge the new store with the existing customer.

1. The mSupply Support Team will use the footrunner code ''store_create_from_name'' to clone the original store. We will need to provide:
   1. Name ID (not name Code ) to create the store for (must not be blank or already a store)
   2. Store mode for new store (one of store, dispensary or report). Almost always, this should be store
   3. Sync ID for site on which the new store will be Active (optional; if left blank, will default to the current site ID)
2. Configure items visibility for the store
3. Configure synchronisation settings
4. Configure store visibility to other stores

Using the mSupply Desktop User Guide Merge the new store name with the existing customer name. There is some footrunner code that can facilitate this for multiple sites.

NOTE: Before merging any unfinalised Customer Invoices from supplying stores to these existing customers need to be finalised first. On a system with supplying stores on multiple sync sites, this can take a long time. Start early, and if possible, ask the supplying stores to refrain from creating new Customer Invoices until the merging is done…

If you try to do the merge before finalising unfinalised customer invoices, you will get an error message, and as that message indicates, the merge will not proceed

First manually create and appropriately configure a single store.

Make sure the relevant sync sites have been created and then, for EACH store:

1. The mSupply Support Team will use the footrunner code sync_clone_sync_site to clone the original store. We will need:
   1. Sync ID for source sync site
      
      
   2. Sync ID for clone sync site
      
      
   3. Sync version (v1 for desktop, v3 for mobile)
      
      
   4. Decision on whether the cloned store will have 'group' store visibility (visible to all other stores with the same supplying store) or not
      
      
   5. Decision on whether to also clone locations, transactions, stock, requisitions. (almost always NO!)
      
      
   6. new store code and name for each cloned store
      
      
   7. new user name and password for the each cloned store's default user
      
      
2. If there are actually existing customers for each of these stores, you will then need to merge the existing customer name with the new store
   
   
3. The store will have the same item visibility configuration as the store that has been cloned. Review, and if necessary, Configure items visibility for the store
   
   
4. The store will have the correct 'basic' sync settings. Review, and if necessary, configure synchronisation settings
   
   
5. The store will have the correct 'basic' store visiblity settings, including, if you have selected it, 'group' store visibility. Review, and if necessary, configure store visibility to other stores