Skip to content

Corevist Commerce


We take your feedback and feature requests seriously and often incorporate your requests into our product roadmap. Please share your thoughts with us and interact with other customers like you! While we can't respond to every suggestion, our product team regularly reviews all of the ideas submitted.

When submitting ideas, we encourage you to:
  1. Provide context and/or use cases for your feedback.
  2. Attach screenshots of the area of the application you're wanting improved.
  3. Be supportive and helpful. Upvote the ideas you like and add comments to start a discussion.
  4. If you need immediate assistance with an issue, please contact our support team.

Corevist Commerce

Categories

(thinking…)

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

3 results found

  1. BuyBot enhancements to reduce dependency on Corevist for error resolution.

    Modify the BuyBot process flow so client Customer Service can review the parsed data (adjust if the order failed) and resend the order to SAP. This could be a change for error resolution vs opening a support ticket for Corevist. During error resolution, it would be great to identify the field that failed so it could be quickly reviewed. This would allow the user could make an adjustment and resend to the order to SAP again.

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  BuyBot  ·  Admin →
    Deferred  ·  Rachel Eaton responded

    This would require a rearchitecture of the BuyBot system. This may be an idea for the long term roadmap, but we do not have plans to address this idea in the short term.

  2. BuyBot System (Mapping Errors) visible in SAP

    It would be great to have a trigger directly in SAP when there are system related errors/failures for BuyBot orders (mapping errors, program errors, etc.). Current errors that are seen are SAP standard errors (duplicate PO, materials not set up) however when there are any Corevist/BuyBot errors, these never reach SAP in order to trigger a message. If there was a way that these could be flagged to a predetermined Z-table using an RFC, these could keep both SAP and the PDF order report in sync (and allow for internal reporting on success vs. failure rates) related to both customer/process…

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  BuyBot  ·  Admin →
    Deferred  ·  Rachel Eaton responded

    We're happy to support addition features in BuyBot and the PDF orders report, but do not have plans to send data already present in BuyBot over to SAP. Feel free to submit another idea with the business problem you are trying to solve instead of a desired solution.

  3. PO Header RDD

    If Header RDD is not present in PO, default the Header RDD to the earliest date on the PO lines

    iE: HEADER RDD = 06.30.2022

    Line 10 RDD 06.30.2022

    Line 20 07.05.2022

    Line 30 07.15.2022

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  BuyBot  ·  Admin →
    Deferred  ·  Rachel Eaton responded

    Line item RDD has been implemented. This particular use case can be handled via an SAP project customization.

  • Don't see your idea?