About the service
Extend your plugins without breaking updates
Your shop or website relies on plugins that do almost everything right. We add the missing part — an extra field, a different checkout rule, a custom shipping calculation — through hooks, filters and separate extension code. The vendor’s files stay untouched, so you can keep installing their updates.
-
Audit
What the plugin allows
-
Extension
Behaviour changed via hooks
-
Separate code
Your changes in one place
-
Update test
Checked against new versions
The idea
Change the plugin’s behaviour, not its code
Editing a plugin’s files directly works — until the next update quietly overwrites every change.
Well-built plugins offer hooks and filters for exactly this reason. We use them to change what the plugin does from the outside, so the original can be updated while your additions stay in place.
Business value
Keep the plugin, lose the limits
Replacing a plugin your team knows is expensive and risky. Extending it keeps the familiar admin, the existing data and the vendor’s updates — and adds exactly what was missing. That is usually faster than a rebuild and safer than editing the original.
When an extension is needed
- A plugin does almost what you need
- Updates are skipped because they undo changes
- Earlier edits were made inside plugin files
- Shipping or pricing rules don’t fit your business
What you will get
- An audit of the plugin’s hooks and options
- Extensions in a separate, versioned plugin
- Earlier direct edits moved into safe code
- A tested update path for future versions
Benefits
Why plugin customization with Scaleable
We extend WooCommerce and other popular plugins in our own projects — for net and gross prices, request-only products and custom shipping rules — so we know where their hooks are.
-
Updates stay possible
Vendor files are never edited, so security and feature updates can be installed as soon as they appear.
-
Smallest possible change
We look for an existing option, hook or filter first and write new code only where the plugin offers no way in.
-
Tested before you update
Before a major plugin update, we check your extensions against the new version on staging.
-
Every change documented
Each extension is listed with what it changes and why, so nobody has to guess later which behaviour is custom.
Principles
Extension Principles That Drive Results
-
Never Touch Vendor Files
All changes live in a separate plugin or child code. The original can be replaced by a new version without losing your adjustments.
-
Hooks Before Workarounds
If the plugin offers a hook, filter or setting, we use it. Overriding templates or copying functions is the last resort, not the default.
-
Every Update Is a Test
Major vendor updates are tried on staging with your extensions active before they reach the live site.
The extension isn’t the finish line
We don’t patch and leave. We keep it update-ready.
Plugins release new versions all the time. The developers who wrote your extension test it with each larger update and adjust it when the vendor changes a hook or a template.
Part one
Extension
The missing behaviour added through hooks and separate code, with the original plugin left untouched.
- Review of the plugin’s hooks, filters and settings
- Extension built as its own small plugin
- Documentation of every changed behaviour
Part two
Maintenance
The same extension kept working as the original plugin, WordPress and WooCommerce move on.
- Update tests on staging with your extensions active
- Adjustments when a vendor changes a hook
- Clear advice on when an update is safe to install
Process
Our Extension Workflow
We read the plugin before we change it. An audit shows which hooks and options exist, the plan uses them wherever possible, and every release is tested against the current plugin version first.
-
Audit
Plugin, version and any earlier edits reviewed.
-
Hooks & Options
Every available hook, filter and setting listed.
-
Extension Plan
Which change goes where, written down for your approval.
-
Build
Extension developed as separate code in Git.
-
Update Test
Plugin updated on staging, extension checked again.
-
Release
The extension goes live with notes on what changed.
Collaboration
Small changes, clearly explained
Extensions are often small, but they touch tools your team uses every day. Before we build, we show you what will change on which screen. After release, you get a short note per extension — so your team always knows what is standard and what is custom.
- Changes shown before the build
- A short note per extension
- Standard and custom kept apart