Change how an add-on behaves when changing its look is not enough

Paid versionModules

You get clear options and their risks, and if editing the add-on is the only way, the change is made with a backup and noted for the next update.

What it replaces: 2-6 h of developer time

What you write to Claude

„i want the free shipping notice only in the cart. if that needs a change inside the module, tell me the options and the update risk before writing anything”

The problem

The free shipping add-on shows its message on every page. We want it only in the cart, and that's in the add-on's code, not its look.

What Claude does

  1. Claude checks whether a change of look or position is enough.
  2. If not, it warns you that the add-on's next update will erase a direct edit, and offers alternatives.
  3. If you choose the direct edit, it shows the exact change, saves it with a backup and notes it for the next update.

What you get

You choose the path knowing the trade-offs. Any direct edit is backed up and recorded.

You stay in control

You see every change before it is saved and nothing happens without your yes. Work on add-ons uses a separate, extra-protected connection, usually set up by whoever looks after your shop, and add-on files are backed up before they change.

See pricing

Related use cases

For developers
Area
4 · Modules
Connector
service connector
In the free Audit
no, paid version only
For
Developer, Agency / freelancer
Tools
ps_list_modules, ps_module_file, ps_override_module_template, ps_manage_hook_positions, ps_module_config, ps_restore_file_backup

Step by step

  1. Finds the module and the hooks it uses (ps_list_modules with hook).
  2. Checks if the result can be reached in block 3: a template override (ps_override_module_template), CSS or a different hook position (ps_manage_hook_positions).
  3. If only the module's code can do it, reads the relevant file with ps_module_file (action read) and explains the options: direct edit, a module setting (ps_module_config) or asking the module author.
  4. On your choice, edits with ps_module_file (action edit): diff preview, PHP syntax check and backup; restorable with ps_restore_file_backup.
  5. Records that the edit will be lost on the next module update.

Safety

Modules (block 4) work only through the service connector (separate token accepted only from allowlisted IP addresses) and are off after installation; the owner gets an e-mail when the block is switched on. Every write shows a preview, runs only after your approval (one-time token) and is logged in the change history. Direct edits to module files are erased by a module update; Claude says so before writing. A template override in the theme (block 3) survives updates and is preferred for changes of look.

Last updated: 2026-10-05