Custom Storefront Error Pages

You can create branded custom error pages (technically referred to as a 404 error page) within the storefront. Use custom error pages to provide a helpful message to your customers, with information about what to do next, instead of a generic message like 404 URL not found.

Select Administration > Site Development > Custom Error Pages.

You can upload customized error pages for the following HTTP status errors:

Internal Server Error (majorerror.html)
URL not found (url_error.html)
Timeout (overload.html)

Note: Static resource error pages cannot be customized.

Uploading

The B2C Commerce Web Server error pages are uploaded to a shared directory. To view this directory, select Administration > Site Development > Custom Error Pages.

Within Business Manager, you can download a template .zip file containing all error pages that are used in cases where the application server is down or doesn't respond in time. After you download the .zip file, you can customize the content, archive your work, and upload it.

Upload the pages as one .zip file that includes the following:

One html file per error code
CSS files and images as necessary

The uploaded .zip file must be named errorpages.zip. Don't use names such as myCustomErrorPages.zip.

Note: Only one .zip file can be uploaded at a time. Remember to reference CSS files and images using /waroot/FILENAME.

After your upload, the .zip file is automatically extracted and the content is stored on the web server.

Note: The content is loaded to the web server via a job that runs every 2 hours. You might have to wait up to 2 hours to see the content on the server.

Testing

Test customized errors by:

404 error: entering an invalid URL.
Transmission error: Call support and request that they take down the application server for the instance. Only do this on Sandboxes.