Skip to content

A sample report

The same document a verified owner receives, produced by the shipped rules from a storefront we wrote ourselves.

Synthetic storefront

www.deep-synthetic.example is not a real shop. It is a storefront we authored for our own tests — every product, category, extension and defect in it was written by hand, and the hostname is under a reserved domain that resolves nowhere. We do not publish an audit of somebody else’s site as marketing, which is the same commitment the crawler page and the partner clauses make to merchants who are not our customers.

The findings, the scores and the skipped checks below are not written copy: they are what the rules in the product produce from that storefront, at a standard audit depth, rendered at the Enterprise plan so nothing is hidden behind a lock. The executive summary a language model writes is absent, because no model was called to produce this document and we do not fabricate one.

SuiteCommerce health report — www.deep-synthetic.example

Generated 2026-09-15T00:00:00.000Z

Scores

81 / 100Overall health

Host
www.deep-synthetic.example
Platform
sca
Release
2024.1.30 (certain, modern family)
Theme
none detected
Extensions
2
Audit depth
standard
Pages fetched
60
Pages rendered
20
Generated
2026-09-15T00:00:00.000Z
SEO58 / 100

coverage 72%

Exposure80 / 100

coverage 74%

Content90 / 100

coverage 84%

Performance98 / 100

coverage 86%

Accessibility94 / 100

coverage 100%

Platform95 / 100

coverage 86%

Platform95 / 100 · coverage 86%

Platform findings
SeverityConfidenceStatusFindingAffectedSourceEvidence
WarningCertainUnknownThe SSP application is a year or more behindThe storefront runs SuiteCommerce 2024.1.30, at least 4 release cycles behind 2026.1 — roughly 2.0 years of core fixes and features that are not on this site.site-widerule

The SSP application is a year or more behind

The storefront runs SuiteCommerce 2024.1.30, at least 4 release cycles behind 2026.1 — roughly 2.0 years of core fixes and features that are not on this site.

Affected
site-wide
Attributed to
cause not attributed
Rule
platform/release-behind
Source
rule

Evidence (2)

  • Site › release.normalised"2024.1.30"site:release.normalised
  • Site › releaseSource"RELEASE_METADATA"site:releaseSource

Fix

Setup > SuiteCommerce Advanced > Set Up Web Site, and the SSP application bundle at /app/a code change

  1. Read Oracle release notes from this release forward and list the core changes that touch the extensions and theme this site runs.
  2. Install the target release as a second SSP application in sandbox and point a test domain at it.
  3. Re-apply the theme and extension overrides against the new core, then re-run this scan against the sandbox domain before switching production.
InfoCertainUnknownThe extensions this storefront shipsThe storefront ships 2 extensions from 1 vendor(s).2 modulesrule

The extensions this storefront ships

The storefront ships 2 extensions from 1 vendor(s).

Affected
2 modules
Attributed to
cause not attributed
Rule
platform/extension-inventory
Source
rule

Evidence (2)

  • Synthetic.Menus.2.1.02 modulesext:Synthetic.Menus.2.1.0
  • Synthetic.Wishes.1.0.01 modulesext:Synthetic.Wishes.1.0.0

Fix

Commerce > Extensions > Extension Manager, the activation list for this domaina configuration change

  1. Check the list against the extensions you believe are in use on this domain.
  2. De-activate anything no longer needed: an inactive extension still ships its JavaScript until it is removed from the activation list.

Want this for your own storefront? See the plans, or verify a domain and take the free audit.