This year every tool that touches a store has grown an AI feature, and some of them want write access to your products, your prices and your customer messages. The risk is rarely the model being stupid. It is a tool with more access than it needs, nobody watching what it did, and no way to undo it. These are the five rules we apply to PixL and would apply to anything else you try.
1. Read-only first
Any tool should be able to show you its value without changing a thing. Connect it with read-only permissions, let it watch for a week or two, and judge what it would have done. If it needs write access to show you anything useful, be suspicious. In Shopify this means a custom app with read scopes only; in WooCommerce, a REST API key set to Read.
2. Approval before action, with a dial
When you do let it act, every action should start as a suggestion you tap to approve. Only after you have watched the suggestions be right for a while should any category of action run on its own, and you should be able to turn that back down in one click. A tool that only offers "fully automatic" or "off" is asking you to trust it before it has earned it.
3. Limits in money, set by you
An action that moves money needs a ceiling. A purchase order over a certain value, a price change over a certain percentage, a refund over a certain amount: these wait for a person regardless of how much you trust the tool. Set the limits in your currency, where you can see them, and review them quarterly.
4. A log you can read
Everything the tool did, when, why, and what it was looking at when it decided. Not a dashboard with a success rate, a plain list. If a customer asks why they got a reply, or a supplier asks why a PO changed, you need the answer in a minute. If the tool cannot show you that, it is not ready for your store.
5. Know where your data goes
Ask three questions and expect plain answers: where is my data stored, who else can see it, and what happens to it if I leave. "Your own workspace, nobody, and it is deleted" is the right shape of answer. Vague answers about the cloud are not. Also ask whether your data is used to improve the tool for other customers, and get the answer in writing.
A sixth, for the tool-makers
If you build these tools, as we do, the sixth rule is: have a person on the account. Models change monthly, connectors break when platforms update their APIs, and a store owner should not be the one who notices. Someone whose job it is to watch the tool, fix what it got wrong and keep it current is the difference between a product and a liability. It is the main reason PixL is sold with a team attached rather than as a login.
None of this is about distrusting AI. It is about giving it the same rules you would give a new hire with access to the bank: start small, watch closely, widen the access as the trust is earned, and keep the receipts.
