No. Upvoting is a soft signal of interest that writes only to a separate counter column. Customers still go through the normal WooCommerce checkout to place a real pre-order, and the pre-order count is tracked the same way it always has been. The two signals stay separate so the team can compare loose demand to hard commitment.

Yes. The board accepts anonymous upvotes by default with rate limiting by IP and cookie. If you want stricter signal, you can require login, restrict voting to existing customers, or weight votes from repeat buyers more heavily than first time visitors, all without changing how WooCommerce Pre-Orders runs underneath.

Yes. SleekView reads pre-order configuration from WooCommerce product meta, so any product the team flags for pre-order appears on the board the next time it refreshes. There is no second registration step, no separate data import, and no risk of the board missing a product the storefront has already started promoting.

Cards keep their history with a canceled status pill so the team can see which launches were dropped and why. Upvote totals stay attached, which makes it easier to revisit those decisions later if customer demand keeps coming back for the same product or the same idea on the next planning cycle.

Yes. Stores often add an unreleased card without enabling WooCommerce Pre-Orders on the product yet. Customers can still upvote the card to signal interest, and the team can flip it into a real pre-order on the storefront once the vote count clears a threshold the merchandising team is comfortable with.

Yes. Because votes live in a column on the product meta, any reporting that already reads WooCommerce meta also sees the upvotes. That includes the Pre-Orders admin views, WooCommerce analytics, and any custom dashboards built on the same database, so the team always has a single shared signal across tools.

Yes. SleekView supports per-row visibility, so confidential launches can stay off the public board until the team is ready. Internal staff can still see hidden cards from an admin-only board that uses the same data source, so internal planning and public conversations both happen in the right surface at the right time.

The board uses cached snapshots and rate-limited vote writes, so a spike in traffic during a launch announcement does not pile pressure on the WooCommerce database. Customers can still upvote and place real pre-orders, and the load profile looks similar to a normal storefront sale rather than something the team needs to provision special infrastructure for.