In order to begin a Searchspring-led implementation or ProServ project, whether that be as a new customer, for a redesign, a re-platform, or adding features or functions, you must have a finalized design.
You must provide a URL to a finalized, production-ready product listing page (category/collection or search results page) on a dev/staging environment, preview theme or live/production site. This is what the Searchspring team will match during the implementation. Searchspring cannot accept PDF, PSD, Adobe XD, Figma, InVision or other prototype, mockup or wireframe formats. The design needs to be fully coded out by your team on a dev/staging instance or preview theme of the e-commerce platform Searchspring is to be integrated on.
Searchspring expects these items to already exist, and be functional, on the provided product listing page before we begin the implementation if you plan to have them on your site:
- Filters navigation*
- Sorts*
- Badges
- Various price displays (standard, strikethrough, from $X, etc.)
- Quick Add
- Quick View
- Add-To-Cart
- Wishlist / Favorites
- Compare
- Ratings & Reviews
- Hover Over Thumbnail Swap
- Color Swatches
- Fabric Swatches
- Size Swatches
- Pagination, Load More, or Infinite Scroll
*Searchspring does have a default design for filters and sorts, so if these two features are not built/functional on the dev/staging instance or preview theme we are matching, you can opt to use our default design. We will match your site's overall styling and fonts, but adjustments beyond that are very limited.
There should be no plans to make any changes to the dev/staging instance or preview theme we are matching during the Searchspring requirements gathering and implementation process.
Please note, if any changes are made during the implementation process that impact Searchspring, it will delay the project timeline and additional fees may apply.
Comments
0 comments
Article is closed for comments.