Storemend

Trust · Safety protocol

How I make sure I can't hurt your store

No drama about what could go wrong — just the procedure that makes "wrong" boring. Five steps, every job, no exceptions. For each one: what happens, why it's there, and what you'll actually see on your side.

  1. I work on a copy.

    Your theme is duplicated; I work on the unpublished copy. Your live store doesn't change while I work.

    What happens

    Before any code changes, I duplicate your live theme inside Shopify. Every edit lands on that unpublished copy.

    Why

    A mistake on a copy is a non-event. Your live store keeps selling, untouched, the whole time.

    What you'll see

    A new unpublished theme in Online Store → Themes, named for the job. Your storefront: exactly as before.

  2. You preview first.

    You get a preview link and approve the result before anything is published.

    What happens

    When the work is ready, you get a Shopify preview link to the unpublished copy — your real store, your real products, the fix in place.

    Why

    Nothing ships without your eyes on it. You judge the result on your actual store, not on screenshots or my word.

    What you'll see

    The preview link in our chat thread. Your approval is written down there too — publishing waits for it.

  3. Publishing by agreement.

    Going live is scheduled by agreement with you — a window you choose and confirm.

    What happens

    After you approve the preview, we agree on a publishing window that suits you and your store. That's when the copy goes live — not before.

    Why

    Even an approved change deserves a planned moment to go live — agreed in advance, with both of us able to look at it as it lands.

    What you'll see

    A proposed window in chat — you confirm it or suggest another. The publish lands in your project timeline with a timestamp.

  4. Everything's reversible.

    Every delivery includes a handover note: what changed, where, and how to undo it.

    What happens

    Theme work stays undoable by design. Anything outside themes — settings, apps — is changed with a written note in your project timeline of what changed and how to undo it.

    Why

    You should never be dependent on me to roll something back. The undo path is written down in plain English, for you or any developer after me.

    What you'll see

    The handover note attached to your delivery in the project portal: what changed, where, and the exact steps to reverse it.

  5. Access ends with the job.

    My collaborator access is scoped to the job and removed when we're done.

    What happens

    I work through a Shopify collaborator request — never your password — with only the permissions the job needs. When the project closes, I remove my own access, or you revoke it.

    Why

    Standing access is risk with no benefit. If you hire me again, a fresh request takes a minute.

    What you'll see

    In Settings → Users: the exact permissions while the job runs, and the access gone when it's done. You can revoke it yourself at any moment, one click.

    The full story of how access works is on the collaborator access page.

Why this page exists

This protocol is also the reason the guarantee is affordable: when nothing risky touches your live store, "delivered as proposed or made right" is a promise I can keep without flinching.

Tell me what's broken.

Describe the problem in plain English. The protocol above runs on every job — including yours.

Start the chat

Not sure it fits? Ask in chat — I'll tell you straight if it's not a fit.

The risk, reversed

  • Delivered as proposed, or made right. If work misses the proposal, I fix it free — and refund anything I can't make match.

  • 30-day warranty. Defects in my delivered work, fixed free.

  • A scope-based proposal first. You see exactly what you'll get, and the price, before any work starts.

  • Your live store stays untouched. All work on an unpublished theme copy — you preview and approve before anything goes live.