attachment-3-rfp-nhlc-2026-06.xlsx
XLSX spreadsheet 67 KB Posted
- Attached to
- E-Commerce Modernization
- Solicitation number
- RFP NHLC 2026-06
- Issued by
- Merrimack County, New Hampshire
About this file
This file is a comprehensive requirements document for the New Hampshire Liquor and Cannabis Commission's (NHLC) E-Commerce Modernization project, detailing mandatory requirements, system functionalities, implementation specifications, and operational support expectations for a hosted e-commerce platform. The project encompasses development of a multi-user portal supporting brokers, vendors, licensees, and retail customers, with integration to Microsoft Dynamics 365 NextGen and Global Payments systems. Key deliverables include configuration of production, staging, UAT, and development environments; establishment of active interfaces to D365 across all environments; and on-site project manager presence at NHLC headquarters a minimum of three days per week during gap analysis, design, development, testing, and implementation phases, plus five weeks post-launch. The vendor must comply with GovRAMP authorization requirements, NIST SP 800-171 R2 controls, PCI DSS standards, and WCAG 2.1 Level AA accessibility standards, with annual attestation of compliance. Implementation requirements mandate comprehensive gap analysis, detailed design documentation for all customizations, user and administrator documentation in editable format, launch and cutover planning with rollback strategies, and "as built" documentation. The contract term extends through operational support phases with provisions for system enhancements upon statement of work submission.
Operational support commences upon the effective date and extends through contract term and any extensions, with the vendor responsible for maintaining 99.99% uptime excluding scheduled maintenance windows and providing 24/7 technical support with response times of 15 minutes for critical Class A deficiencies, two hours for Class B, and next business day for Class C issues. The vendor must apply all critical patches within 60 days of general availability release and obtain approval from the NHLC Chief Systems Officer for maintenance windows and product updates, with minimum two business days prior notification required. All latest program updates, maintenance releases, and patches are provided at no additional cost, and the vendor shall maintain detailed records of repair and maintenance activities with quarterly reporting on uptime, change requests, critical outages, and deficiency metrics by class. Enhancement requests require vendor quote development within 10 business days of statement of work receipt, with all development following NHLC-approved software development lifecycle methodology. The document includes comprehensive functional requirements across allocations, allowance offers, finance, ordering, payment processing, product information, reporting, and user account management, with data set requirements specifying daily, monthly, and quarterly reports for brokers, vendors, and licensees, including proprietary broker-specific inventory and performance reports and non-proprietary shared reference lists.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| attachment-4-rfp-nhlc-2026-06.pdf | ||
| addendum-1-rfp-nhlc-2026-06.pdf | ||
| addendum-2-rfp-nhlc-2026-06.pdf | ||
| rfp-nhlc-2026-06.pdf | ||
| attachment-1-rfp-nhlc-2026-06.pdf | ||
| attachment-2-rfp-nhlc-2026-06.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
B-2.1 Mandatory Requirements
| Req # | NHLC Requirement Description | Vendor Response |
| M1 | No equipment or services on the State of New Hampshire's Prohibited Technologies List found here: Prohibited Technologies List | |
| M2 | Hosting Environment must be GovRAMP Authorized | |
| M3 | No equipment or services on the FCC Covered List found here: FCC Section 2 List of Equipment and Services | |
| M4 | Comply with controls required by NIST Special Publication 800-171 R2, Protecting Controlled Unclassified Information in Nonfederal Systems | |
| M5 | Comply with Payment Card Industry Data Security Standards (PCI DSS) | |
| M6 | Vendor shall provide an annual Attestation of Compliance (AOC) with PCI DSS | |
| M7 | Web content and mobile applications must comply with WCAG 2.1, Level AA. | |
| M8 | Vendor shall complete the VPAT 2.5 WCAG (November 2023) and submit with their proposal in Section III: Responses to Business and Technical Requirements ITI Accessibility Policy | |
| M9 | Continuous Monitoring – For any resulting award(s) and subsequent contract(s), the awarded contractor(s) will grant access to continuous monitoring and reporting supporting GovRamp Authorization status through the life of the contract. The State reserves the right to request and review all Third-Party Assessment Organization (3PAO) audits, risk assessments, vulnerability assessments, and penetration tests of the contractor's environment. The contractor shall respond to all flaws discovered by providing a mutually agreed remediation plan. | |
| M10 | Vendor shall provide Production environment with established interfaces to D365 NextGen and Global Payments to support all customer activity | |
| M11 | Vendor shall provide a STAGE environment which is maintained in the same software environment as production as is reasonably practical to support problem investigation and hot-fix evaluation. Active interfaces to the D365 STAGE environment shall be established and maintained. | |
| M12 | Vendor shall provide a UAT environment which is maintained in the same software environment as production as is reasonably practical to support user acceptance testing. Active interfaces to the D365 UAT environment shall be established and maintained. | |
| M13 | Vendor shall provide a DEV environment that will support development and integration testing of any website enhancements. Active interfaces to the D365 Dev environment shall be established and maintained. | |
| M14 | Vendor shall monitor and administer all environments and insure that adequate resources are allocated to support the needs of the user base for each environment. | |
| M15 | Vendor Project Manager shall be on-site at NHLC Headquarters a minimum of 3 days per week (8:00 AM to 4:00 PM) for the duration of the gap analysis, design, development, testing and Implementation phases of the project plus the first five weeks after system go live. NHLC shall provide space and connectivity. | |
| M16 | For up to six months prior to end of the contract (including any extensions) the vendor shall participate in turnover tasks to facilitate migration to a new system. |
B-2.2 System Requirements
| Subject Area | Req Number | User Group | NHLC Requirement | Base | Vendor Response |
| Config | |||||
| Custom | |||||
| Allocations | 1 | Broker User | Broker Licensees must be able to submit proposed allocations to NHLC Staff for review and approval | ||
| Allocations | 2 | Broker Users | Brokers must be able to allocate product to a specific customer pending NHLC approval | ||
| Allocations | 3 | Broker Users | Brokers can only allocate merchandise they represent | ||
| Allocations | 4 | NHLC Staff | The NHLC must be able to view submitted allocations with the following information: date submitted, product number, product name, licensee number allocated to, who submitted allocation, status of allocation | ||
| Allocations | 5 | NHLC Staff | Provide the ability to view open existing broker allocations containing the following information: original quantity allocated, original allocation date, allocation expiration date, total purchase, inventory available for purchase | ||
| Allocations | 6 | NHLC Staff | NHLC must be able to approve or reject allocations by one, multiple, or all | ||
| Allocations | 7 | System | Upon rejection by NHLC, broker to receive email notification | ||
| Allocations | 8 | Licensee User | Must provide product allocations and available inventory for Licensee to view | ||
| Allocations | 9 | Broker User | Only Licensees with active license status can have product allocated to them | ||
| Allocations | 10 | Broker Users | Allocations done at the bottle level can only be done if the product is bottle pick eligible | ||
| Allocations | 11 | Broker Users | All products must allow for allocation in case quantity | ||
| Allocations | 12 | Broker Users | Licensees can only have product allocated to them if they are authorized to purchase it | ||
| Allocations | 13 | Broker Users | Brokers must be able to search for Licensees by: licensee name or licensee number | ||
| Allocations | 14 | Broker Users | Submitted allocation must have a start and end date | ||
| Allocations | 15 | Broker Users | Broker must be able to submit allocations by manual entry | ||
| Allocations | 16 | Broker Users | Broker must be able to submit allocations by file upload for one or more products for more than one Licensee in the same file | ||
| Allocations | 17 | Broker Users | Broker must be able to submit allocations by file upload for one or more products to the same Licensee | ||
| Allocations | 18 | Broker Users | Brokers must be able to cancel the unused portion of an allocation at anytime | ||
| Allocations | 19 | Broker Users | Submitted allocations should be accessible to the broker with the following information: date submitted, product number, product name, Licensee number product allocated to, who submitted allocation, status of allocation. | ||
| Allocations | 20 | Broker Users | All data fields on pages are searchable and filterable | ||
| Allocations | 21 | Broker Users | Broker must be able to view any open/existing allocation with the following information: original quantity allocated, original allocation date, allocation expiration date, total purchase, inventory available to purchase | ||
| Allocations | 22 | Broker Users | Brokers available inventory for a product must be reduced by the previous allocations of that product | ||
| Allocations | 23 | Broker Users | Upon allocation expiration, all unpurchased quantities of the allocation are made available to the Broker. | ||
| Allocations | 24 | Licensee User | Licensees must only see their allocated quantity of merchandise | ||
| Allocations | 25 | Licensee User | Total orders must never exceed the total amount of allocated product | ||
| Allocations | 26 | Licensee User | Licensees can place orders against their allocated product multiple times but not be allowed to exceed the available allocated amount | ||
| Allocations | 27 | Licensee User | Ordered quantities must reduce the available quantity of the allocation | ||
| Allocations | 28 | Licensee User | Allocations are visible to Licensees within 15 minutes after NHLC approval | ||
| Allocations | 29 | Licensee User | Product visibility is removed from the Licensee upon depletion of the allocation | ||
| Allocations | 30 | Licensee User | Product visibility is removed from Licensee upon expiration of the allocation | ||
| Allocations | 31 | System | Upon NHLC approval, broker and Licensee to receive email notification | ||
| Allocations | 32 | System | Upon rejection by NHLC, inventory should be released from allocation and returned to the broker’s available quantity | ||
| Allocations | 33 | System | Available quantity of an allocation needs to be maintained in real time | ||
| Allowance Offers | 1 | Broker User | Must be able to propose allowance offers for NHLC review and approval or rejection. | ||
| Allowance Offers | 2 | Broker User | Allowance offers can be for a bailment period, or within a bailment period, submission dates cannot be longer than a bailment period | ||
| Allowance Offers | 3 | Broker User | Broker submissions must be limited by the system to pre-defined submission periods | ||
| Allowance Offers | 4 | Broker User | Allowance Offer submissions may be uploaded using a template downloaded from the website. | ||
| Allowance Offers | 5 | Broker User | Allowance Offers may be manually entered on the website for all price channels | ||
| Allowance Offers | 6 | Broker User | All submissions must be viewable to the broker and display the following data fields: product number, product name, submission date, active date, and who submitted and price channel | ||
| Allowance Offers | 7 | Broker User | Broker submission screen must be searchable and filterable by all data columns and include all submission statuses. | ||
| Allowance Offers | 8 | Broker User | The broker needs the ability to delete any rejected offers | ||
| Allowance Offers | 9 | Broker User | Brokers can only submit for a product that exists and is active | ||
| Allowance Offers | 10 | Broker User | Brokers can only submit for products that they represent | ||
| Allowance Offers | 11 | Broker User | A verification must be performed on all submissions and generate an error warning when applicable. Warnings must include but are not limited to: Product does not exist, Off Prem Warehouse can't be less than Off Prem retail store, Offer can't be less than cost, Offer can't be less than $0.05, Duplicate Offers | ||
| Allowance Offers | 12 | Broker User | Error warnings must be emailed to the brokers as well as displayed on the page | ||
| Allowance Offers | 13 | Broker User | Must be able to apply data archiving rules | ||
| Allowance Offers | 14 | Broker User | Brokers must be able to export a file using the same file format as their import | ||
| Allowance Offers | 15 | Broker User | The export must adhere to how the allowance offer screen is filtered | ||
| Allowance Offers | 16 | Broker User | Broker can submit an allowance offer that is broker funded, state funded, or a mix | ||
| Allowance Offers | 17 | NHLC Staff | NHLC must be able to configure pre-defined submission periods | ||
| Allowance Offers | 18 | NHLC Staff | NHLC must have the ability to upload modified templates for use on the website | ||
| Allowance Offers | 19 | NHLC Staff | All submissions must be viewable to the NHLC to include the following information: product number, product name, submission date, active date, and who submitted and price channel | ||
| Allowance Offers | 20 | NHLC Staff | The NHLC screen needs to be searchable and filterable by all data fields to include all submission statuses | ||
| Allowance Offers | 21 | NHLC Staff | The NHLC needs to be able to review and define the auto approval rules - currently hardcoded | ||
| Allowance Offers | 22 | NHLC Staff | The system must be able to auto approve select offers based on pre-defined auto approval rules set by the NHLC | ||
| Allowance Offers | 23 | NHLC Staff | Any offers that do not meet auto approval rules need to be provided in a list for the NHLC to review and approve or reject | ||
| Allowance Offers | 24 | NHLC Staff | The NHLC needs to be able to review and approve/reject any offers that were not auto approved | ||
| Allowance Offers | 25 | NHLC Staff | The NHLC needs the ability to approve/reject any offers individually, in multiple or all | ||
| Allowance Offers | 26 | NHLC Staff | The NHLC needs to be able to view all submitted offers regardless of approval status | ||
| Allowance Offers | 27 | NHLC Staff | The NHLC Needs to be able to view details about the product in relation to the offer to include the following information: bottle cost, full price retail for period submitted, sale price for channel for offer, and GP% | ||
| Allowance Offers | 28 | NHLC Staff | The NHLC needs the ability to export allowance offers as needed for commission use, in defined format. This layout differs from the required broker export. | ||
| Allowance Offers | 29 | NHLC Staff | The export must adhere to how the allowance offer screen is filtered at time of export | ||
| Allowance Offers | 30 | NHLC Staff | Must be able to apply data archiving rules | ||
| Allowance Offers | 31 | NHLC Staff | The NHLC can submit an allowance offer for any broker as needed, this offer will need to be approved by the NHLC | ||
| Allowance Offers | 32 | NHLC Staff | Error warnings must be emailed to NHLC as well as displayed in the screen | ||
| Allowance Offers | 33 | System | The system applies copy rules for select price channels | ||
| Allowance Offers | 34 | System | If an offer is initially approved, and later rejected in D365, the offer must reflect the change to "rejected" on the website. | ||
| Allowance Offers | 35 | System | Allowance offers must integrate into D365 within an hour of approval | ||
| Finance | 1 | Licensee User | Invoice should contain the original quantity ordered and the quantity that was actually shipped/picked. | ||
| Finance | 2 | Licensee User | Ability to search by order history and prior invoices by product. | ||
| Finance | 3 | Licensee User | Ability to search payment history | ||
| Finance | 4 | Licensee User | Ability to export payment history in CSV and PDF formats | ||
| Finance | 5 | Licensee User | Provide the ability to pay open invoices with ACH and/or credit card payments | ||
| Finance | 6 | Licensee User | Allow the ability to place a deposit on their account for use on future purchase(s) with credit card and/or ACH payments | ||
| Finance | 7 | Licensee User | Must have a role to allow Licensee users to view and pay invoices and view payments, and credits on behalf of one, multiple, or all of the licenses in the business enterprise | ||
| Finance | 8 | Licensee User | Invoices must be exportable in CSV and PDF formats | ||
| Finance | 9 | Licensee User | An invoice view must provide the status of invoices (open, canceled, paid, closed, etc.) | ||
| Finance | 10 | System | Invoices created by D365 must integrate, be viewable and payable on the website | ||
| Finance | 11 | Licensee User | Must have a role to allow Licensee users to view invoices on behalf of one, multiple, or all of the licenses in the business enterprise | ||
| Licensee User Experience | 1 | System | User experience must be based on user group and roles assigned to the user account | ||
| Licensee User Experience | 2 | Broker User | Only view information for products the Broker represents | ||
| Licensee User Experience | 3 | Broker User | Must be able access: Allocations, Purchase Price Submission, Product Submission/Approval, Inventory Transactions, Order Samples, Products, Reports, Promo Card, Image Submission/Approval | ||
| Licensee User Experience | 4 | Broker User | Show total inventory at warehouse in bottles and case amounts | ||
| Licensee User Experience | 5 | Broker User | Show total inventory in retail stores in bottles and case amounts | ||
| Licensee User Experience | 6 | Broker User | When a product’s inventory total is selected, must be able to drill down to show where the inventory is located | ||
| Licensee User Experience | 7 | Broker User | When a product is selected, website must show sale price for all price groups | ||
| Licensee User Experience | 8 | Broker User | When a product is selected the cost for the prior three months and next six months should display | ||
| Licensee User Experience | 9 | Broker User | Sale pricing and cost tables must be filterable | ||
| Licensee User Experience | 10 | Broker User | When a product is selected, display the total inventory of warehouse and retail store locations. Must be able to drill down to inventory of bottles and cases. Must be able to drill down to inventory at warehouse and inventory and retail locations | ||
| Licensee User Experience | 11 | Broker User | When a product is selected, must display the inventory of product at both warehouse and retail store level | ||
| Licensee User Experience | 12 | Broker User | When a product is selected, show total inventory at warehouse in bottles and case amounts | ||
| Licensee User Experience | 13 | Broker User | When a product is selected, show total inventory in retail stores in bottles and case amounts | ||
| Licensee User Experience | 14 | Licensee User | Ability to select and change a default shopping location (Retail Outlet or Warehouse) | ||
| Licensee User Experience | 15 | Licensee User | Only display inventory for products that are available for purchase by the user type viewing the information | ||
| Licensee User Experience | 16 | Licensee User | All available inventory for all authorized locations must be displayed when no specific location or product is selected. When selecting a specific product, provide an option to view its available inventory quantities across all authorized locations. | ||
| Licensee User Experience | 17 | Licensee User | Provide the ability to select a retail location to view or shop for products. If product is searched but no location is selected, only those retail locations with available inventory will display. If customer selects a product and a location, that location must have available inventory to yield results. | ||
| Licensee User Experience | 18 | Licensee User | If user changes their shopping location during a session, the site must then display the inventory for the new shopping location. | ||
| Licensee User Experience | 19 | Licensee User | Product search must adhere to defined rules and display only products allowed for purchase by the customer type. | ||
| Licensee User Experience | 20 | Licensee User | Each retail location will only display selected products with available inventory. Retail locations will not show out of stock products. | ||
| Licensee User Experience | 21 | Broker User | Product information on the landing page screen must provide the following information: product name, product number, product size, product lifecycle state, product image, pack size, current MSRP | ||
| Licensee User Experience | 22 | NHLC Staff | The NHLC must possess the ability to restrict products from displaying based upon both customer type and product characteristics. | ||
| Licensee User Experience | 23 | NHLC Staff | NHLC must see all products | ||
| Licensee User Experience | 24 | NHLC Staff | Allow the NHLC to view product inventory at warehouses and retail locations | ||
| Licensee User Experience | 25 | System | When a product is selected, website must show the product characteristics from D365 | ||
| Licensee User Experience | 26 | NHLC Staff | Marketing promotion group should update dynamically on the website based on product lifecycle state (Powerbuy, new products, etc.) | ||
| Licensee User Experience | 27 | NHLC Staff | Support a promotion type that allows Marketing to designate specific products to be shown in a special grouping for the promotion. Products can be designated individually and by file upload. (e.g. Outlet Price Busters) | ||
| Licensee User Experience | 28 | System | Business license types are displayed based on the License Description field in D365 | ||
| Order Fulfillment Tool | 1 | NHLC Staff | The system provides a notification to retail store staff when an order needs to be processed | ||
| Order Fulfillment Tool | 2 | NHLC Staff | The order fulfillment tool (OFT) needs to be accessible on a mobile device in addition to a standard PC. | ||
| Order Fulfillment Tool | 3 | NHLC Staff | Is sortable/filterable on all columns | ||
| Order Fulfillment Tool | 4 | NHLC Staff | Has the ability to search by order number, order date, customer name, customer number | ||
| Order Fulfillment Tool | 5 | NHLC Staff | Have the ability to print picking and packing slips | ||
| Order Fulfillment Tool | 6 | NHLC Staff | The ability to search for orders within 90 days | ||
| Order Fulfillment Tool | 7 | NHLC Staff | The printed picking and packing slips must display customer information (Name, Account Number, Address, Shipping Address, Email Address, Phone Number, Pick Up Person, Date ordered, Date Picked, Date Shipped) | ||
| Order Fulfillment Tool | 8 | NHLC Staff | The printed picking and packing slips must display information about the product purchased (Product Number, Product Name, Quantity Ordered, Quantity Picked/Shipped) | ||
| Order Fulfillment Tool | 9 | NHLC Staff | The printed picking and packing slips must display information about the pricing of the products purchased (individual product purchase price, total Line price, individual product cost X quantity) | ||
| Order Fulfillment Tool | 10 | NHLC Staff | The printed picking and packing slips must show any discounts and coupons applied to the order. | ||
| Order Fulfillment Tool | 11 | NHLC Staff | The printed picking and packing slips must show a subtotal and total and reflect all line totals minus any discounts and coupons | ||
| Order Fulfillment Tool | 12 | NHLC Staff | Capture customer digital signature at time of pick up and integrate to D365 | ||
| Order Fulfillment Tool | 13 | NHLC Staff | Update and communicate the statuses of order processing (Open, Picking, Packing, Picked, Shipped) at a minimum | ||
| Order Fulfillment Tool | 14 | NHLC Staff | The quantity of cases and bottles is clearly displayed when the same product number has both ordered. | ||
| Order Fulfillment Tool | 15 | NHLC Staff | Order processing screens group ordered products by product category | ||
| Order Fulfillment Tool | 16 | NHLC Staff | Support the use of handheld scanners in the picking, packing, and validation of order processing | ||
| Ordering - Consumer | 1 | Retail Customer | Customer can order more than one unit of measure (Bottle/Case/Subpack) of the same product number in the same order. | ||
| Ordering - Consumer | 2 | Retail Customer | Perform inventory checks on selected products every time a location change occurs. | ||
| Ordering - Consumer | 3 | Retail Customer | Include shipping/tracking details in shipping confirmation email/text | ||
| Ordering - Consumer | 4 | Retail Customer | Customer should only be allowed to populate their shopping carts in locations that support their customer type. | ||
| Ordering - Consumer | 5 | Retail Customer | The ability for the customer to log into their account and follow the status of their order fulfillment process. | ||
| Ordering - Consumer | 6 | Retail Customer | Provide customized text/email messages to the customer throughout the order process (Received, Picked, Shipped, etc.) | ||
| Ordering - Consumer | 7 | Unverified User | The ability to add items to a shopping cart must be available to guest users | ||
| Ordering - Consumer | 8 | System | Must provide a process to address abandoned/inactive carts to ensure temporarily reserved inventory is released. | ||
| Ordering - Consumer | 9 | Retail Customer | Products may be ordered from retail stores by the bottle without incurring a bottle-pick fee. | ||
| Ordering - Consumer | 10 | System | Orders must integrate into D365 as close to real time as possible after finalization | ||
| Ordering - Customer | 11 | Retail Customer | Full product information and ordering functionality must be available in mobile responsible format to allow ordering from phones and tablets. | ||
| Ordering - Licensee | 1 | Licensee User | Visibility of product inventory should be pre-determined by customer type and NHLC-defined product characteristics | ||
| Ordering - Licensee | 2 | Licensee User | Provide the ability to place orders using a File Upload | ||
| Ordering - Licensee | 3 | Licensee User | Provide the ability to place orders using a saved or cloned cart | ||
| Ordering - Licensee | 4 | Licensee User | Provide the ability to place orders using an order sheet in a NHLC-defined format | ||
| Ordering - Licensee | 5 | Licensee User | All orders must be validated for data integrity (ex. valid product ID, active license, etc.) | ||
| Ordering - Licensee | 6 | Licensee User | Allow all 3rd party shipping orders to select a ship/pick-up date between 1 day and 10 days post order date | ||
| Ordering - Licensee | 7 | Licensee User | All product pricing is at the time of the order not the ship date | ||
| Ordering - Licensee | 8 | Licensee User | Apply and display configurable fees as a separate line item when individual bottles are ordered | ||
| Ordering - Licensee | 9 | Licensee User | Provide case/sub pack quantity on the product page | ||
| Ordering - Licensee | 10 | Licensee User | Provide a summed total of product inventory available to purchase with the ability to drill down by each location | ||
| Ordering - Licensee | 11 | Licensee User | When a location is selected, only inventory totals for that location should display for each product | ||
| Ordering - Licensee | 12 | Licensee User | Allow Licensee Users the ability to see out of stock products | ||
| Ordering - Licensee | 13 | Licensee User | Whether a product is "eligible" is determined by its product characteristics | ||
| Ordering - Licensee | 14 | Licensee User | If a product is "bottle pick" eligible within the product list view, display both the case price and the bottle price | ||
| Ordering - Licensee | 15 | Licensee User | If product is "bottle pick" eligible in the list view, allow it to be added to cart as a case. | ||
| Ordering - Licensee | 16 | Licensee User | If a product is "bottle pick" eligible in product detail, allow the ability to toggle between bottle and case. Update the price dynamically and add to cart based on unit of measure selected | ||
| Ordering - Licensee | 17 | Licensee User | If a bottle in case quantity is added to a cart, automatically change unit of measure to a case and update quantity to the correct corresponding amount. No additional charges should be applied. | ||
| Ordering - Licensee | 18 | Licensee User | Enable products to be ordered by each unit of measure (Bottle/Case/Subpack - each or all) | ||
| Ordering - Licensee | 19 | System | Site must transmit all ordered inventory to D365 in bottles regardless of ordered unit of measure | ||
| Ordering - Licensee | 20 | System | Support product purchase limits based on NHLC-defined product characteristics | ||
| Ordering - Licensee | 21 | System | Inventory added to a cart must be temporarily reserved for a NHLC pre-defined period of time until order is finalized. If order is not finalized within the pre-defined period of time, inventory will become available to other users. | ||
| Ordering - Licensee | 22 | System | If inventory is no longer available by the time a user checks out, a message must be displayed to inform the user that the inventory is no longer available. | ||
| Ordering - Licensee | 23 | Licensee User | Display the inventory from the location based on the default order settings of the product | ||
| Ordering - Licensee | 24 | Broker User | Only provide the ability to order from the warehouse | ||
| Ordering - Licensee | 25 | Broker User | When ordering product, a Broker must receive Off Prem pricing | ||
| Ordering - Licensee | 26 | Licensee User | Full product information and ordering functionality must be available in mobile responsible format to allow ordering from phones and tablets | ||
| Out-of-State Transfer | 1 | Broker User | Provide the ability to request an out-of-state transfer for shipping | ||
| Out-of-State Transfer | 2 | Broker User | Provide the ability to request out-of-state transfer via file upload | ||
| Out-of-State Transfer | 3 | Broker User | Out-of-state transfer requests must transmit to the NHLC for approval | ||
| Out-of-State Transfer | 4 | Broker User | Broker can only request transfers from vendor owned inventory | ||
| Out-of-State Transfer | 5 | Broker User | Display available on hand inventory on to the request screen | ||
| Out-of-State Transfer | 6 | Broker User | Allow the portal to show all out-of-state transfer details (Date submitted, who submitted, date modified, status) | ||
| Out-of-State Transfer | 7 | Broker User | All portal fields need to be filterable and searchable | ||
| Out-of-State Transfer | 8 | NHLC Staff | Must have the ability to approve or reject out-of-state transfer requests | ||
| Out-of-State Transfer | 9 | NHLC Staff | Display available on hand inventory on the approval screen | ||
| Out-of-State Transfer | 10 | NHLC Staff | Enable portal to show all out-of-state transfer requests and the following information: Date submitted, who submitted, date modified, status | ||
| Out-of-State Transfer | 11 | NHLC Staff | All portal fields need to be filterable and searchable | ||
| Out-of-State Transfer | 12 | NHLC Staff | Review and approve or deny requests for out-of-state transfer | ||
| Out-of-State Transfer | 13 | System | Send a "we have received your request" email to the broker | ||
| Out-of-State Transfer | 14 | System | Send approval or rejection email to Broker | ||
| Out-of-State Transfer | 15 | System | Send inventory status change to D365 | ||
| Out-of-State Transfer | 16 | System | Send file to DHL for processing | ||
| Out-of-State Transfer | 17 | System | Send confirmation of DHL receipt of file to NHLC | ||
| Out-of-State Transfer | 18 | System | Out-of-State transfer will integrate once approved | ||
| Payment | 1 | Licensee User | During the checkout process, preauthorization of the payment method must be performed on the total value of the order placed. Once the order is finalized, only the total for the fulfilled (picked/shipped) products will be captured against the payment method used. | ||
| Payment | 2 | Licensee User | Must support the use of ACH, credit card, and "House" accounts as payment options | ||
| Payment | 3 | Licensee User | Enable the account's ability to apply any credit on their account to their purchase at time of checkout and enable the account’s ability to apply any credits to open invoices. | ||
| Payment | 4 | Licensee User | Provide the ability to pay individual invoices or multiple invoices in a single transaction | ||
| Payment | 5 | Licensee User | Allow the ability to make a partial payment on an open invoice | ||
| Payment | 6 | Licensee User | Payments must be applied to the oldest invoices first (FIFO) | ||
| Payment | 7 | Licensee User | When invoice is selected, display the line details of the invoices | ||
| Payment | 8 | Licensee User | Invoices need to be filterable by status (open, canceled, paid, closed, etc.) | ||
| Payment | 9 | Licensee User | Invoices created by retail register purchases must be integrated into D365 and be able to be viewed and processed on the website. | ||
| Payment | 10 | Licensee User | Payments must be integrated to Dynamics using Customer Payment Journals | ||
| Payment | 11 | Licensee User | Invoices must be exportable in Excel and PDF formats | ||
| Payment | 12 | Licensee User | Provides status of invoices (open, canceled, paid, closed, etc.) | ||
| Payment | 13 | Licensee User | Payment to integrate into D365 in real time | ||
| Payment | 14 | Licensee User | House Account is prohibited from being used for payment of invoices | ||
| Payment | 15 | Licensee User | Email confirmation is sent to Licensee when payment is made | ||
| Payment | 16 | Retail Customer | The checkout process must have the flexibility to accept multiple forms of payment as well as multiple forms of payment within the same transaction (split payments) including but not limited to: any combination of house credit, eCheck/ACH, credit cards, or Stored Value Cards. | ||
| Payment | 17 | Retail Customer | If a transaction is not finalized the refund must be returned to the original form of payment(s). If a transaction that has partial payments does not complete, all partial payments are refunded to the original form of payment | ||
| Payment | 18 | Retail Customer | Must support all major online payment methods, including all major credit cards and Stored Value Cards | ||
| Payment | 19 | Retail Customer | Payment processing must occur via PCI-compliant Hosted Payment Page or embedded iframe hosted by PCI-compliant provider | ||
| Payment | 20 | Retail Customer | Must provide the ability for a customer to check their Stored Value Card balance with a third-party provider. | ||
| Payment | 21 | System | Must integrate with the NHLC's Stored Value Card platform | ||
| Payment | 22 | System | Perform a system check to validate whether the licensee is approved to use ACH as a payment option | ||
| Payment | 23 | System | Perform a system check to validate whether the licensee is approved to use House Account as a payment option | ||
| Payment | 24 | System | Perform a system check on ACH payments to ensure the purchase total is within the approved dollar limits set for the specific account placing the order | ||
| Payment | 25 | System | Perform a system check for "On Account" Purchases to validate that the purchase total is within approved dollar limits set for the specific account placing the order | ||
| Payment | 26 | System | Conduct a check on all Licensee purchases to determine if the account is delinquent or on credit hold | ||
| Payment | 27 | System | Notify the Licensee at the time of purchase if an order is placed while delinquent or as soon as the account goes on credit hold | ||
| Payment | 28 | System | Conduct a check on all Licensee purchases to ensure the account is still authorized to make purchases | ||
| Payment | 29 | System | Daily Payment reconciliation report is sent to NHLC Staff which includes a list of orders and invoices that were processed over 24 hour period. Reports must include the source and details of any payments | ||
| Payments - Licensee | 1 | Broker User | Notification is sent to Broker when payment is made | ||
| Payments - Licensee | 2 | Vendor User | Notification is sent to Vendor when payment is made | ||
| Product Information | 1 | All | The system should allow filtering by several filter categories | ||
| Product Information | 2 | All | Provide intuitive search capabilities to compensate for spelling errors | ||
| Product Information | 3 | All | Provide intuitive search capabilities to return results closely matching "most likely" to "least likely". | ||
| Product Information | 4 | All | Users should be able to filter search results | ||
| Product Information | 5 | All | Enable search capabilities returning results which contain product number or partial product number | ||
| Product Information | 6 | All | Enable search capabilities returning results which contain product name or partial product name | ||
| Product Information | 7 | All | Users should be able to search and filter by product size/unit of measure | ||
| Product Information | 8 | All | Users should be able to search and filter by product sub type (ex. Vodka, Pinot Noir) | ||
| Product Information | 9 | All | Users should be able to search by product style (ex. Flavored Vodka, White Wine) | ||
| Product Information | 10 | All | Users should be able to search by product country of origin | ||
| Product Information | 11 | All | Users should be able to filter by product price range | ||
| Product Information | 12 | All | Users should be able to filter by product type | ||
| Product Information | 13 | All | Users should be able to filter by product sub type | ||
| Product Information | 14 | All | Users should be able to filter by proof value or alcohol percentage | ||
| Product Information | 15 | All | Users should be able to filter by country, or state | ||
| Product Information | 16 | All | Users should be able to filter by a specific product flavor | ||
| Product Information | 17 | All | Users should be able to filter by appellation | ||
| Product Information | 18 | All | Users should be able to filter by vintage | ||
| Product Information | 19 | All | Users should be able to filter by region | ||
| Product Information | 20 | All | Users should be able to filter by product certification | ||
| Product Information | 21 | All | Product characteristics from D365 should be searchable/filterable on websites | ||
| Product Information | 22 | All | Search functionality should allow for the use of wildcard entries | ||
| Product Information | 23 | All | Provide the ability to search for products that are part of the current promotion | ||
| Product Information | 24 | All | Ability to search for products that are a part of marketing initiatives | ||
| Product Information | 25 | All | When a product is offered at a reduced price, the following pricing details must be displayed on the product page and within the cart: Original Price, Discount Price and Total Savings. | ||
| Product Information | 26 | Broker User | Must be able to display inventory in all retail locations, Vendor and NHLC Owned inventory in Bailment warehouses and NHLC owned inventory in state-owned warehouse or represented products | ||
| Product Information | 27 | Broker User | Allow the ability to see out-of-stock products | ||
| Product Information | 28 | Broker User | Broker must be able to access the following: Allocations, Purchase Price Submission, Product Submission/Approval, Out-of-State Transfers, Order Samples, Products, Reports, Image Submission/Approval, Invoice Payments for products they represent. | ||
| Product Information | 29 | Broker User | Only products represented by broker should be viewable. | ||
| Product Information | 30 | Broker User | Display the pricing of all pricing group channels for the selected product for the previous three months and the next six months. | ||
| Product Information | 31 | Broker User | Display the product cost for the previous three months and the next six months for selected product | ||
| Product Information | 32 | Broker User | Sale pricing and cost tables must be filterable | ||
| Product Information | 33 | Broker User | When selecting a product, display its inventory in total for the warehouse and retail stores. Provide the ability to drill down this value to view the inventory levels separately between bottles and cases. Enable further drill down to view inventory separately between the warehouse and the retail stores. Provide a separate drill down to see the inventory of both bottles and cases at each retail location. | ||
| Product Information | 34 | Broker User | When a product is selected, show its inventory at both warehouse and retail store level. | ||
| Product Information | 35 | Broker User | When a product is selected, display its total inventory separately between bottle and case amounts at the warehouse location. | ||
| Product Information | 36 | Broker User | When a product is selected, display its total inventory separately between bottle and case amounts at the retail store locations. | ||
| Product Information | 37 | Broker User | When a product is selected enable editing capabilities for product submissions | ||
| Product Information | 38 | Broker User | Only certain NHLC-defined fields should be editable. When editing a product, only those fields identified as editable should be enabled. | ||
| Product Information | 39 | Licensee User | Product pricing displayed is based on the customer type of the Account User | ||
| Product Information | 40 | Licensee User | Show product inventory at both the warehouse(s) and retail stores | ||
| Product Information | 41 | Licensee User | Display total inventory in bottles and case amounts at warehouse(s). | ||
| Product Information | 42 | Licensee User | Display total inventory in bottles and case amounts at retail stores. | ||
| Product Information | 43 | Licensee User | When viewing a product’s total inventory, provide a breakdown of inventory by location. | ||
| Product Information | 44 | Vendor User | Product information on the landing page screen must display the following data fields: Product name, Product number, Product size, Product lifecycle state, Product image, pack size, current MSRP. | ||
| Product Information | 45 | Broker User | Display the D365 product characteristic when selection is made. | ||
| Product Information | 46 | NHLC Staff | All edits must be approved by the NHLC | ||
| Product Information | 47 | System | Updates to inventory must be performed as near real time (preference) as possible but no less frequently than every 15 minutes. | ||
| Product Information | 48 | System | Must provide a nightly full refresh of available inventory | ||
| Product Information | 49 | System | Must be able to map to all inventory statuses used in D365 | ||
| Product Information | 50 | System | Obtain product images and descriptions from a third-party system | ||
| Product Information | 51 | Vendor User | Only products represented by the vendor should be viewable | ||
| Product Information | 52 | Vendor User | Vendor must be able to access the following: Purchase Price Submission, Product Submission/Approvals, Reports, Image Submissions, Invoices. | ||
| Product Information | 53 | Vendor User | Must be able to display inventory in all retail locations, Vendor and NHLC owned inventory in Bailment warehouses and NHLC owned inventory in state-owned warehouse for represented products | ||
| Product Information | 54 | Vendor User | Allow the ability to see out-of-stock products | ||
| Product Information | 55 | Vendor User | Display the pricing of all pricing group channels for the selected product for the previous three months and the next six months. | ||
| Product Information | 56 | Vendor User | Display the product cost for the previous three months and the next six months for selected product. | ||
| Product Information | 57 | Vendor User | Sale pricing and cost tables must be filterable | ||
| Product Information | 58 | Vendor User | When selecting a product, display its inventory in total for the warehouse and retail stores. Provide the ability to drill down this value to view the inventory levels separately between bottles and cases. Enable further drill down to view inventory separately between the warehouse and the retail stores. Provide a separate drill down to see the inventory of both bottles and cases at each retail location. | ||
| Product Information | 59 | Vendor User | When a product is selected, show its inventory at both warehouse and retail store level | ||
| Product Information | 60 | Vendor User | When a product is selected, display its total inventory separately between bottle and case amounts at the warehouse location | ||
| Product Information | 61 | Vendor User | When a product is selected, display its total inventory separately between bottle and case amounts at the retail store locations. | ||
| Product Information | 62 | Vendor User | When a product is selected, enable editing capabilities for product submissions. | ||
| Product Information | 63 | Vendor User | Only certain NHLC-defined fields should be editable. When editing a product, only those fields identified as editable should be enabled. | ||
| Product Pricing | 1 | Broker User | Broker must be able to approve/reject purchase price submitted by vendors, approved offers must pass to NHLC for approval | ||
| Product Pricing | 2 | Broker User | Broker must have the ability to submit purchase price to NHLC for approval process | ||
| Product Pricing | 3 | Broker User | Details on the submitted cost must show the current case cost, the current retail bottle price, the new case cost, new retail bottle price | ||
| Product Pricing | 4 | Broker User | Cost may be submitted via upload. Required fields are: product number, start date, case cost | ||
| Product Pricing | 5 | Broker User | Cost may be submitted manually on the website individually. Required fields are: product number, start date, case cost | ||
| Product Pricing | 6 | Broker User | Brokers can only submit purchase prices for products they represent | ||
| Product Pricing | 7 | Broker User | Brokers can only submit purchase prices for products that exists in the system and are active products | ||
| Product Pricing | 8 | Broker User | Provide a verification check on all submissions. Display error warnings as applicable. Warnings must include, but are not limited to: Duplicate product number, Product does not exist, Product does not belong to the Broker/Vendor | ||
| Product Pricing | 9 | Broker User | Error warnings must be emailed to the vendors/brokers as well as displayed on the page | ||
| Product Pricing | 10 | Broker User | All submissions must be viewable to the vendor/broker and contain the following data fields: product number, product name, submission date, active date, and who submitted | ||
| Product Pricing | 11 | Broker User | Vendor/Broker submission screen should be searchable and filterable by all data columns and all submissions statuses. | ||
| Product Pricing | 12 | NHLC Staff | The application of promotions and coupons is configurable to be either favorable for the NHLC or the customer | ||
| Product Pricing | 13 | NHLC Staff | NHLC to create configurable messaging of promotional events | ||
| Product Pricing | 14 | NHLC Staff | NHLC must have the ability to accept/reject all purchase prices. Accepted purchase prices will integrate into D365 | ||
| Product Pricing | 15 | NHLC Staff | Details on the submitted cost must show the following information: current case cost, the current retail bottle price, the new case cost, new retail bottle price | ||
| Product Pricing | 16 | NHLC Staff | NHLC must have the ability to accept/reject one, multiple, or all purchase price submissions | ||
| Product Pricing | 17 | NHLC Staff | Accepted prices must integrate to D365 within an hour | ||
| Product Pricing | 18 | NHLC Staff | All submissions must be viewable to the NHLC with the following information: product number, product name, submission date, active date, and who submitted | ||
| Product Pricing | 19 | NHLC Staff | The NHLC must have the ability to export purchase prices for commission uses as needed in a format to be defined by the NHLC | ||
| Product Pricing | 20 | NHLC Staff | The export must adhere to how the purchase price screen is filtered at time of export | ||
| Product Pricing | 21 | NHLC Staff | The NHLC screen needs to be searchable and filterable by all data columns to include the statuses of all submissions | ||
| Product Pricing | 22 | System | The system must be able to ingest and apply promotions and coupons that have been configured in D365 | ||
| Product Pricing | 23 | System | Sale pricing must be displayed on all pages that show product. | ||
| Product Pricing | 24 | System | Ability to interface with third-party marketing platforms. | ||
| Product Pricing | 25 | Vendor User | Vendor must have ability to submit purchase price to broker for approval process | ||
| Product Pricing | 26 | Vendor User | Vendors can only submit purchase prices for products they represent | ||
| Product Pricing | 27 | Vendor User | Vendors can only submit purchase prices for products that exists in the system and are active products | ||
| Product Pricing | 28 | Vendor User | Details on the submitted cost must show the current case cost, the current retail bottle price, the new case cost, new retail bottle price | ||
| Product Pricing | 29 | Vendor User | Cost may be submitted via upload. Required fields are: product number, start date, case cost | ||
| Product Pricing | 30 | Vendor User | Cost may be submitted manually on the website individually. Required fields are: product number, start date, case cost | ||
| Product Pricing | 31 | Vendor User | Provide a verification check on all submissions. Display error warnings as applicable. Warnings must include, but are not limited to: Duplicate product number, Product does not exist, Product does not belong to the Broker/Vendor | ||
| Product Pricing | 32 | Vendor User | Error warnings must be emailed to the vendors/brokers as well as displayed on the page | ||
| Product Pricing | 33 | Vendor User | All submissions must be viewable to the vendor/broker and contain the following data fields: product number, product name, submission date, active date, and who submitted | ||
| Product Pricing | 34 | Vendor User | Vendors cannot purchase product, submit Allowance Offers, Request Out-of-State Transfers, or Allocations | ||
| Product Submission | 1 | Broker User | Must be able to propose new products to the NHLC | ||
| Product Submission | 2 | Broker User | Must be able to submit products manually | ||
| Product Submission | 3 | Broker User | Must be able to submit products in a bulk upload | ||
| Product Submission | 4 | Broker User | Products submitted manually will have a dynamic submission page that will change based on product type being submitted | ||
| Product Submission | 5 | Broker User | Product submission templates will be provided for download on the website | ||
| Product Submission | 6 | Broker User | Uploaded products must allow for an image and cost to be applied prior product submission | ||
| Product Submission | 7 | Broker User | Submitted case cost returns an estimated MSRP on case and bottle cost | ||
| Product Submission | 8 | Broker User | Product ID numbers are sourced from the next available number | ||
| Product Submission | 9 | Broker User | Broker can approve/reject Vendor submitted products | ||
| Product Submission | 10 | Broker User | Rejected products can be rejected with or without the ability to edit | ||
| Product Submission | 11 | Broker User | If broker approves the vendor submission, product then goes to NHLC for approval | ||
| Product Submission | 12 | Broker User | Broker submitted products must go to NHLC for approval/rejection | ||
| Product Submission | 13 | Broker User | If a product was rejected and is editable, Broker can see that status in the submission list | ||
| Product Submission | 14 | Broker User | Broker should have the ability to edit NHLC-defined fields and resubmit to NHLC for approval/rejection | ||
| Product Submission | 15 | Broker User | All product submissions are visible and contain the following data fields: Product number, date submitted, status, product name, with all fields searchable and filterable | ||
| Product Submission | 16 | Broker User | When selected, all submitted product information is available: status, submitted by, submitted date, last modified, last modified by | ||
| Product Submission | 17 | Broker User | Must be able to submit product | ||
| Product Submission | 18 | Broker User | Must be able to submit product in bulk via upload | ||
| Product Submission | 19 | Broker User | Must be able to submit product manually on the website | ||
| Product Submission | 20 | Broker User | Products submitted manually will have a dynamic submission page that will change based on product type being submitted | ||
| Product Submission | 21 | Broker User | Product submission templates will be provided for download on the website | ||
| Product Submission | 22 | Broker User | Submitted case cost returns an estimated MSRP case and bottle cost | ||
| Product Submission | 23 | Broker User | All product submissions are displayed with the following information: product number, date submitted, status, product name, with all fields searchable and filterable | ||
| Product Submission | 24 | NHLC Staff | Provide the ability to accept or reject product submissions both individually or in multiples | ||
| Product Submission | 25 | NHLC Staff | Allow NHLC to approve/reject any product edits | ||
| Product Submission | 26 | NHLC Staff | Uploaded products must be accessible to allow an image and cost to be applied to product submission | ||
| Product Submission | 27 | NHLC Staff | NHLC can approve/reject broker submitted products | ||
| Product Submission | 28 | NHLC Staff | Rejected products can be rejected with or without the ability to edit | ||
| Product Submission | 29 | NHLC Staff | When selected, all submitted information is available for review: status, submitted by, submitted date, last modified, last modified by | ||
| Product Submission | 30 | NHLC Staff | NHLC has the ability to select one or many records | ||
| Product Submission | 31 | NHLC Staff | NHLC must be able to submit products for any broker or vendor | ||
| Product Submission | 32 | NHLC Staff | Any NHLC created products must be approved/rejected by the NHLC | ||
| Product Submission | 33 | NHLC Staff | If a product was rejected and is editable, NHLC should be able to see that status on the submission list | ||
| Product Submission | 34 | NHLC Staff | NHLC staff should be able to edit NHLC-defined fields and resubmit to NHLC for approval/rejection | ||
| Product Submission | 35 | NHLC Staff | NHLC must be able to input any available product in D365 for submission | ||
| Product Submission | 36 | NHLC Staff | NHLC must have the ability to submit non-standard products via a dynamic submission page containing applicable data entry fields | ||
| Product Submission | 37 | NHLC Staff | Approvals and rejections must be able to be performed individually, in multiples, or all | ||
| Product Submission | 38 | System | Pricing and Product details must update in real time | ||
| Product Submission | 39 | System | Product ID number is sourced from the next available number | ||
| Product Submission | 40 | System | Approved products must integrate into D365 at least once a day | ||
| Product Submission | 41 | System | Fully rejected products will not integrate into Dynamics | ||
| Product Submission | 42 | Vendor User | Vendor submitted products must got to broker for approval/rejection | ||
| Product Submission | 43 | Vendor User | If a product was rejected and is editable, vendor can see that in status submission list | ||
| Product Submission | 44 | Vendor User | Vendor can edit NHLC-defined fields and resubmit to broker for approval/rejection | ||
| Product Submission | 45 | Vendor User | Must be able to propose new products to the NHLC | ||
| Product Submission | 46 | Vendor User | Must be able to submit products in a bulk upload | ||
| Product Submission | 47 | Vendor User | Must be able to submit products manually | ||
| Product Submission | 48 | Vendor User | Products submitted manually will have a dynamic submission page that will change based on product type being submitted | ||
| Product Submission | 49 | Vendor User | Product submission templates will be provided for download on the website |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .