This article lists the system parameters and their values that are used to integrate the Order Manager with your Miva Merchant shopping cart.
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 the Order Manager will use the custom field's value as the SKU.
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. This parameter was introduced in Version 5.8 .
MivaDecryptionKey - Enter the Decryption Key used on your Miva Site [Optional]. This is only required if you use Merchant 4.14 or higher and use Payment Encryption on the website. If you do not enter this value here, you will be prompted to enter it at the time you download orders. If you leave this value blank at the time of download, you WILL NOT receive your payment data for the orders. You will receive **SECURED** instead of the field values.
MivaMaxOrderDownload - Maximum number of orders to download at a time (default=100). Set this value to a lower number should you experience timeout issues with the download.
MivaSyncBackOrders - 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 the Order Manager send an inventory synch notification at import to account for backorders which effectively returns Miva's QOH to zero. This parameter was introduced in Version 5.602.
MivaUseCustomCustomerFields - Set to true to include custom customer fields in the product import. This parameter is only for use with Miva 5.
MivaUseCustomProductFields - Set to true to include custom product fields in the product import. This parameter is only for use with Miva 5.
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 - Set to true to replace a checkbox's value (yes/no) with the name of the checkbox (attribute). This is set to False by default and is not typically used unless directed to do so by Stone Edge Technical Support.
UseMivaEncryption - If you use Miva Merchant's new Data Encryption feature to encrypt payment data on your site, set this parameter to True. You will also need to enter your Encryption key into the MivaDecryptionKey parameter (optional) or enter it at the time of download (you'll be prompted for the key if it was not saved in the parameter).
ModStop Modules
UseModStopInventoryTrk - Set to True to have Order Manager 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 Order Manager to build unique SKUs based on the product options.
UseModStopAgentTrk - Set to True to have Order Manager use ModStop's AgentTrk module
UseModStopCouponTrk - Set to True to have Order Manager look for coupons generated by ModStop's CouponTrk module
UseModStopDiscountTrk - Set to True to have Order Manager look for discounts generated by ModStop's DiscountTrk module
UseModStopGiftCertTrk - Set to True to have Order Manager process Gift Certificates redeemed from ModStop's GiftCertTrk module. Gift Certificates will be processed as a payment method
UseModStopMemberTrk - Set to True to have Order Manager look for member points redeemed from ModStop's MemberTrk module. Redeemed points will be processed as a payment method.
Sebenza Studios Additional Checkout Data Module
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.
DestForAddendField1 through DestForAddendField10 - 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)
Sebenza Ultimate Order Status Module
UseSebenzaUltimateOrderStatus - Set this value to true if your store uses the Ultimate Order Status Module from Sebenza Studios. Order Manager will notify the Miva Site when status events occur. Requires Miva Export Module Version 3.142 or higher.
Setup Inventory Tracking at the Attribute Level
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 Order Manager and Miva Merchant.
UseModStopInventoryTrk - Set to True to have Order Manager 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 Order Manager to build unique SKUs based on the product options.
Viking Coders Modules
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.
MultiStoreAttributeInventory - 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. Set to False by Default.
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 Order Manager and Miva Merchant.
UseVikingCodersOrderStatusMgr - Set this value to true if your store uses the Order Status Module from Viking Coders. Order Manager will notify the Miva Site when status events occur.
Importing Custom Order Checkout Fields from Miva Merchant
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.
DestForAddendField1 through DestForAddendField10 - 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)
Updated : 8/28/09