MeshWatch
Know exactly what your ERP update changed
Platform releases arrive on the vendor's schedule, not yours, and something your team has relied on for years quietly stops working. MeshWatch keeps the settings, customizations and scripts behind your ERP, so you can see what moved and go back to the version that worked.
What it does
A history for the part of your ERP nobody documents
Not the data. The settings, customizations and scripts that decide how the data behaves.
- Compare before and after a releaseMark the day the release landed. MeshWatch shows which settings, customizations and scripts are no longer what they were.
- The person who built it left. The history did not.Find out when a setting became what it is now, and the name your ERP recorded against the change, where it recorded one.
- Changes nobody claimedA queue of the changes that arrived without an explanation. Write the note while somebody still remembers why.
Retention
Your ERP forgets. Your archive does not.
The source system keeps very little for very long, which is why last year's answer is usually gone by the time somebody needs it.
What NetSuite remembers
NetSuite clears its own script execution logs after roughly a month, and the notes attached to a record go when the record goes.
About 30 days
What MeshWatch keeps
Settings, customizations and scripts, with the version behind each change, kept in your archive on the Config subscription.
24 months
In practice
It worked in March. What changed?
The incidents that send a team digging through an ERP with nothing to dig through.
A forced release rewrote something.
Compare the account before and after it landed, and see what the platform touched on its way through.
Three parties can change your ERP.
Your own work is documented. The admin, the other consultant and an app update are not. MeshWatch keeps the history for the settings and scripts it covers, whoever made the change.
It worked in March.
Ask what has changed since, instead of guessing which setting moved.
A script stopped behaving.
Open the versions behind it and see what the last change did.
Coverage depends on the ERP and the connector, and history runs from the day you connect. The FAQ has the detail.
Subscriptions
MeshWatch is what the Config subscription turns on
One subscription covers the settings, customizations and scripts behind a connected ERP account, with 24 months of history.
Config and Config+
Settings, customization and script history for one connected ERP account, in two sizes.
Which ERP should we watch first?
NetSuite is first. Tell us what you run and vote for the connector you need next. MeshERP is in pre-launch, so nothing here is purchasable yet.