Miva Inventory Variants, SKU's, and Stone Edge Order Manager

[Krsullivan]

Anyone using MIVA with inventory variants and Stone Edge Order Manager? If so, how are you handling SKU building on import into Order Manager without a Web Import Delimiter? Since MIVA has not way (at least that I can find) to strip out a web delimiterthat Order Manager would like to see, so that a Clean SKUs can be build for import. IE: SP24-NV-L-RG instead of SP24~-NV~-L~-RG~. In order manager, I have tried the AddSKUIfNoDelimeterUse Parameter, which allows the SKU to be build without a web delimiter, the problem is that besides selling clothes, we offer embroidery services (IE Embroidering company name or emblems on garments) anyway, that parameter tries to make a SKU from out embroidery options, which is unique to each order because is personal. And the Strip SKU delimiter setting in order manager does not seem to work, or at least the way we thought it worked.

I should note, one reason we wanted to clean up our SKU at the source was for EDI as well as Bill Weilands Template Feeds for Google and Amazon.

Anyway, Thank you for your time,

Kevin

www.automotiveworkwear.com
www.sullivanuniforms.com

[Rick Wilson]

Re: Miva Inventory Variants, SKU's, and Stone Edge Order Manager

You can set that Delimiter on PR8 and higher.

[Krsullivan]

Re: Miva Inventory Variants, SKU's, and Stone Edge Order Manager

Hey Rick,

I guess I didn't explain it very well. If I am under standing you correctly. We are aware that during auto generation we can set a delimiter of our choice. The issue is that order manager uses a delimiter to build SKU on import, we use the "~" as the import delimiter in order manager. In Miva we used the "-" as the delimiter. So

The parent is SP24 and we used just NV for the option, before generation. We get SP24-NV, which is great. The problem is during import of the order into order manager we get only the SP24, if we use the "-" as the web option delimiter in order manager we still only get SP24, order manager strips out everything to the right of the "-".

If we use, the "~" in Miva and enter the options as NV~ or L~, Miva products skus that look like SP24~-NV~, but ordermanager will import it as SP24-NV. I was stating that Miva does not use a delimiter to strip out unwanted content.

Now, order manager does have a parameter to make a SKU out of the parent and its options (with out a delimiter) This will build the SKU in order manager correctly, for about 99% of our products such as the SP24-NV-L. I am just having trouble with those 1%. It produces SKU beyond the 255 character limit, that order manager has.

I don't understand if Miva generated a unique SKU why order manager will not import the generated SKU, but instead import only the parent SKU. I realize this is a order manager problem, and not miva. I was just asking if anyone else using order manager had a solution, The techs at order manager don't have a solution. I thought about the problem, and figured out a work around, within order manager, to that will build a SKU that looks like E-Direct-Embroidery-1-1-1-1-1-1 . The "1"s are actually an abbreviation of a character string of present text values.

Anyway, that's my story.

Thanks

Kevin

www.automotiveworkwear.com
www.sullivanuniforms.com

[Rick Wilson]

Re: Miva Inventory Variants, SKU's, and Stone Edge Order Manager

Got it.

[2CDev]

Re: Miva Inventory Variants, SKU's, and Stone Edge Order Manager

Rick, any idea if Kevin means attribute options or inventory variants? I have to assume he means attribute option codes, because variants have their own whole product code which added to the main product code would result in a wrong SKU for my client.

Kevin?

Thanks all.

[Krsullivan]

Re: Miva Inventory Variants, SKU's, and Stone Edge Order Manager

Hello Holly, At that time we were NOT using inventory variants rather attribute options, so Yes I was talking about the attribute option codes. We were using the Build A SKU feature within stone edge order manger (now monsoon stoneedge) to create variants within order manager, which worked fine, but we had difficulty when using Bill Weiland's template feed to create a feed for Google. The module was fine, we just could not make the SKU match what google wanted. At that time, I didn't fully understand how or what Google wanted, and later learned how we could cheat a bit so not have to upload 50K SKU's. Since then, We have switched over to Miva inventory variants, which was much easier in the long run for us, but did create duplicate order manager SKU's, since many variants were slightly different. Did this answer you question. Kevin, www.automotiveworkwear.com

[2CDev]

Re: Miva Inventory Variants, SKU's, and Stone Edge Order Manager

Thank you Kevin, immense help!! Just what we needed to know. Appreciate it.