Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

[Jim McCormick]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Fail to apply framework: UI module mismatch Error:

When I try to apply framework css_fw, I keep getting UI module mismatch error.

What would cause this error?

Thanks.

You can't apply an MMUI framework to a CSSUI store.

[Siamese-Dream.Com]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Not to go too off topic, but...

From what we can tell, close to 95% of our customers who use Real Time Gateways, Auth and Capture at the same time, so capturing after the fact is sort of rare.

Isn't that (technically) against the policy of the credit card companies? I thought we merchants are prohibited from settling a transaction BEFORE it ships out (and that we only have three days from the original authorization to send out the order and capture funds, or we are supposed to go through the whole authorization process over again).

[d_host]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Mark - I'm with you on that one. I think it's the other way around - 95% merchants do (or should be doing) AUTH ONLY and capture later when they process and ship orders out. The AUTH&CAPTURE at the same time is only good for soft goods delivery, where the goods are delivered immediately. Shipping physical goods means you should be only doing AUTH at the time the order is placed, and CAPTURE when you are ready to ship, to comply with credit card regulations.

[Siamese-Dream.Com]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Thank you for your confirmation, Remik.

However, I wonder if Mr. Wilson might be right - that 95% of the merchants are doing it WRONG?!?!?!

[p4k]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

The new version does allow for it, but following the old process. Whether or not we build it into the new Manage Orders screen depends on demand and other things.

From what we can tell, close to 95% of our customers who use Real Time Gateways, Auth and Capture at the same time, so capturing after the fact is sort of rare.

With that said, I certainly see why that would be a logical addition and we'll explore it.

I agree with the previous posts on this - the standard should be auth only and capture later. We have always used this method and only perform the capture when the shipment is sent.

[Jim McCormick]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

I think it's the other way around - 95% merchants do (or should be doing) AUTH ONLY and capture later when they process and ship orders out.

The key word is SHOULD. In my experience Rick is right. Most merchants capture at the time of sale.

[Rick Wilson]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Yeah, my statement was not a suggested behavior, but a comment on what really happens.

Also as long as you ship the same day, Authing and Capturing are acceptable at time of sale (or at least it's an accepted de facto practice).

[habermas]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

We have the Customer Account Management module installed and had previously been using that to keep customers apprised regarding order status, tracking numbers, etc. Now that we have completed the Wombat update, and seeing that it includes similar functions, should we remove the Customer Account Management module? If we do so, will the link to customer Order History that is provided as part of the Wombat update then start appearing on the customer Account page (right now, it is not.)?

[Siamese-Dream.Com]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Yeah, my statement was not a suggested behavior, but a comment on what really happens.

Yeah, it just seems kind of funny that there is all this work being done to be "in compliance," and it gets kind of negated by people cutting corners on their processing practices.

[Ksaluzzi]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

This may be a bug in Wombat or user error, but I wanted to report it in case it is a bug.

I've followed the instructions in the "For Hiding Out Of Stock Master Products with Multiple Variations video" http://www.youtube.com/watch?v=A4H8PA2Xack , on this video and when I configure a product w/ variants, the price on the product page is doubled (i.e. product price + inventory variant price). The "Price/Cost/Weight" for the each variant is set to "Sum of Parts"

When I no longer synchronize the inventory with variants, the price goes back to the variant price.

Is this working as designed? If not, what is the correct way to set the pricing when synching inventory with variants?

Thanks in advance.

[Rick Wilson]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

That's because you have the master product price set as well, you need to set the Master Product price to $0

[Ksaluzzi]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Thanks for the reply, Rick.

When I set the price of the master product to $0.00 (in the edit product page), the price is $0.00 on the category page and $0.00 on the search page, but is the correct price on the product page.

[jankal7003]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Please supply a link to complete explanations for each of the PA-DSS compliance issues.

[Rick Wilson]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

That will be posted as part of our PIG (Product Implementation Guide) once it's approved by our PA-DSS auditor. We expect that plus our Report on Compliance to be posted around June 1.

[Ksaluzzi]

Re: Miva Merchant 5.5 PR7 (Wombat) Bugs/Issues

Hi Rick,

Here's an update to my post # 55 regarding synching inventory products with variants.

In this example, the product with variant price should be $1.00. Please keep in mind, the scenario below occurs ONLY when I synchronize the inventory with master product and variants.

1) If I set the price of the master product to $1.00 and the variant to $1.00, the total on the product page will be $2.00, yet the price on the category & search page page is $1.00. Also, the product weight is doubled at checkout.

2) If I set the price of the master product to $0.00 and the variant price to $1.00, the total on the product page is $1.00, yet the price on the category & search page is $0.00

3) If I set the price of the master product to $1.00 and the variant price to $0.00, the price on the product, category and search page is $1.00.

Is the third scenario supposed to be the correct way to handle pricing when synching the inventory with product variants?

Is this a bug or working as designed?

Thanks for your help.

Ken