Proposal Summary
This proposal outlines the enhancements for the “Request a Quote” functionality on the
website for Toolfetch. The enhancements include modifications to the Add to Quote
button, and the integration of a popup form for quote requests.
The scope and the provided estimate are based on the anticipation, expectation, and
understanding through our discussions and email. If the scope change/additional feature
development identified during actual development, they will be treated as change request.
Requirement from Toolfetch
Modify the functionality of the “Add to Quote” button on the product detail page. Instead of
redirecting customers to a login or create a new customer page, display a simplified popup
form allowing customers to enter key information and submit the request quickly.
Deliverables
Update Add to Quote Button on Website:
• The implementer will modify the button text to display “Request a Quote”
The implementer will add functionality to the “Request a Quote” button to open a
modal popup containing the form.
• The form will include the following details:
a. Title: Complete the Quote Form below and we will reply within 1 hour (Mon-
Fri 8:30 AM-5 PM ET).
b. User must fill the following fields:
i. First Name
ii. Last Name
iii. Shipping Address
iv. Item Number
v. Number of units
vi. Email Address
vii. Phone Number
1. Submission Process
When the customer clicks the “Add to Quote” button, a custom record will be created in
NetSuite with the submitted details:
• Customer information (name, email, phone, etc.).
• Items and quantities requested.
2. Notification Email
Email Notification:
o A notification email will be sent to the customer to confirm the submission of
their quote request.
o The email will include:
? Summary of the submitted details.
? A unique reference ID for the request.
o Configurable Email Template:
? The email template and sender email address can be configured via a
Configuration Record in NetSuite.
3. Custom Record Review by Sales Rep
Sales representatives will review the custom record in NetSuite to validate the
details and contact the customer if necessary.
Key Fields in the Custom Record:
o Customer information (name, email, phone).
o Requested items and quantities.
o Status (Pending, Approved, Rejected).
o Internal notes for sales representatives to track communication.
4. Approve and Reject Buttons
The implementor will be adding two custom buttons on custom record for approval and rejection
Approve Button:
o Upon clicking, a quote record (Estimate) will be created in NetSuite.
o The quote will be linked to the correct customer:
? If multiple customer records match the provided details, a
notification will be sent to the sales rep to clarify and resolve
duplicates.
Sales reps can manually update the custom record with the correct
customer ID for accurate linking.
Reject Button:
o Updates the custom record’s status to “Rejected.”
o Marks the record as closed without creating a quote.
5. Duplicate Customer Handling
When duplicate customer records are detected:
o Notify the sales representative with a list of matching customer records.
o Provide key details (e.g., name, email, phone, address) for easy identification.
o Allow the sales representative to:
? Contact the customer for clarification.
? Manually update the custom record with the correct customer ID.
6. Workflow Summary
1. Customer Submission:
a. Custom record is created, and notification email is sent.
2. Sales Review:
a. Sales rep reviews the custom record and contacts the customer if necessary.
3. Approval:
a. Creates a quote linked to the correct customer after resolving duplicates.
4. Rejection:
a. Marks the custom record as closed without creating a quote.
7. Configurable Features
Email Configuration:
o Customizable email template and sender address through a configuration
record.
Duplicate Handling:
o Automated notifications for duplicate customers with manual resolution
options.
Scope Limitation
If customer details are updated after the quote is created, these changes won’t
automatically reflect in the associated custom records.
Resolving duplicate customer records depends on manual intervention, which may
slow the process.Assumptions
Assume that enabled duplicate email management for the website
A checkbox will be created on the configuration record for enabling functionality
testing after development.
The estimate is based on our current understanding of the requirements. Any UI or
functionality changes or additional feature development identified during implementation
will be treated as a change request.
The implementor need create quotes and customers for testing.