The question sounds so small that most owners are embarrassed to ask it. I run this store by myself. I would like to go away for a week. What do I press?
Etsy sellers press Vacation Mode. eBay sellers press Time Away. Shopify owners open the help center and read the first sentence of the official page on the subject: although Shopify doesn't have a vacation setting. What follows are two workarounds, and both of them answer a different question than the one you asked. You wanted to stop working for a week. Shopify offers you two ways to stop selling.
The setting that does not exist
Option one is password protection. Flip it on and your entire site disappears behind a login page: no products, no pages, no blog, no browsing. A shopper who finds you on Google lands on a locked door. Your subscription keeps billing at full price while nobody can see the store. And the door is locked to more than shoppers: one merchant noted in a June 2025 thread that password protecting the store would lose all the work put into Google Merchant listings, because the crawler hits the same wall the customers do.
Option two is the Pause and Build plan, nine dollars a month, and it is built for a sabbatical, not a vacation. The storefront stays browsable, but the plan deactivates the checkout, the POS channel, discounts, gift cards, abandoned checkout recovery, and publishing your products to third party channels. Apps with recurring charges keep charging. When you come back, you cannot simply resume: your old plan is no longer valid, and you must select a new one, which starts a new billing cycle. And there is a catch that turned the whole feature from awkward to unusable for short breaks: the switch to Pause and Build may be scheduled to take effect at the end of your current billing cycle, not when you actually need it.
The community record
The feature request is old enough to vote. In July 2022 a merchant posted the spec in three bullet points: a popup telling shoppers that orders will be delayed until a certain date, an option to turn off the checkout, and a holiday mode order confirmation that reconfirms the delay if someone buys anyway. Shopify staff replied warmly, and pointed the merchant to Pause and Build plus the password page. Which is to say: to close.
Then the workaround itself broke. In September 2024 a merchant who had quietly used Pause and Build as a vacation mode for a year reported that the behaviour had changed: instead of switching immediately and crediting the difference, Shopify now insisted on running out the current term first. He was on an annual plan. His pause would take effect in July 2025, ten months after he asked for it. Support told him this is how it works now. His closing line named the benchmark: even eBay has an excellent vacation mode.
The replies stacked up the way these threads always do. December 2024: a merchant gave up and removed the buy button from product pages by hand, calling it ridiculous that there's no holiday mode built in. January 2025: this is a DISASTER. February 2025: how are we supposed to plan a pause a month or even a year in advance? June 2025: a merchant with a broken machine, unable to fulfill anything, was told the pause would start on the 20th, and that resuming would take a further full month. And in the same thread, the sentence that explains the whole problem better than any feature request: I'm quite happy to keep paying the full monthly price, I just want to stop selling so I can go on holiday. The whole point of Shopify was to be my own boss, and I'm still being dictated to by companies.
The record runs right up to this month. On August 7, 2026, a one person business selling handcrafted jewelry posted a request for a vacation mode that preserves browsing and blocks purchases, calling Pause and Build a nightmare for a one week pause because it is tied to the billing cycle and not my vacation week. The replies were the full workaround economy in miniature: a link to the app store, an offer of custom code, a forty line theme hack that hides the buy buttons behind a true or false switch in the code editor, and a nine dollar a month app pitch. The thread was still active on August 22. So were two others: why is it so hard to set vacation mode for my online store, and how can I set a vacation notice, 2,229 views and counting.
Every workaround answers the wrong question
Line up the options and notice what they have in common.
Password page: no sales for a week. Pause and Build: no
sales for a week, plus a billing puzzle. Theme hack that
hides the buy buttons: no sales for a week, plus editing
code in theme.liquid the night before your
flight and remembering to un-edit it after. Vacation mode
apps: no sales for a week, as a subscription. Every tool
in the drawer implements the same policy, close the till,
and differs only in how much collateral damage it does to
your SEO, your ad accounts, and your Google Merchant feed
on the way down.
That policy is borrowed from marketplaces, and it does not transfer. Etsy's vacation mode pauses your listings inside someone else's mall; the mall stays open and shoppers come back tomorrow. Your Shopify store is not a stall in a mall. It is the whole shop, with its own search rankings built over years, its own ad campaigns mid-flight, its own email list warm from last month's drop. Turning it off for nine days does not pause that momentum, it spends it. And the arithmetic is not subtle: a store doing even thirty orders a week is burning real revenue to buy something that is not actually rest, because the owner spends the week checking a dead storefront anyway, wondering what the closure is costing.
The question was never how do I stop selling. It is how do I stop working while the store keeps selling.
Ask it that way and the shape of the answer changes completely. Orders can arrive while you are on a beach; they just cannot ship. Shipping a week late is a solved problem in commerce, it is called a preorder, a backorder, a made-to-order window, and customers accept it happily on one condition: they were told before they paid. What actually breaks during an unattended week is not fulfillment. It is the promise machine around it. The banner nobody put up. The confirmation email that promises two day dispatch nobody edited. The where is my order emails compounding unanswered for nine days. The one genuine emergency, buried in them, that needed you on day two.
What the automation actually has to do
As a Dugong playbook, in plain prose:
# trigger
On your away dates, start to
end, plus a daily sweep while
the break is running
# steps
1. Write the away policy:
dates, ship-by promise,
what waits, what can't
2. Dress the store: banner,
product pages, and the
confirmation carry the date
3. Stamp every order: tag it,
note the promise, queue it
for the return
4. Answer the inbox: routine
mail gets the date, the
rest gets escalated
5. Watch for fires: card
testing, chargeback clocks,
stockouts, one daily digest
6. Reopen in order: notice
down, queue oldest first,
ships-today emails out
7. Report the week: orders
taken, tickets answered,
sales a closed store loses
Step two is the July 2022 feature request, finally built, and built to a calendar. On your departure date the storefront notice goes up with the return date in it, the product pages say ordering stays open and shipping resumes on the 2nd, and the order confirmation gains a paragraph making the same promise, so nobody learns about the delay after paying. On your return date all of it comes down by itself. That last clause matters more than it looks: half the vacation banners on the internet are stale because taking them down depended on a human's first jetlagged morning back.
Step three keeps the week from becoming an archaeology project. Every order placed during the break is tagged, annotated with the promise it was sold under, and queued. If an order needs payment capture before an authorization expires, that fires on time, the discipline that runs the unpaid order that never cancels itself. Step four is the inbox. Most of what arrives during an away week is one question wearing different clothes, when will my order ship, and it has a true answer, the date you published. The automation sends it, politely, per order, with the real order details. What it does not recognize, a refund demand, a legal threat, a supplier email, gets forwarded to you, which is a far shorter list than everything.
Step five is why you can actually turn the phone off. Some things cannot wait nine days, and they are enumerable: a card testing attack flooding the checkout, a chargeback whose response deadline lands mid-break, a high-risk order big enough to hurt, a bestseller selling out, a site outage. The watcher checks for exactly these, sends one short digest a day that says all quiet, and pings you immediately for the two or three events per year that genuinely need a human on a beach to care. Everything else waits, because you decided in step one that it can.
Step six is the reopening, which manual vacations always fumble. The notice comes down at 8am, the queue is sorted oldest first with the promises attached, and every waiting customer gets a note that their order ships today, which converts a week of silence into a kept promise. The honest limits, stated plainly: nothing packs boxes, so the ship-by date must be one your hands can keep when you return. A fully sold out product with no buffer may still deserve a real pause, and the playbook can hide the buy button for that one product instead of the whole store. And the policy is yours to write: whether your customers will happily wait nine days is a judgment about your products, not a setting a tool should guess.
Why this is a compiler problem, not an app problem
The app store answers to vacation mode all do the same thing because they can only do one thing: block the checkout between two dates. But the away policy is not one switch, it is a paragraph, and the paragraph is different for every store. A print shop wants orders open and a two week window. A perishables seller wants the subscription boxes paused but the pantry items selling. A jeweler wants everything open except the made-to-order pieces. One store wants grandma's birthday order escalated if the note mentions a date before the return. Those are sentences about your shop, and they should compile into the automation as written, the same principle that runs every automation worth building. A checkout blocker cannot hold your paragraph. A compiler can.
Run the week again with the sentences compiled. You leave on the 24th. The banner is already up, the confirmation already promises dispatch from the 2nd. Forty one orders arrive while you are gone; every one is tagged, queued, and confirmed with the date. Nineteen customers email; seventeen get the date within minutes, two get forwarded to you, and only one needed anything. The Wednesday digest says all quiet. On the 2nd the banner comes down, the queue prints oldest first, and forty one ships-today emails go out before lunch. Revenue lost to the vacation: nothing. Times you checked the admin from the beach: fewer than you would admit to last year.
The workflow worth building this week
Start with the promise, not the tools. Look at your products and decide what a customer will cheerfully accept: orders ship from the date you return, plus your normal handling time. If some products cannot promise that, made to order, perishable, wedding-dated, list them; they get the buy button hidden, not the store. Write the away note in your own voice once: we are away until the 2nd, ordering stays open, everything ships when we are back. That note is about to appear in four places, and it should not sound like a plugin wrote it.
Then say the brief the way you would hand it to a house-sitter. From the 24th to the 2nd, show my away note on the storefront and product pages and add it to the order confirmation. Tag every order that comes in and queue it for my return. Answer shipping questions with the date, and forward me anything that is not a shipping question. Hide the buy button on the custom pieces only. Ping me only for fraud, chargebacks, a sellout, or the site going down; otherwise one digest a day. On the 2nd, take the note down, sort the queue oldest first, and tell every waiting customer their order ships today. That is the whole paragraph. The compiler turns it into the workflow, and the store finally has the button the help center admits does not exist: yours.
If you are a Shopify merchant with a vacation story, the
trip you cancelled because of the store, the pause that
would not start until the 20th, the banner that stayed up
until November, the inbox is open:
field-notes@dugong.live. We are collecting
case studies for the next issue.