Proposal Summary
This proposal outlines the scope of enhancing the existing reorder functionality to allow
customers to review and edit personalized checks using Liquid Pixels before placing an
order. This enhancement aims to improve customer satisfaction by providing an opportunity
for customers to verify and modify their personalization details before finalizing their
orders.
The estimated time for the completion of the proposal is 68 hours.
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 Artina Group
• Flag and Highlight Personalized Checks for Review
Any personalized check added to the cart through the reorder feature should be flagged or
highlighted to prompt the customer to review it. This action will direct them to the Liquid
Pixels interface, where their previously provided information will be pre-loaded as
accurately as possible.
• Matching Old Personalization Fields to Liquid Pixels Fields
For orders that previously used Liquid Pixels, this should work seamlessly. However, for
orders that pre-date Liquid Pixels, additional work will be required to match the old
personalization fields with the new Liquid Pixels fields.
• Support for Previously Uploaded Logos and Color Personalization
Previously uploaded logos should also be loaded. If the logo is in an unsupported format, a
message should indicate that the customer needs to provide a new logo.
• Handling Check Starting Numbers
The starting check number should be managed in one of the following ways:
Automatically increment the previously entered starting number by the quantity of checks
previously ordered and provide this as a suggested starting number.
Page I 4Load the previously entered starting number but highlight the field, prompting the customer
to update it.
In either case, the customer should have to change or somehow acknowledge that the
starting number is correct.
• Handing more than one Personalized item in the cart
It should be able to recognize more than one personalized item in the cart and allow
the customer to edit and update each one before proceeding to checkout.
Deliverables
Currently, the item that is ordered (pre-date Liquid Pixels) from the reorder is not auto-
populating field values.
The implementor will add the functionality for auto-populating the data on the edit
option. A new item option will be added to identify items coming from the reorder
section.
Also, the implementor will add a new item option to store the logo name.
o So, logo name will be displayed on the cart page.
o If company color/bank color is not selected, Black will be set as default.
o If font is not selected, Helvetica will be set as default.
o If a user had previously selected the “Add Color Logo for $90” option, the
default $90 for the Color Personalization/Color Logo option will be selected.
To ensure customer awareness, the orders from the reorder section will be
highlighted on the cart page before proceeding to checkout.
Additionally, the implementor will highlight the check start number on the cart page,
allowing customers to notice and update it if necessary.
Currently, it is possible to add more than one liquid pixel item on the cart page and
place an order.
Scope Limitation
The proposal is based on the discussions, anticipations, and understanding through
our discussions and email. Any requirement, change, and feature development
identified during the development process will be treated as change request.
Only the Liquid pixel items are considered in this requirement.
For pre-date Liquid Pixels orders, as well as orders created before our changes, the
logo name cannot be restored. For now, this will be set as a static name.
The logo name will be displayed properly for orders created after our
implementation is completed.
Assumptions
•Development will be initially done in the sandbox and then will be pushed to
production, once verified in the sandbox.
•Any additional changes to the UI or functionality will be considered extra.