Make sure your webstore shows the latest changes
Oracle NetSuite SuiteCommerce lets you manage cache invalidation requests across multiple domains, either for an entire domain or for specific URLs, so your web store reflects your most recent changes.
Below we cover when to use each option, how to submit and monitor requests, what SuiteCommerce invalidates automatically, and how to handle common scenarios.
- Menu path
- Commerce > Content Management
- Scope
- Whole domain or specific paths
- Automatic
- Hosted file edits and overwrites
Full domain cache clearing
During development, or after redeploying SSP applications, clear the cache for the entire domain so updates to File Cabinet content, script files, CMS, and Item Search API output become visible.
This approach also helps when you have made multiple changes and tracking every affected URL is impractical.
Targeted URL cache clearing
For specific content updates, such as frequently changing banners, you can clear the cache for particular URLs. This method targets the SSP or SuiteScript files that define the content you want to refresh.
For example, to update a banner defined in /page.ss, submit a cache invalidation request for that specific URL.
Creating a new cache invalidation request
- Go to Commerce > Content Management > Cache Invalidation Requests > New.
- Select one or more domains in the Available Domains list and move them to the Selected Domains box. At least one domain is required.
- Choose the type of operation:
- Clear cache for the whole domain(s): clears the cache for the entire domain.
- Clear cache for the following path(s): clears the cache for specific URLs. You must add at least one URL path before submitting.
- Click Submit to start the cache invalidation request.
Note: For domains without CDN caches, a cache invalidation request clears only internal caches.
Monitoring cache invalidation status
After you submit a request, track its progress on the Cache Invalidation Status page. It lists all cache invalidation requests and lets you filter by:
- Date submitted: submission date and time range.
- Request type: Automatic, Manual, or both.
- Domain: one or more specific domains.
- User: the person who submitted the request.
- Status: Processed, In Progress, Failed, or any combination.
To open this page, go to Commerce > Content Management > Cache Invalidation Requests. You can also check a specific request by clicking Cache Invalidation Status on the Cache Invalidation Request page.
Automatic cache invalidation
SuiteCommerce automatically invalidates cached content in certain cases, reducing the need for manual requests:
- When you modify the content of a hosted file.
- When you overwrite a hosted file or media item.
Automatic invalidation is not triggered when you move, delete, rename, or upload new files. In those cases, you may need a manual request.
Group cache invalidation requests are created in scenarios such as uploading files through SOAP web services or uploading a .zip file to the File Cabinet. If a threshold is reached, multiple path requests may be replaced with a single wildcard request.
To prevent system overload, automatic throttling is enabled. If a high volume of requests is generated, some may be suspended and show the status "Suspended" on the Cache Invalidation Status page.
Cache invalidation in specific scenarios
Updating stylesheets
- Upload the new CSS file to the File Cabinet.
- Use the Cache Invalidation by URL page to invalidate the cached CSS:
- Enter the website domain, for example
www.mywebstore.com. - Enter the CSS file path, for example
/c.1234/skins/style.css.
- Enter the website domain, for example
This clears the CDN cache, but not the shopper's browser cache.
Changing product details
Submit a path request for the Item Search API response:
- Enter the website domain, for example
www.mywebstore.com. - Enter the Item Search API path, for example
/api/items?id=123.
Updating a product image
Enable Generate URL Timestamp on the file record to force a fresh CDN version.
Clearing SMT content
When new Site Management Tools (SMT) content is published, related caches are cleared for the site, including the Media Cache, Ignite Response Cache, Hosted Page Util Cache, and CDN Cache.
Make invalidation a routine
Cache invalidation is a routine part of SuiteCommerce operations, not an emergency tool. Use full-domain clears when many assets change together, and path-based clears when you know exactly what changed.
If content still looks stale after a request, check whether your domain uses a CDN or only internal caches, and whether the browser cache is involved. Reach out if you want help designing a safer invalidation routine for your team.