I assume for your problem you tried the netSuite online help files? No "problem" here. You will also have to make the DNS/CNAME change that I'm talking about. It was all in an email from NetSuite titled "DNS Settings Changes Required for...". Search your email and you'll find the same notification. Then maybe you'll need…

No answer, waiting on clarification from NetSuite. NetSuite, can you clarify in here?

I remember setting that up back when we got started in NetSuite. The prefixes were definitely optional. I thought it was at "Set-Up ->Company->Auto Generated Numbers", but I was wrong as I don't see it there now.

* removed. Wrong answer

We used to see that error in the first version and still can see that in the first version when I deployed the old one. StephQ, When I go to the "Execution Log" tab on the Reference My Account SSP application settings area. It has these three errors each time I attempt to view an old order in "My Accounts"... Error ....…

Fixing the NetSuite mini-cart /cart summary so that it actually works with a site builder site (that uses reference checkout) is an enhancement ...and not a bug. That should be a clear indicator about the future of site-builder development ...in case there was any doubt. Issue Number: 324521 Type: Enhancement Severity: S3…

...if you're using a combination of Site Builder and Reference Implementations, you can create the "mini cart" by simply using JavaScript/HTML. We have some customers who already implemented that. I would think that this is not an exceptional use scenario. NetSuite makes the Reference checkout available to Site Builder…

I should say our site builder store's theme has pretty much nothing but <NLPORTLETCONTENTS> for the content of its "CART SUMMARY PORTLET TEMPLATE" . And what it serves up with <NLPORTLETCONTENTS> is not compatible with reference checkout.

Well, I'd help, but you're getting way more out of it than we are. This is all our customer's see... [ATTACH=CONFIG]n323248[/ATTACH]

We use.. https://www.magictoolbox.com/magicslideshow/

NetSuite says: The mini cart we're using was created via the NS tag <NLPORTLETCONTENTS> which is intended to be used only in Site Builder sites. Our store is a Site Builder site, but uses a reference checkout/cart ...so, a hybrid. He then says that... There must be a different way or approach to add a mini cart without…

Also, see this post if you're using reference checkout/cart with your site builder site.

NO. We tried it. Had errors and reported them to NetSuite. No fix ever came. We turned it OFF. To make matters worse... pretty much ZERO new ecom features for sitebuilder users in v2014.2.

It does look great. Nice job and thanks for sharing. When I saw the title of your post, I was hoping that you'd developed something that we're looking for. I'd like a feature like this that combines the "manually related" items and the correlated items into one seamless list. Lets say that we want a maximum of 5 items. So,…

Try Nextopia. We've been happy with their service.

jwenzer, I hope you are wrong. I hate that fuzzy pricing model. I found a little more information here (nothing about pricing though)... http://ignitecommerce.com/netsuite/

"Tools that Plug and Play with NetSuite" Nice tag line. It describes what we've been wanting for some time. Most web store improvements however are not "plug and play". Most NS webstore improvements require programming knowledge and/or a 3rd party developer. Now with two separate Ecom platforms, it seems like NS is…

I'd think that when pricing Ignite, NetSuite would look at the price to integrate with Magento as a good number to match since Magento is a common viable ecom alternative that is presently available to NS subscribers. Magento Go Prices... http://go.magento.com/plans/ The hosted version of Magento ("Magento Go") ranges from…

What ever happened to ignite commerce? It was touted as the big revolutionary change in the previous release. It seems to have died ...or else never quite lived yet. So far, we've gotten no feature gains out of that release .

Oh, I didn't know that they purchased the Ignite company. So, NS isn't required to pay a 3rd party for each new Ignite subscriber. Well, there is even a better argument for just making Ignite the "ecom edition" default web store platform. It will bring NS ecom into the 21st century and they'll pay for it by increased NS…

I tried getting some pricing answers, but our account rep is not longer with netSuite. The temporary rep confirmed my fears. The "Ignite" add-on is exorbitantly expensive. She was a little unsure of her self, so hopefully she was wrong. The really bad news is that IF we turn down all ties with anything "Ignite", we'll be…

"re-implement our site and pay a lot more money" ...that option was already available with other best of class ecommerce platforms (like Magento). If this is the case, then Ignite is nothing new to report and the real story with 2012.1 is that we can stop waiting for NS to fix their ecommerce. Fixing it will be off of…

The subject line of this thread says "Ignite Ecommerce". NetSuite is integrating with "Ignite Commerce" and not "Ignite Ecommerce"... right? So, they integrating with this.... http://ignitecommerce.com/ ...right? Are there any more details ...other than this... The new NetSuite Ignite Commerce platform enables the creation…

I've always fealt that the lack of communication and slow pace of e-com improvements were both symptoms from being woefully understaffed ...at least on this side of the pond.

If the cost is no more then an additional one or two hundred (per month), then I'll gladly pay extra for "full featured" ecommerce. We already pay for "add on" services to fix deficiencies in the NS web store (like Nextopia for our web store search). I could drop those services if we get all of the Ignite features (listed…

There will be a variety of pricing options for Ignite. Some of them will be new structures with no additional subscription cost (but will be based upon percent of revenue) and others will have some cost. I'll gladly stay with the current NS e-commerce platform if Ignite takes a percent of revenue. You say "some of them",…

...set of APIs that provide you access to the data in the system, and SuiteScript Server Pages that allow you to write custom sites that make use of that data. In the paraphrased sentence shown above, I'm hearing that we will need a more advanced IT guy. Does it require advanced programming skills? I tried to see more…

please please ensure that the old styles still remain live?!?!? This highlights a problem with a "roll your own" approach to ecom. We all built our own fixes to missing web-store features, then if/when NS adds them years later ...we have to undo what was done and/or have bugs relating to the hundreds of varied approaches…

The NetSuite eCommerce team does realize that our HTML layout and ability to customize the layouts etc. needs improvements. Good. Note: There are threads in here from 2006 complaining about how far behind it was (even back then) and yet the webstore/layouts/templates have remained mostly unchanged since we started using…

What about an iframe? May not be ideal for SEO as the blog is actually stored elsewhere, but an easy solution. To bad we can't install word-press right in our file cabinet.