Proposal Summary
This proposal covers the scope of remove the dependency of NetSuite from Wineye website
and Admin dashboard.
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 Nickolls & Perks Ltd
The client wants to eliminate the dependency on NetSuite for displaying and updating
products from Liv-Ex, and instead, manage these functionalities directly from the website.
Deliverables
The implementer proposes to eliminate the following dependencies between NetSuite and
Wineye.
1. Product insert/update
The implementer will change the process of product insert/update in Wineye so that it
directly fetched from the Liv-Ex API rather than the map-reduce script (JJ MR Production
Items Sync NPUK-913) from NetSuite.
The implementer will redevelop the functionality same as what is in the map-reduce script
(JJ MR Production Items Sync NPUK-913).
The Liv-Ex APIs that the implementer will use are as follows:
- SEARCH_MARKET_SERVICE_API-/search/v1/searchMarket
- TIGHTSPREAD_API- /grid/v1/grid3
- ABV_DATA_API -/abv/data/v1/abvData
- LWIN_VIEW_API -/lwin/view/v1/lwinView
- ORDER_STATUS_API- /exchange/v1/orderStatus
The implementer will set up a cron job to handle the product insert/update process.
The product data will be updated in the Wineye database, and the details will be displayed
on the admin dashboard.
This process will be scheduled to run every 4 hours.
2. Order sync
The order creation will occur directly in Wineye, so the implementer no longer needs to
perform order syncs with NetSuite.
Page I 4Assumption
The client will provide the required access to Liv-Ex in sandbox and production account.
Note: Since the implementer has already set up a cron job for order updating, it is necessary
to check the processing time and any potential impact on the existing cron job. These checks
can only be performed after the implementation. If the implementer identifies any changes
during this analysis, the customer will be promptly informed. Any additional effort required
will also be communicated.
Scope of limitation
The implementer assumes that the client already has a sandbox domain, and that
initial development can be conducted there. If the implementer needs to create the
domain and handle its related configuration, it will be treated as a change request.