SEOM uses hundreds of system parameters to tailor the program to a merchant's way of doing business.
Each system parameter is associated with a parameter group, based on its function.
One way of viewing system parameters is to select a specific Parameter Group at the Set System Parameters screen. It is also possible to search for a parameter by entering a portion of its name.
While some parameters could logically belong to more than one parameter group, the program only assigns a parameter to a single group. Be sure to look for other related group names when researching the available parameters for a particular function.
To change a system parameter, go to the Main Menu>Settings>System Functions>Set System Parameters, or select System Parameters from the Quick Clicks on the Main Menu Accordion, provided it has not been deleted by the user.
For instructions, review the Knowledge Base topic, Set System Parameters.
Parameter Name |
Comments |
AddendumDestination |
Set this parameter to specify where the information from the Addendum module is stored. Options include the Order Instructions field, the Comments field or the custom fields. If Custom fields is selected you'll also need to set the DestForAddendField# parameters to state which custom field will receive the data returned in field # from the addendum module. If a destination is not set, the data will be ignored. |
CustomFieldCodeForSKU |
If you use Custom Product Fields on your Miva Store to store the product SKU, enter the "Code" of the custom field in this parameter and Stone Edge will use the custom field's value as the SKU |
DestForAddendField1 |
Select a custom field to store the data returned from field 1 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField10 |
Select a custom field to store the data returned from field 10 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField2 |
Select a custom field to store the data returned from field 2 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField3 |
Select a custom field to store the data returned from field 3 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField4 |
Select a custom field to store the data returned from field 4of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField5 |
Select a custom field to store the data returned from field 5 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField6 |
Select a custom field to store the data returned from field 6 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField7 |
Select a custom field to store the data returned from field 7 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField8 |
Select a custom field to store the data returned from field 8 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
DestForAddendField9 |
Select a custom field to store the data returned from field 9 of the additional checkout data module used (Addendum.mv or Sebenza Studios Additional Checkout Data) |
MivaAllowDeleteBatches |
Set to true to display a button on the Select Batch form at time of order import that will allow you to delete one or more batches from your Miva Store. Default=false |
MivaAllowNegativeQOH |
If True, the system will allow quantity on hand in Miva to go below zero. |
MivaMaxOrderDownload |
Enter the maximum number of orders included in a single download. Default number is set to 100. If you experience timeout errors on your server, you may want to decrease this value. |
MivaSynchBackorders |
If you synchronize quantity on hand with your Miva site and you allow purchases of out of stock items (pre-sell items) which causes Miva Inventory to track below zero, set this parameter to true to have Stone Edge send an inventory synch notification at import to account for backorders which effectively returns Miva's QOH to zero. |
MivaUseCustomCustomerFields |
Set to true to include custom customer fields in the product import. |
MivaUseCustomProductFields |
Set to true to include custom product fields in the product import. |
MultiStoreAttributeInventory |
False by Default - Set this parameter to True if you will be using Viking Coders Inventory Manager or ModStop's InventoryTrkPro on multiple websites. AFTER SETTING THIS TO TRUE YOU MUST REBUILD SUBSKUS to allow the system to properly calculate the identifiers needed for the inventory modules. |
UseAddendumModule |
Set this to True if you are using the Addendum.mv module with your store. This will allow you to specify the custom field destination of the field 2 through field 10 returned from the addendum.dat file. See the AddendumDestination parameter to set the location of the downloaded data to the Order Instructions field, Comments field or the custom order fields. |
UseCheckBoxNameInBuildSubSKU |
Custom Parameter for use with Miva Merchant stores - Should be False by Default. Contact Stone Edge Technologies regarding the use of this parameter prior to setting to True!!! |
UseModStopAgentTrk |
Set to True to have Stone Edge use ModStop's AgentTrk module |
UseModStopCouponTrk |
Set to True to have Stone Edge look for coupons generated by ModStop's CouponTrk module |
UseModStopDiscountTrk |
Set to True to have Stone Edge look for discounts generated by ModStop's DiscountTrk module |
UseModStopGiftCertTrk |
Set to True to have Stone Edge process Gift Certificates redeemed from ModStop's GiftCertTrk module. Gift Certificates will be processed as a payment method |
UseModStopInventoryTrk |
Set to True to have Stone Edge communicate with Mod Stop's InventoryTrkPro module. Real-time inventory tracking can be done using up to 4 attribute levels per item. Requires that you also use the BuildSubSKUs feature to allow Stone Edge to build unique SKUs based on the product options. |
UseModStopMemberTrk |
Set to True to have Stone Edge look for member points redeemed from ModStop's MemberTrk module. Redeemed points will be processed as a payment method. |
UseSebenzaAddlDataModule |
Set this to True if you are using the Sebenza Studios Additional Checkout Fields module. This will allow you to specify the custom field destination of the field 1 through field 10 returned from the Sebenza Module. See the AddendumDestination parameter to set the location of the downloaded data to the Order Instructions field, Comments field or the custom order fields. |
UseSebenzaUltimateOrderStatus |
Set this value to true if your store uses the Ultimate Order Status Module from Sebenza Studios. Stone Edge will notify the Miva Site when status events occur. |
UseVikingCoderCheckout |
Set this to True if you are using the Special Order Instructions module from Magic Metal (formerly referred to here as the Viking Coders Additional Checkout Fields module). This will allow you to specify the custom field destination of the field 1 through field 5 returned from the Module. See the AddendumDestination parameter to set the location of the downloaded data to the Order Instructions field, Comments field or the custom order fields. |
UseVikingCodersInventoryMgr |
Set this parameter to True if you use the Inventory Manager module from Michael Brock (Viking Coders: BROK_INVENTORY.mv or .mvc). This module allows you to communicate inventory levels at an attribute level between Stone Edge and Miva Merchant. |
UseVikingCodersOrderStatusMgr |
Set this value to true if your store uses the Order Status Module from Viking Coders. Stone Edge will notify the Miva Site when status events occur. |
Created: 1/22/15
Revised:
Published:04/13/16