Dear all,
Thank you for your time and effort in responding to the RFP.
In response to your questions, please refer to the RFP for most answers.
The website that currently exists has all of the links, photos & contact information that is needed in the proposed new website. All source materials will be provided by FWA.
Mailchimp will remain intact.
The Paya payment system will remain in place as it stands currently. Possibly an updated Plug-in for WooCommerce subscription.
The current ERP vendor will remain the same for the mapping of WooCommerce to Sage.
Phase 1 deadline remains intact for online sales orders to be up & running with all the testing completed by January 5, 2026.
Phase 2 is open to negotiations, but the date is there to get the upgrades to the website in place as soon as possible.
The “Form” workflow will be directed to the specific department that handles the form subject.
Technical questions/answers for RFP
- The mapping platform- For the FWA Map and the Projects map, do we have a preference for Google Maps, Mapbox, or ArcGIS. You referenced an ArcGIS viewer in the RFP. Do we plan to embed ArcGIS layers, or do you want a WordPress-managed dataset that we can style directly – No preference
 - Please confirm the exact Waterway Status page URL that must remain unchanged and any banner rules for timing and prominence – https://foxwaterway.com/status-waterway/. Banner should update immediately upon status change. We would like it in the header on every page.
 - Does the mobile app need any additional endpoints or data structures beyond reading the current Waterway Status page ? – No
 - The email platform is currently Mailchimp. Should new forms write to Mailchimp only or also to a CRM? If a CRM is in use, which system and objects should receive data? Newsletter sign-up form should only send data to Mailchimp
 - You currently use WP Engine. Are you open to remaining on WP Engine? If you want alternatives, do you prefer a managed WordPress host or a VPS on a cloud provider? Yes, we are open to WP Engine. We prefer a managed WordPress host.
 - Any restrictions on deployment tools or a preference for Git based workflows SEO, analytics, and performance – No restrictions
 
- Please confirm that we should set up GA4, Google Tag Manager with core events, and Google Search Console, and whether you can provide property access for handoff. We can provide property access so you can confirm that everything is communicating properly.
 - If multiple solutions are acceptable, what is the preferred proposal organization: (a) integrated within the main proposal with clear delineation between primary and alternative solutions, (b) primary solution in the main body with alternatives in appendix, or (c) separate proposal documents for each solution? – (b) primary solution in the main body with alternatives in appendix
 
Should pricing for multiple solutions be presented side-by-side in a comparison matrix, or should the primary solution pricing be in the main cost section with alternative pricing in an appendix? How will proposals containing multiple solutions be evaluated—will each solution be scored independently, or will only the primary/recommended solution – pricing for multiple solutions should be presented side-by-side in a comparison matrix. Each solution will be scored independently
- Can you provide a list of plugins, themes, and WooCommerce extensions that are in use on the existing site?
 
Theme: Divi
Contact Form 7
Gravity Forms
Popup Builder
Popup Maker
Redirection
Site Kit by Google
Woo Store Vacation
WooCommerce
WooCommerce Extra Fees Plugin
WooCommerce Paya Gateway
WooCommerce Product Add-Ons Ultimate
WooCommerce.com Update Manager
Wordfence Security
WP Mail SMTP Pro
WP Rocket
WPCode Lite
XML Sitemap Generator for Google
Plugins: To accurately scope the phase 1 work, are you able to provide access to the admin of a staging site for review? – yes
- Will the agency provide access to WP Engine’s staging environment, or should we create a separate development environment under our hosting until migration? – create a separate development environment under your hosting.