In this Topic: Show
Miva Merchant Version 5.5 provides a limited ability for the user to perform Inventory Synchronization at the attribute level (real-time inventory tracking) without the need for a third-party add-on product. This feature is not suitable for all users, and requires the v3.518 export module, at a minimum. Please be sure to read and understand the information in this topic before implementing this feature.
Set the BuildSubSKUDelimiter parameter to the underscore character “_”. Currently Miva Merchant does not permit user defined delimiters in their Variant SKU (SubSKU) built by their automated system. Miva has stated that they will add a user definable delimiter in the near future at which time the delimiter specified at Miva would also need to be set in the BuildSubSKUDelimiter parameter in the Order Manager.
Set BuildSubSKUs to TRUE to have Stone Edge build SubSKUs at order import.
Set up the Parent SKU in Miva with the appropriate Attributes and Options. Keep in mind that the full value present in the Option’s Code field will be the value appended to the Parent SKU by Miva’s automated variant build system. As Miva does not support the Stone Edge parameters WebOptionCodeDelimiter or WebOptionProductDelimiter features, do not add additional delimiters to the Option’s Code Field in Miva. If you need to utilize these options in Stone Edge then you must use a third party inventory tracking system with Miva such as Viking Coders Inventory Manager.
Use Miva’s “Auto Generate” option under the Inventory Variants tab to build the SubSKUs. Select either Pricing option for the SubSKUs (calculated by parent/attribute or fixed at the variant). Miva will generate the appropriate SubSKUs using an “or” methodology which results in more SubSKUs than Stone Edge will generate. For example:
A Parent SKU with three sizes and three colors will generate nine SubSKU variations in Stone Edge, however, Miva Merchant will generate fifteen SubSKUs. The additional six SubSKUs represent three sizes with no color selection and three colors with no size selection – impossibilities in the variant world. Variants that do not represent actual products should be removed from the variant list and Miva’s Products list as Stone Edge will not support these types of variations.
Import products from Miva to Stone Edge using the Import Inventory feature found on the Shopping Cart Functions screen (Main Menu>Settings>System Functions>Shopping Carts>Additional Functions>Import & Update Data). The product import does not import the SubSKUs as part of the download, however, it does import any SubSKUs built in Miva that are no longer flagged as a variant – assuming they remain in Miva’s Products table (see step #3 above).
Use Stone Edge's Build SubSKUs option (Main Menu>Settings>Inventory Functions>Build Sub-SKUs) to create the SubSKUs in the its inventory. Pricing for the SubSKUs during the build is determined from the parent SKU and the option price modifier(s) defined at Miva. Once the SubSKUs are created, manual adjustments can be made to the SubSKU’s price. Keep in mind that Stone Edge cannot refresh SubSKU prices from Miva, so any price changes applied in Miva must be repeated in Stone Edge.
Once SubSKUs are built, return to the Cart Functions screen to import the product QOH from Miva using Get QOH from Miva.
Quantity on hand synchronization between Stone Edge and Miva is operational, provided the SubSKUs appearing in the Order Manager match up with those in Miva Merchant. To enable real-time inventory synchronization, set system parameter SynchQOH = TRUE, and edit the shopping cart definition and select Synchronize Inventory.
Stone Edge can handle kits defined in Miva Merchant, however, it is a tedious proposition. A kit is defined in Miva Merchant by first identifying the Kit SKU (Parent) and a set of attributes and options – similar to variants. Once the Variant SKUs (SubSKUs) are built, the user can assign a list of parts to each of the SubSKUs effectively defining a “kit”. The assigned parts can be regular products or variants but must not contain other kits as this concept is not supported in Stone Edge.
The Stone Edge product import from Miva does not support kits, so they are not automatically created in Stone Edge. Instead you can create kits manually after building SubSKUs in Stone Edge. Assign the parts list to each SubSKU that represents the kit part list for that variation.
At order import, Stone Edge receives the Kit SKU (Parent) and the selected options from Miva. The system builds the SubSKU then reviews the SubSKU to see if it represents a kit. If so, the system adds the parts list defined in Stone Edge’s inventory. Keep in mind that any changes to a kit’s part list at Miva must be duplicated in Stone Edge’s inventory.
NOTE: As Kits are virtual products, quantity on hand for the kit’s Variant SKU is not performed. QOH is adjusted only on the parts that make up the actual kit.
Created: 9/22/14