HomeGuides › Heimish business web

Heimish business web

Running an online store that closes for Shabbos and Yom Tov

Why a fixed Friday 5pm cutoff is wrong most of the year, and how a frum store closes properly: real zmanim, Yom Tov, delivery dates, and automated emails.

By BH Web Solutions · Updated 2026-07-29

A store on Main Street locks its door before Shabbos and everyone understands. A store on the internet has no door. It sits there taking money at 11 p.m. Friday night unless somebody built it to stop — and building it to stop properly is harder than it sounds, because the moment it has to stop moves every single week.

This is not a business-hours question

Most e-commerce platforms treat closing as a scheduling preference: you're on vacation, you're short-staffed. For a frum business it is three problems wearing one coat.

The halacha. Whether a Jewish-owned website may take orders and charge cards automatically on Shabbos is a real shailah, not a settled matter. Poskim discuss it under several headings — mekach umemkar (commerce on Shabbos), s'char Shabbos (taking payment for Shabbos itself), and how it looks to someone watching. Some are lenient about a site that runs on its own with no Jew doing anything. Others are not. I build websites; I don't pasken. Ask the shailah first, then build to the answer.

The reputation. Your frum customers notice. A kosher grocery whose checkout is cheerfully taking orders at 9 p.m. Friday night gets talked about, and not warmly. The reverse is underrated: a clear closed notice is a trust signal that quietly tells a heimish customer you are one of them.

The operations. Between roughly 52 Shabbosos and 13 days of Yom Tov in the diaspora, a frum business is closed on the order of 60-odd days a year — fewer when a Yom Tov falls on Shabbos and the two overlap. That's about one day in six. An order placed Friday and shipped Monday is fine. An order placed Friday with no acknowledgment until Monday is how you get a chargeback.

Three ways to close, and what each costs you

ApproachBest forThe catch
Keep taking orders, process later Non-food retail where the rav is comfortable Requires a psak. Confirmation emails must be held, not sent.
Take the order, hold the money — card authorized, charged Sunday Stores that want the sale but no money moving Authorizations expire, commonly around seven days with major processors. Banks often show the hold as a pending charge, which confuses people.
Disable checkout, keep the store visible Most businesses. The default I recommend. The cart must survive until motzei Shabbos or you lose the sale.
Replace the site with a closed page Almost nobody Damages search visibility and turns away browsers who would have returned.

Catalog up, checkout off is right for most stores because it costs nothing. Someone researching a stroller Friday night still reads the product page, adds to the cart, and buys Saturday night when the button returns.

Getting the time right, which is the hard part

Shabbos moves every week

Shabbos begins at sunset, and the custom in most American communities is to light candles 18 minutes before. Sunset in New York on a Friday in late December is around 4:30 p.m.; in late June it's around 8:30 p.m. Candle lighting in Brooklyn therefore runs from roughly 4:10 p.m. in December to a little past 8:10 p.m. in late June — a four-hour swing, shifting a minute or two every week.

That's why "close Fridays at 5 p.m." is wrong most of the year. From late November through late January the store is open past candle lighting. From March through October it's shut for hours it could have been selling. The first failure costs more than money.

Motzei Shabbos moves too, and minhagim differ

Shabbos ends at nightfall, and here there's genuine variation: 42 minutes after sunset, 50, 60, or 72 (Rabbeinu Tam), and some communities reckon by how far the sun has dropped below the horizon rather than by fixed minutes. Fifty is widespread in America. Use what your rav uses, and when unsure pick the later one — reopening ten minutes late costs nothing, ten minutes early is a problem. In winter, when Shabbos ends before 5:30 p.m. and nobody is at the warehouse, many stores don't reopen Saturday night at all. They reopen Sunday morning. That's fine; just say so on the site.

Location, time zones, and two traps

Zmanim — the halachic times of day — depend on latitude and longitude. Brooklyn, Monsey and Lakewood differ by a minute or two, which rarely matters. Brooklyn and Los Angeles differ by three hours, which matters enormously. The rule: the store closes on the business's local time, not the customer's. A California shopper at 5 p.m. their time finds your New York store closed, and that's correct.

Two traps. Most web servers run on UTC; if the closing logic uses server time with a hard-coded offset, it will be exactly one hour wrong for half of every year when daylight saving shifts. Compute in a named zone like America/New_York instead, which handles the change automatically. Second, Israel's daylight saving dates differ from America's, so if you deal with an Israeli printer or supplier, the gap isn't always the usual seven hours.

Where the times come from

You don't guess these. Candle lighting is computed from the sun's position for your exact coordinates, then adjusted by your community's offset. Two mature, free sources: Hebcal publishes a Jewish calendar and Shabbos-times service a website can query automatically, and the KosherJava zmanim library (with a JavaScript port) implements the astronomical calculations along with the various shitos for nightfall.

The alternative — pasting a year of dates into the site — works beautifully for eleven months and then silently fails. I've seen it more than once: a hard-coded holiday list quietly stops closing the following year, and nobody notices until a customer mentions it. The calendar must be computed, not typed.

Yom Tov is multi-day, and depends where you are

Yom TovClosure days — diasporaClosure days — Israel
Rosh Hashanah22
Yom Kippur11
Sukkos (first days)21
Shemini Atzeres / Simchas Torah21
Pesach (first and last days)2 + 21 + 1
Shavuos21
Total138

Now stack Shabbos on top. When Yom Tov falls Thursday and Friday it runs straight into Shabbos and the store is shut three consecutive days — roughly 72 hours with no orders, no phones, no shipping. The same happens when it falls Sunday and Monday. These are the biggest operational events in a frum retailer's year, and each one needs an order deadline announced in advance.

Chol HaMoed

The intermediate days of Pesach and Sukkos — four and five days respectively in the diaspora — are their own category. Melacha is restricted but not forbidden outright, and the leniencies (davar ha'aved, an unrecoverable loss, and tzorchei hamoed, needs of the festival) are case-by-case. Some businesses run normally, some reduce hours, some close. That's a shailah for your rav. The site just needs to express whichever answer you get, set separately for Pesach and Sukkos — in practice, a checkbox in your admin area.

Erev Pesach, for food stores

This one gets missed. If you sell chometz and do a mechiras chometz, the store must not be selling chometz from the deadline on erev Pesach until after the chag. An automated store still taking orders for bread flour during Pesach is a real problem, not a cosmetic one. The build is simple — tag every chometz SKU once, then an automatic hide-and-block window driven by the same calendar as everything else. Work the exact times out with the rav handling your mechira; the deadline is earlier in the day than people assume.

What the customer should see

Angry customers are almost always surprised customers. Nobody is upset that you close for Shabbos. They're upset that they paid Friday night, heard nothing for two days, and started wondering whether the site is a scam. A small sitewide countdown starting a few hours before closing does most of the work — not a popup:

Closing for Shabbos in 1 hour 40 minutes. Orders placed after 3:40 p.m. today will be packed Sunday morning.

Then a closed banner with a real reopening time generated from the same calendar, rather than a vague "back soon": We're closed for Shabbos. You're welcome to browse and add to your cart; checkout reopens Sunday at 8:00 a.m. Anything in your cart will still be there.

Finally, a permanent explanation on your shipping or FAQ page, worded for a customer who isn't Jewish — you'll have some, and confusing them helps nobody:

We're a family business and we close for the Jewish Sabbath, from sundown Friday to nightfall Saturday, and for Jewish holidays. Orders placed during those times are processed the next business day. Sabbath times change weekly, so the exact hours vary through the year.

One detail matters more than it should: if a customer is halfway through checkout when the cutoff hits, don't throw them out with an error. Keep the cart, explain, and offer to email them when checkout reopens.

The messages that fire while you're not looking

You close the checkout, feel finished, and at 10:40 p.m. Friday night your abandoned-cart reminder goes out to four hundred people. Everything below runs on a timer and will run on Shabbos unless you stop it:

  • Abandoned-cart sequences, which fire a fixed number of hours after a cart is left — often 1, 24 and 72. A Thursday-afternoon cart triggers the 72-hour message squarely on Shabbos.
  • Order confirmations and shipping notices, triggered instantly if you're still taking orders.
  • Review requests, sent a set number of days after delivery, so they land on Shabbos roughly one week in seven.
  • Back-in-stock and price-drop alerts, triggered by inventory changes that don't respect the calendar.
  • Scheduled campaigns and SMS blasts. Someone schedules a 6 p.m. Friday send in July without thinking. In December, 6 p.m. Friday is well into Shabbos.
  • Paid ad schedules and live chat widgets. Friday-night ads to a store that can't take the order are money on the floor.

Most email and SMS platforms offer quiet hours, but almost always as a fixed daily window like 9 p.m. to 8 a.m. — which does not track candle lighting, and that's the whole problem. Either suppress sends through a Shabbos window your own system calculates, or, more simply, schedule nothing on Fridays and set every automated sequence to send Sunday through Thursday only. Cruder, far more robust.

Separately: US telemarketing rules under the TCPA restrict marketing calls and texts to 8 a.m. through 9 p.m. in the recipient's local time zone, year-round. If your list spans time zones, both constraints apply. More in the guide on email and SMS marketing law.

Deliveries and shipping

  • Block Shabbos and Yom Tov in the date picker, grayed out with a reason shown. A customer who picks Saturday and finds out later is a customer you've lost.
  • End Friday delivery windows hours early, not at candle lighting — a driver needs to finish, get back and get home. For a December Friday with 4:10 p.m. candle lighting, the last realistic slot is early afternoon and the cutoff is probably Thursday night.
  • Watch Saturday carrier delivery. UPS, FedEx and USPS all deliver Saturdays in many areas. Frozen meat shipped Thursday for Saturday arrival sits on a porch a full day — a spoilage claim, and the replacement shipping is yours.
  • Publish a shipping calendar before every Yom Tov. "Last day to order for delivery before Pesach: Tuesday." One sentence, on the homepage, three weeks out.

Delivery-day rules interact closely with zone rules; if you're setting up both, see kosher grocery delivery zones.

The erev Yom Tov surge

For a heimish food business the year isn't flat — it's a handful of enormous spikes on known dates, so there's no excuse for being unprepared. What goes wrong, roughly in order: the site slows or falls over under traffic it never sees otherwise, at the exact hour customers will simply call someone else (worth reading about site speed for online stores before erev Pesach, not during it). Stock counts drift because the counter and the website sell the same items. The cutoff is unclear, so orders keep arriving after you can fill them. And the closure lands mid-surge: erev Yom Tov often is the closing moment, so your busiest hour ends abruptly at candle lighting. Set the checkout cutoff earlier than usual that day — the kitchen needs a runway.

Two things help: a homepage countdown for the two weeks before a major Yom Tov ("Pesach orders close Tuesday 8 p.m."), and a pre-order window opening well in advance so some demand shifts off the peak. Caterers can move a lot of load this way.

Edge cases worth handling once

  • An owner override. You'll need to close for a levaya, a snowstorm, or the day the freezer died. One switch, plain language, no developer.
  • A preview mode, so you can check the closed wording on a Tuesday without closing the store for everyone. Admin access should never be locked out by the storefront closing.
  • A buffer. Close 20 to 40 minutes before candle lighting, not at it. Clock drift and a customer who started checkout two minutes early both argue for margin.
  • Fast days. Tisha B'Av, Taanis Esther and the rest carry no melacha restriction, so most stores stay open. Some close anyway. The system should allow that without code.
  • Contact forms keep arriving. Set the auto-reply to say when you'll actually respond — "we're closed for Shabbos, we'll reply Sunday" — not "shortly."

What this costs

Less than people expect if it's built with the store, more than it should be if it's bolted on two years later. A manually flipped banner is an hour or two. The full automated setup — zmanim-driven cutoffs, checkout lock, cart preservation, blocked delivery dates, Yom Tov calendar, message suppression, owner override — is typically one to three days depending on the platform. As a rough order of magnitude, a few hundred dollars up to around $1,500 for most small stores. Ranges, not quotes.

Worth knowing: off-the-shelf store-hours plugins — small add-on programs that extend a store's features — almost all assume fixed weekly opening hours, which is precisely the wrong shape here. What's needed is a small piece of custom logic plus a proper Jewish-calendar data source. It isn't a big job; it just isn't the job those plugins do, which is why so many frum stores end up with a banner somebody flips by hand and forgets. If you'd like it built in properly, that's work we take on.

The short version

  • Ask your rav what the store may do on Shabbos, then build to that answer. The technology is the easy part.
  • Never use a fixed Friday cutoff. Candle lighting in New York swings from about 4:10 p.m. to past 8:10 p.m. across the year; compute it from real zmanim data for your location, in your local time zone.
  • Keep the catalog visible and switch off only checkout. Show a real reopening time and keep the cart intact.
  • Yom Tov is 13 closure days a year in the diaspora, sometimes three consecutive with Shabbos. Handle Chol HaMoed and erev Pesach chometz deliberately.
  • Suppress abandoned-cart emails, review requests and SMS blasts — a fixed "quiet hours" setting won't track candle lighting.
  • Block Shabbos and Yom Tov in the delivery date picker, end Friday windows hours early, and publish an order deadline before every Yom Tov.

Want this handled properly?

We build websites and online stores for businesses that need them to actually work — in English and Yiddish. Tell us what you're trying to do and we'll tell you straight what it takes.