Skip to content

Sample report

What a SuitePulse report looks like.

An example analysis of a fictional ERP environment: health, ranked findings, one investigation in full, and a finding from every category.

Every number on this page is illustrative. This is not a customer environment.

Health overview

Health overview: score 78 out of 100, 23 problems detected, findings ranked by business impact, and a six-month trend. Example analysis with illustrative data.
ERP health: Production environmentExample analysis
Problems detected
23
Performance impact
Medium

By category

Performance72%FairTechnical debt75%FairData83%GoodAutomation70%FairReporting78%FairConfiguration90%Good

Findings by business impact

Highest first

  1. highScheduled script consuming excessive resourcesPerformance
  2. highApproval workflow re-triggers on every order editAutomation
  3. highOrder search scans every transaction since go-liveReporting
  4. mediumTwo scripts update the same field on every sales orderTechnical debt
  5. mediumUnused custom fields on the sales order formData
  6. lowIntegration role holds permissions no process usesConfiguration

Health over time

Health score by month: Apr 84, May 82, Jun 80, Jul 77, Aug 74, Sep 78. A fix was applied in Sep.
  1. Apr
  2. May
  3. Jun
  4. Jul
  5. Aug
  6. Sep

Dashed line: first fix applied

Top finding, investigated

Scheduled script consuming excessive resources. The sync reads every open order and saves each one, even when nothing changed.

Dependencies traced

  • Scheduled scriptNightly order sync
  • Saved searchAll open orders
  • WorkflowOrder approval
  • RecordSales order
  • IntegrationWarehouse
orders = search("All open orders")for order in orders:    recalculate(order)  // runs on unchanged orders    save(order)  // runs on unchanged orders

Impact

  • Longer execution time
  • Higher resource usage
  • Delays other scheduled jobs

Affects order fulfillment, warehouse sync, approval routing.

Recommended fix

Effort: Medium

Batch processing + optimized search criteria

  1. Filter the search to orders changed since the last run
  2. Process results in batches
  3. Skip the save when nothing changed
Nothing changes until your team approves it.

One finding from every category

Example finding: Two scripts update the same field on every sales order. Root cause: A 2021 customization and a newer one both recalculate shipping cost on save. Recommended fix: Retire the older script after confirming the newer one covers its logic. Example analysis with illustrative data.
Finding in Technical debtExample analysis
mediumTechnical debt

Two scripts update the same field on every sales order

Root cause
A 2021 customization and a newer one both recalculate shipping cost on save.
Impact
  • Slower record saves
  • Conflicting values
  • Higher maintenance effort
Recommended fix
Retire the older script after confirming the newer one covers its logic.

Applied only after your team approves it.

Example finding: Unused custom fields on the sales order form. Root cause: Fields added for a retired fulfillment process are still loaded and saved on every order. Recommended fix: Hide, then archive the fields after confirming no report or script reads them. Example analysis with illustrative data.
Finding in DataExample analysis
mediumData

Unused custom fields on the sales order form

Root cause
Fields added for a retired fulfillment process are still loaded and saved on every order.
Impact
  • Heavier record loads
  • Cluttered forms
  • Confusing reports
Recommended fix
Hide, then archive the fields after confirming no report or script reads them.

Applied only after your team approves it.

Example finding: Approval workflow re-triggers on every order edit. Root cause: The workflow runs on any field change, so address edits restart approval routing. Recommended fix: Limit the trigger to changes in amount or terms. Example analysis with illustrative data.
Finding in AutomationExample analysis
highAutomation

Approval workflow re-triggers on every order edit

Root cause
The workflow runs on any field change, so address edits restart approval routing.
Impact
  • Slower order processing
  • Duplicate approval emails
  • More manual follow-up
Recommended fix
Limit the trigger to changes in amount or terms.

Applied only after your team approves it.

Example finding: Order search scans every transaction since go-live. Root cause: The search behind the fulfillment dashboard has no date or status filter. Recommended fix: Add status and date criteria so it reads only open orders. Example analysis with illustrative data.
Finding in ReportingExample analysis
highReporting

Order search scans every transaction since go-live

Root cause
The search behind the fulfillment dashboard has no date or status filter.
Impact
  • Slow dashboards
  • Higher resource usage
  • Timeouts at month end
Recommended fix
Add status and date criteria so it reads only open orders.

Applied only after your team approves it.

Example finding: Integration role holds permissions no process uses. Root cause: A retired shipping connector still has full access to customer and order records. Recommended fix: Revoke the integration's credentials and remove the role. Example analysis with illustrative data.
Finding in ConfigurationExample analysis
lowConfiguration

Integration role holds permissions no process uses

Root cause
A retired shipping connector still has full access to customer and order records.
Impact
  • Unnecessary access risk
  • Harder audits
Recommended fix
Revoke the integration's credentials and remove the role.

Applied only after your team approves it.

Get this report for your own ERP.

A free analysis runs on your environment, read-only, and we walk you through what it finds.

  • No credit card
  • Read-only connection
  • See what SuitePulse finds in your environment

Plans for single environments, growing teams and partners. See pricing