Announcement

Collapse
No announcement yet.

BASK Volume Pricing bug in Suivant

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bruce - PhosphorMedia
    replied
    Leslie You might get a start on asking miva (unless you have direct access) for a csv export of Bill's VP table. In my experiance, they are usually straightforward and simple. Then, generate a product export in miva with the VP fields setup, and then try to convert the EP VP export to match the setup in the miva export.

    Leave a comment:


  • Nick
    replied
    lesliekirk interesting was the store a default setup? I was not able to replicate the issue in a default store. Can you send me the link so I can test?

    Leave a comment:


  • lesliekirk
    replied
    Originally posted by Nick View Post

    lesliekirk It is recommended to use the default Volume Pricing functionality. Unfortunately we do not have any tools to help translate the data from the Emporium Plus export format to the Miva Volume Pricing Import (maybe something ChatGPT can handle).
    Hi Nick the test I did was using the default Marketing Volume Pricing Price Group.

    Leave a comment:


  • Nick
    replied
    Originally posted by lesliekirk View Post
    Really old post but it's looking like the only option is to move away from the EmporiumPlus Volume Pricing module? Just had a store owner realize she is being ripped off by devious individuals who are exploiting this flaw.

    Brennan did you ever developer the tool needed to "translate" the data?
    lesliekirk It is recommended to use the default Volume Pricing functionality. Unfortunately we do not have any tools to help translate the data from the Emporium Plus export format to the Miva Volume Pricing Import (maybe something ChatGPT can handle).

    Leave a comment:


  • lesliekirk
    replied
    Also, I just tested with the Shadows 10.07 ReadyTheme and the problem is still there.

    Leave a comment:


  • lesliekirk
    replied
    Originally posted by Brennan View Post
    Re: BASK Volume Pricing bug in Suivant

    My guess is that the volume pricing is only calculated on the ADPR (add to cart) action. The update action is completely separate. MIva's built in Volume Pricing will handle this correctly if you're able to migrate to it.
    Brennan - I'm attempting to test with just one product assigned to the Volume Pricing Price Group. It is offering the volume discount but when I make adjustments to the product quantity at the BASK screen - is does not return the full price:

    SDB18V.png

    Is there a fix floating around out there?

    Leave a comment:


  • lesliekirk
    replied
    Really old post but it's looking like the only option is to move away from the EmporiumPlus Volume Pricing module? Just had a store owner realize she is being ripped off by devious individuals who are exploiting this flaw.

    Brennan did you ever developer the tool needed to "translate" the data?

    Leave a comment:


  • netblazon
    replied
    Re: BASK Volume Pricing bug in Suivant

    Thanks Brennan.

    Leave a comment:


  • widgetsupply
    replied
    Re: BASK Volume Pricing bug in Suivant

    It would be really nice to be able to choose the discount from the product tabs. It really sucks hunting down what discount the product has to to change it.

    Leave a comment:


  • Brennan
    replied
    Re: BASK Volume Pricing bug in Suivant

    The concept of groups in the basket array was introduced in Version 9. It relates to grouping multiple item into a single line item in the cart in conjunction with promotions. Take for example a Buy 2 get 1 free promotion. Normally Miva would display these are two separate line items since two would have a different price than the third one.

    With Groups, Miva combines all three products into a single line item and displays the savings on the 3rd item. Even though the default page templates now use the groups array on basket, it is completely optional. If you don't need that functionality you can change it back to the normal basket:items array and update the action top be QNTY.

    Regrading our built in volume pricing there are product specific settings and an import for it. One of the problems you may face is the export for the Emporium Module is in a completely different format than the import for our Volume Pricing (You can see the import template under Data Management -> Import settings).

    We looking into providing a tool that translates it easier, but for now there will most likely be some data to massage.

    Leave a comment:


  • netblazon
    replied
    Re: BASK Volume Pricing bug in Suivant

    Brennan, I think this is because Suivant uses QTYG as its action, rather than using the more traditional QNTY, when updating the quantity within the basket. Weiland's Volume Pricing works fine on the QNTY action and always has.

    Rather than forcing a migration at this time, since you guys own the code, could you add support for QTYG?

    If not, what would be the effect of changing Suivant's basket page to loop through items and use QNTY, rather than looping through groups and using QTYG? This is the first I've come across the idea of "groups" in the basket and I'm not entirely sure how they work.

    Thanks,
    Susan

    Leave a comment:


  • widgetsupply
    replied
    Re: BASK Volume Pricing bug in Suivant

    It works in my version 8 5.5 store:
    http://dev.widgetsupply.com/

    Leave a comment:


  • widgetsupply
    replied
    Re: BASK Volume Pricing bug in Suivant

    I guess my questions are:

    - Can i import and export built in Miva volume pricing. If so, it should be pretty easy.

    - The reason I didn't already do it is because it looks to me like you have to add a product, then go to the marketing location to add a quantity discount rather than doing it from the product screens. Is there a way to assign a built in Miva pricing level in the product screens?

    Leave a comment:


  • widgetsupply
    replied
    Re: BASK Volume Pricing bug in Suivant

    Originally posted by Brennan View Post
    My guess is that the volume pricing is only calculated on the ADPR (add to cart) action. The update action is completely separate. MIva's built in Volume Pricing will handle this correctly if you're able to migrate to it.
    Do you have any suggestions for migrating to the built in Miva Volume Pricing.

    Thanks,
    John

    Leave a comment:


  • Brennan
    replied
    Re: BASK Volume Pricing bug in Suivant

    My guess is that the volume pricing is only calculated on the ADPR (add to cart) action. The update action is completely separate. MIva's built in Volume Pricing will handle this correctly if you're able to migrate to it.

    Leave a comment:

Working...
X