A few months back we wrote about Shopify's AI Toolkit and said the quiet part out loud: before you let AI touch your store, make sure someone knows where the fire extinguisher is.

That post was about caution.

This one is the setup guide.

Because "be careful" is not a system.

Keys, backups, and boundaries are a system.

Here is the exact way to hand AI real access to a real store without handing it the matches. 🔥

What you need before AI touches anything

A Shopify store

Obvious, but specific: you need owner-level access to it.

If an agency or an old developer holds the keys, get that sorted first.

You cannot control access you do not own.

Shopify CLI

Shopify's official command line tool.

This is the front door that AI tools like Claude, Cursor, and Codex use to talk to your store.

It matters because it forces the conversation we are about to have: when you connect it, you choose exactly what it is allowed to see and do.

Matrixify

The backup app.

It exports your products, collections, customers, and metafields into spreadsheets you keep.

Think of it as the undo button Shopify never gave you.

The rule that matters more than any tool: scopes

When you connect the CLI or create app credentials, Shopify asks which permissions to grant.

These are called scopes.

Every scope is a door in your store.

So build AI a small scoped space: only the doors the job actually needs, and not one more.

Read access is much safer. Not harmless.

Reading products cannot break products.

So when a job can be done read-only, do it read-only.

But not all reads are equal.

Customer lists, order history, payouts, and banking details are your business walking out the door.

An alt-text job does not need to see your payouts.

If a read scope makes you wince, that is the answer.

Write access is where stores break

Grant as little write access as you possibly can to do the job.

Updating product descriptions? Write access to products. Nothing else.

Not themes.

Not orders.

Not customers.

One job. One scope. ⚠️

Back up whatever you are about to let AI write to

This is the part everyone skips and everyone regrets.

The rule is simple: whatever the job writes to, export it first.

✅ Updating products? Matrixify export of every product first
✅ Touching collections? Export the collections and their rules
✅ Metafields in play? Export those too
✅ Editing the theme? Duplicate it in admin before a single line changes

The export takes minutes.

The rebuild takes weeks.

Choose minutes. 🧯

When the job is done, take the keys back

Access is not a subscription.

When the product update ships, revoke the write scope.

If AI is not actively working in your store, it should not be holding keys to it.

Small access in. Keys back on the hook after.

The whole system in five lines

Scope small.

Back up first.

Run the job.

Verify what changed.

Revoke what is no longer needed.

That is it. That is the difference between merchants who get leverage from AI and merchants who get a rebuild quote.

This is exactly how FireNet Designs runs AI on client stores

Not because we are scared of it.

Because we have seen what happens when nobody sets the boundaries.

We scope the access, take the backups, run the work, and hand back a store that is better than we found it.

Call FireNet Designs before you hand your store keys to something that never sleeps.

We would still rather help you prevent the fire than charge you to rebuild after it.