How It Works

Exactly what happens
between close
and open.

Whether you're a restaurant owner locking the door at 10pm or an e-commerce brand winding down for the night, the same gap exists: your ordering system or store keeps running, and nobody's watching it. We designed this process so you know exactly what we do during that window — before your first night of coverage, not after your first incident.

Most overnight failures on Shopify, WooCommerce, Toast, and Square come from the same short list of causes. We've built platform-specific triage playbooks for each one. When your checkout breaks at midnight we're not starting from scratch — we're running a diagnostic we've run before.

Intake Call✦Platform-Specific Setup✦Coverage Starts✦Overnight Triage✦Escalation with Context✦Morning Report✦Restaurants & E-Commerce✦You Wake Up Knowing✦ Intake Call✦Platform-Specific Setup✦Coverage Starts✦Overnight Triage✦Escalation with Context✦Morning Report✦Restaurants & E-Commerce✦You Wake Up Knowing✦
What's true every night

Three things that hold
for every client,
every night.

These aren't marketing commitments. They're operational ones. If we can't deliver on one for your specific situation — your platform, your volume, your setup — we'll tell you during the intake call before you've paid anything.

01 Transparency

You know what happened overnight every single morning.

The morning report goes out before 8am, every day, without exception. Green night — one line. Something happened — full incident timeline, what we found, what we did, current status. Whether you opened a restaurant at 7am or logged into your Shopify dashboard — you start informed, not discovering.

Before 8am local time · Every morning · Green or incident — always reported

02 Scope clarity

You know what we fix and what we escalate before we start.

During onboarding we build a triage playbook specific to your platform — Toast, Square, Shopify, WooCommerce — and approve it with you before the first night. What we fix directly, what routes to escalation, who gets called and when. No ambiguity at 2am.

Playbook built during onboarding · Reviewed with you · Approved before coverage starts

03 Real response

A person responds to alerts — not a ticket queue, not an auto-acknowledgment.

When an alert fires during your overnight window, a human being assesses it and takes action within 15 minutes. Not a system response. Not an email reviewed at 8am. Someone working, on it, during the hours your restaurant is dark or your store is between peaks.

15-minute response target · Overnight window set to your schedule

Payment system in a restaurant — the transaction flow Meridian monitors overnight
Every transaction runs through systems we watch overnight
Response target
Under 15 minutes
Why payment systems specifically

Payment failures are the
most expensive overnight
failure mode.

For a restaurant, a payment gateway error at 11pm costs every order that can't complete until morning. For an e-commerce brand doing $15K/week, a broken Stripe integration running 6 hours overnight is a $500+ revenue event — before you factor in the customers who don't come back.

Payment failures have a short diagnostic list: gateway configuration changes from a platform update, SSL mismatches, third-party authentication timeouts, API credential rotation. We know the list. The difference between catching it at 11:15pm and at 7:30am is almost always the difference between a 20-minute fix and a 6-hour loss.

The insider note on payment gateways Stripe, Square Payments, Toast Payments, and Shopify Payments all rotate credentials and push configuration updates periodically — and not always during business hours. When a credential rotation causes a payment failure overnight, the fix is usually quick once you know that's the cause. The delay is always in finding out what actually broke. That's our job.
A typical incident night

What actually happens
between 11pm and 7am.

Most nights nothing fires. Those nights still produce a morning report — one line confirming coverage held. When something does happen, here's the exact sequence. This example is a Shopify payment failure, but the structure is identical for Toast, Square, and WooCommerce incidents.

10:00 PM

Coverage window opens

Your overnight window begins. Monitoring is active across all configured URLs — homepage, ordering page, checkout flow, payment step. Your team is offline. We're on.

11:22 PM

Checkout flow monitor fires

Our functional checkout check fails at the payment step. The ordering page loads fine — standard uptime tools show the site as "up." We open an incident log immediately. A restaurant owner and a Shopify store operator would both find out at 8am without this.

11:26 PM

Triage begins against your platform playbook

We run the diagnostic built for your specific platform during onboarding. Check payment gateway status. Review error logs. Identify the last integration update. For Shopify: review app event history and gateway configuration. For Toast: check the partner integration log.

11:34 PM

Cause identified — gateway configuration conflict

A payment integration pushed a configuration update that conflicted with current gateway credentials. Known failure mode, documented fix. We apply it directly using the access established during onboarding.

11:41 PM

Checkout confirmed working — monitoring stable

Functional checkout check passes. Test transaction confirms the payment step is working. Monitoring stable. Incident log updated. You are not woken up. Total downtime: 19 minutes.

7:00 AM

Morning report delivered before your day starts

Incident at 11:22pm. Payment gateway configuration conflict. Fix applied at 11:41pm. Ordering confirmed stable since. Total downtime: 19 minutes. No action required — but here's everything that happened while you were asleep.

Triage protocol

What we fix directly.
What we escalate — and how.

Before coverage starts you receive a documented triage scope for your specific platform. Below is the general framework. Onboarding adds the restaurant- or store-specific layer on top.

We resolve directly

These we fix while you sleep.

Most overnight ordering and checkout failures have known causes and documented fixes across all four platforms we cover. We apply them and confirm resolution before the morning report goes out.

  • Plugin or app conflicts causing checkout failures or broken pages
  • SSL certificate errors and renewal failures
  • Payment gateway configuration conflicts from overnight updates
  • Third-party script failures blocking the ordering or checkout flow
  • Redirect loops and broken redirect chains
  • Performance crashes from resource spikes with a safe rollback path
  • Menu and ordering page failures from update conflicts
  • Toast, Square, Shopify, and WooCommerce app integration conflicts with known resolution steps
The fix vs. escalate boundary It's never about difficulty — it's about authorization. Anything requiring a business decision, database access, or changes beyond what we established during onboarding routes to escalation immediately. Speed matters less than doing the right thing.

We escalate — with full context

These we hand off properly.

When something exceeds our direct scope, we escalate immediately — but not blindly. Your developer or tech contact receives a brief, not a forwarded alert with a question mark. They start from a diagnosis, not from scratch.

  • Issues requiring direct code-level changes or database access
  • Security incidents requiring owner decision and containment
  • Server infrastructure failures outside our access level
  • Platform outages (Toast, Square, Shopify, WooCommerce hosts) where the fix is external
  • Business decisions embedded in the technical resolution
  • Payment disputes or fraud patterns requiring merchant action
  • Data integrity issues affecting orders, inventory, or customer records
What a Meridian escalation actually looks like When we escalate we've already triaged. Your developer receives: what triggered the alert, at what time, what we checked, what we tried, what we found, and the most likely fix path. For restaurant clients that's often their Toast rep or web developer. For e-commerce brands it's often their Shopify developer or agency. Either way — they walk in with a briefing.
Your specific path

Onboarding through coverage —
plan by plan.

Both plans follow the same onboarding sequence. The difference is the depth of the triage playbook and the platform-specific monitoring we configure for your ordering system or store.

Meridian
Watch

Overnight uptime coverage for restaurants and online businesses. Monitoring, triage, escalation, and morning reports — every night during the hours your team isn't working.

From $400 / month

$13 a day

Onboarding: 3–5 business days · Then ongoing

Get started →
Step 01Intake call30 minutes

We walk through your site, your platform (restaurant ordering or e-commerce), your current monitoring setup, and your escalation preferences. You leave knowing exactly what we'll cover and what we won't. No prep needed — just access to your site admin.

Site reviewPlatform documentationEscalation preferences
Step 02Monitoring configurationDays 1–3

We configure monitoring across your key URLs, route alerts to our overnight system, and build your triage playbook. If you have existing monitoring, we connect to it. If not, we set it up. Every alert path is confirmed active before coverage begins.

URL monitoringAlert routingTriage playbook build
Step 03Your review + coverage confirmationDays 4–5

We walk you through the monitoring setup and your triage playbook before the first night. You confirm everything looks right. The first morning report goes out on day one — even if the night is perfectly quiet — so you know exactly what to expect going forward.

Playbook reviewFirst morning reportCoverage confirmed
OngoingNightly coverage + monthly summaryEvery night

Coverage runs every night during your window. Morning reports go out every morning. End of month you receive a full summary: uptime percentage, incidents logged, response times, resolutions applied. Your documentation — not just our memory.

Nightly coverageDaily morning reportMonthly summary

Meridian
Commerce

Everything in Watch, plus functional checkout flow monitoring that catches the failures standard uptime tools miss entirely. Built for restaurants and e-commerce brands where downtime is measured in lost revenue, not just inconvenience.

From $600 / month

Under $20 a day

Onboarding: 3–5 business days · Then ongoing

Get started →
Step 01Extended intake — platform specific45 minutes

We go deeper: your ordering or e-commerce platform, every app and integration, your payment gateway stack, and your incident history. Especially useful: have you ever woken up to lower orders or sales than expected without knowing why? That's almost always a silent overnight checkout failure — exactly what Commerce catches.

Platform reviewApp auditPayment gateway configIncident history
Step 02Full monitoring configurationDays 1–3

Standard uptime monitoring plus functional checkout flow monitoring — synthetic checks that move through your actual ordering or purchase process the way a real customer would. We configure payment gateway health checks, menu or product availability checks, and cart completion monitoring separately from basic URL uptime.

Checkout flow monitoringPayment gateway checksRevenue triage logic
Step 03Platform-specific triage playbookDays 2–4

We build a triage playbook for your exact stack. Shopify fails differently than WooCommerce fails differently than Toast. Your playbook reflects your specific platform, your apps, and your most likely failure modes based on what we learn during onboarding — not a generic template applied to everyone.

Platform-specific playbookApp conflict matrixClient review + approval
Step 04Coverage confirmationDay 5

We walk through the full monitoring setup before the first night. You see exactly what's being watched, how alerts route, and what the escalation chain looks like. First morning report on day one so you know before you go to sleep that night exactly what's watching your revenue.

Walkthrough callFirst report previewCoverage confirmed
OngoingNightly coverage + monthly revenue summaryEvery night

Coverage runs nightly. Morning reports go out every morning. Monthly summary includes standard Watch metrics plus checkout uptime percentage, ordering or purchase flow incident log, payment gateway events, and app conflicts detected. Revenue-specific context for Commerce incidents.

Nightly checkout coverageDaily morning reportMonthly revenue summary
Process questions

Things people need
to know before
they start.

The intake call covers everything specific to your setup. These are the questions that come up before the call.

What access do you need to our systems?+

For monitoring only — none. We monitor from the outside. For first-response fix capability we need limited administrative access scoped to where common failures occur. We always operate on least-privilege: never more access than the triage scope requires. For Shopify stores: a Staff account with specific app and theme permissions. For WooCommerce: a limited Admin role. For Toast: read access to your ordering configuration. All access is cleanly revoked at offboarding with a confirmation log.

How will I receive the morning report?+

Via email, delivered before 8am your local time. If you prefer Slack, we can route it there. Format is the same regardless: overall status first, then the detail. Green nights take under a minute to read. Incident nights are complete but concise — what broke, when, what we did, current status. You start your day knowing, not investigating.

What does "15-minute response target" mean exactly?+

It's the time between alert receipt and active triage beginning — not time-to-resolution. Resolution depends on what broke. Most common fixes take 10–30 minutes once we've identified the cause. The 15-minute target is about not leaving an alert sitting in a queue. In practice most alerts are opened within 5 minutes during covered hours.

Can you cover multiple restaurant locations or multiple Shopify stores?+

Yes. We configure monitoring and triage playbooks per location or per store, route morning reports as you prefer — consolidated or per-site — and handle escalation according to the contact hierarchy you set. Multi-site pricing is scoped during the intake call based on site count, platform, and risk profile. One conversation, clear number.

What happens when we cancel?+

30 days notice. During that window we maintain full coverage and prepare a proper handoff: monitoring configurations documented for your team, the triage playbook formatted for internal use, incident history exported, all access cleanly revoked with a log. You leave with everything we built for your restaurant or store — nothing disappears with us.

Ready to start

You now know more about overnight
coverage than most restaurant owners
and store operators ever will.

Which means you can make a clear decision about whether Meridian fits your business. If it does — or if the intake call would help you decide — start the conversation. 30 minutes, no pitch.

→ Start the conversation Review the plans first →

No long-term contract · Onboarding in under a week · Month-to-month