Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 4 of 4

Thread: Price Import Ignores MSRP?

  1. #1
    steve@groovecommerce.com is offline Junior Member
    Join Date
    Sep 2009
    Posts
    21

    Default Price Import Ignores MSRP?

    Hi,

    I am trying to use the Price Import feature but it appears that the import completely ignores the imported MSRP value.

    I am exporting a category with 5 products as an Excel document. I am then editing the prices for only one product. I run the import (using the same file I just exported and edited) and the prices and stock have all updated correctly except for the MSRP which stays the same.

    Is this a known issue? I seem to remember seeing someone else mention a similar problem some time ago.

  2. #2
    Rob is offline Senior Member
    Join Date
    Aug 2004
    Posts
    3,037

    Default

    MSRP is not looked at or updated by our default importer no. You could do it via WSi (which can update anything) or you'd have to mod the excel import routine and format to add the MSRP field.

    Why? well, MSRP really isn't used very often anymore, but if you need it, that makes sense, but you'll have to do a small mod for it
    AspDotNetStorefront
    Shopping Cart

  3. #3
    Rob is offline Senior Member
    Join Date
    Aug 2004
    Posts
    3,037

    Default

    and the mod isn't that hard, about 10 mins work.
    AspDotNetStorefront
    Shopping Cart

  4. #4
    steve@groovecommerce.com is offline Junior Member
    Join Date
    Sep 2009
    Posts
    21

    Default

    Already did it myself. All that was necessary was to include the MSRP field in the stored procedure. What I'm curious why it wasn't already included seeing as it's part of the export.