5 Areas to Check | Copying A SuiteCommerce Configuration Record
It is wise to double-check that these five often troublesome areas of a copied SuiteCommerce Configuration Record are correctly set up.
Date
August 24, 2026
Read
7 min
When moving a SuiteCommerce website from Sandbox to Production (or vice versa), one of the required steps is to copy the Configuration Record and paste it into the new site. The fastest way to do this is to copy the configuration JSON.
While copying the Configuration JSON is helpful and speedy, it is wise to double-check that all areas of the Configuration Record are correctly set up. Below are often troublesome areas to verify that are configured after the copy.
1. Absolute URLs vs. Relative URLs – Use Relative URLs
Absolute URLs: uses the whole image address = the ‘https://sandbox.yourdomainname.com/image’
Relative URLs: only uses the slash after the domain = ‘/image’ from the example above.
If you use the absolute URL, then the image will not surface on the new domain record after copying the Configuration to the new domain!
Use Relative URLs
2. Sublists (Item Options)
It is helpful to verify that all sublists were copied correctly! In our case, the Item Options sublist was not copied when moving the Configuration JSON from one environment to the other. This made the functionality of some items appear missing.
3. Image URLs / folder paths (favicon)
Similar to Step #1, verify that your image locations and folder paths are directing correctly. To do this, compare and contrast the Configuration Record with the image’s folder location to make sure they are the same.
For your website filters to show properly, it is important to make sure that the internal IDs of your custom lists & custom fields are the same as the former environment.
If these internal IDs are different, then the Facets will not surface properly.
For more information, check out this Facet Field Setup Tutorial that my teammate Jacob wrote back in December of 2023.
5. Price Levels Field IDs Match
Most helpful for Strikethrough Pricing, verify that the price levels have the same field ID in both environments or adjust the destination field ID to the desired level.
Though this list is not comprehensive, it should be a jump start to making sure that your site’s configuration JSON was copied correctly!
Got stuck on a step in this article?
We like to update our blogs and articles to make sure they help resolve any troubleshooting difficulties you are having. Sometimes, there is a related feature to enable or a field to fill out that we miss during the instructions. If this article didn't resolve the issue, please use the chat and let us know so that we can update this article!
If you have questions about how our team can support your business as you implement NetSuite or SuiteCommerce, feel free to contact us anytime. Anchor Group is a certified Oracle NetSuite Alliance Partner and Commerce Partner equipped to handle all kinds of NetSuite and SuiteCommerce projects, large or small!
We are a premium SuiteCommerce agency that creates powerful customer portals. Unlike our competitors, we have already solved your problems.
For SEO purposes on SuiteCommerce, you may want to add a Robots.txt file to the website in order to stop Google bots from crawling your website. Here is a short how-to guide for robots.txt files in SuiteCommerce.
If you are in the middle of setting up a sandbox SuiteCommerce website, it is likely you will need to copy a configuration over at some point. Here is a shortcut that might save you time when moving from a staging domain to the live production website domain.
Here you will select all of the fields you previously added in website Setup. Notice that you are referencing the field ID, not the name. You have to put the exact field ID in for it to work, so if you're running into problems that's the first thing to check as you troubleshoot.