Countdown Clock to close the store

If there a way to code the clock so when it reaches 00 00 00 00 that it closes the store in some way. This could be turning all of the stock to ‘Out of Stock’ or even stopping people checking out?

I want to open the store for limited times and then shut for a time for me to sort orders then i will reopen with a countdown reset.

Any ideas?

1 Like

You can’t do that so to speak currently, however there are a few suggestions here.
https://support.wix.com/en/article/request-vacation-mode-in-wix-stores

You can also look at scheduling recurring jobs for when you want to do a stocktake.
https://support.wix.com/en/article/corvid-scheduling-recurring-jobs

Build your pages in a wixRouter. Then whenever a person attempts to visit the site when it’s closed you route them to a store is closed page. Whenever the store is open you route them to the store. You can decide when and how to start the timer when the page loads. Perhaps you want it on every page so it goes in the header and updated using site page code, alternatively you only load it on specific pages.

The timer can be derived from a data collection that you can manipulate from a dashboard page to close and open the store.

Thanks for that great suggestion Steve.

Just a shame that Wix Stores haven’t implemented that option or something similar to it already though.

Maybe Josh would like to put in a feature request for it here.
https://www.wix.com/corvid/forum/community-feature-request

Here is a Countdown Example that you can use. When the countdown is done you can then close up shop.

Thank you both. I have also requested the feature as you have suggested.

https://www.wix.com/corvid/forum/community-feature-request/countdown-clock-to-open-close-your-store

Question to Steven:

Do you have and links that show examples of WixRouter? I have done simple coding but never into a Data Collection, Do you have any examples of the two integrating?

This example does some router stuff:

Stripe Payment Processing

Integrate the Stripe Payment processing system into a site. Three levels of user access are demonstrated: visitor, freemium (registered), and premium (paid).

Basically it routes baesd on login permissions, but it’ll give you an idea at least.

Josh: If you combine the ideas in Yisrael’s posts you should be able to cobble something together. If you need bespoke help drop me a note in the chat or check my profile. Cheers