NetSuite, can you update the instructions for adding a custom entry field (Like "Customer Comments")? The instructions found in SuiteAnswers (Answer Id: 24969) are NOT for Reference Cart v2.0? Or, can you post the instructions in here. -T

Dadabase, Do you need shipping and handling to display as one value (titled:"Shipping") in the checkout? If so, then there is another BUG blocking you from using he reference checkout.

NS answered in regards to "is there a work-around for the forced cart separation of shipping and handling" and they said... there is no alternate solution available This would not be classified as a Defect since there is no breakage in the functionality and it is working as designed. So, NetSuite shipping had/has a setting…

The "generic error" problem was a NetSuite bug. The workaround/fix was to go to "Setup > Site Builder > Customize Text" and copying the standard warning massages over into the corresponding custom message area. So, in the case of "Your order is under our $5 minimum"... we copied the NetSuite default message for that error…

Bump... Has anyone else tested the reference checkout v2.0 and if so... did a percent of your customers get the "Internal Errors" message during checkout? I opened a case with NetSuite and it seems to be moving slowly. -Tom

Apparently it doesn't pull analytics settings from the default NetSuite Google analytics settings area. Looks like we have to edit Javascript files to make Google analytics work again. Seems like a big step back in configurability (as far as user friendliness goes). The old system wasn't intuitive. Now it appears to be…

Nice. I'm excited. So, this is the non-beta version? It works with PayPal? -Tom

Mariano, before we test v.2.0.1, did they fix the shipping problem from Reference Checkout v2.0? Can we now display just one combined number for shipping and handling (as the field help in NetSuite indicates is expected behavior)?

NetSuite, can you tell us when the reference checkout issues will be fixed?

The reference checkout seems to be a step backwards in a number of ways. The biggest issue is usability (requires a programer and a bit of arcane knowledge to do anything). This shipping issue is just another flaw. Not having the ability to combine shipping and handling (which was an easy setting in the old cart) is a deal…

Found the custom transaction field answer here... https://netsuite.custhelp.com/app/answers/detail/a_id/24969/kw/custom%20transaction%20field%20reference%20checkout BUT, it had this note...."This article applies to the Reference Cart & One Page Checkout bundle prior to v 2.0" It references files not in v2.0. NetSuite, can…

Go to Setup > Company > Enable features. Click the Web Presence subtab. If you don't see "SuiteCommerce Advanced" as an option... then, you don't have "SuiteCommerce Advanced" and you either have SiteBuilder or no ecom.

"not ready for production" = YES We fixed about 4 game stoppers out of 5 needed to make it work. It gave shoppers vague errors. It turned out to be a bug with an easy fix. It messed up the header and had other formatting issues. Fixed by altering code. It breaks Google analytics; fixed with advise from SuiteAnswers.…

We never had that issue and we ran the Reference Checkout for a week before taking it down. If you report the issue, be prepared for the likelihood that they call it an enhancement request!

Thanks for the heads up about the cart issues JBounds! We don't use the cart, and only use the check-out. The check-out has been working pretty good so far. I ran into one issue today. How do we get our Google conversion analytics working again?? Apparently it doesn't use the analytics code entered into the settings at…

Never mind. No need for JavaScript. Just created a custom item field named custitem_custom_altimage and type=Inline HTML formula= CASE WHEN {custitem_ImageNumberTwo} IS NOT NULL then '<!-- -->' else '<style>#secondimagediv {display:none;}</style>' end Then, placed that custom Inline HTML field into the header of the item…

We don't have a verification option turned on in our account. We use PayPal's PayFlow Pro. I see those options in Cybersource settings, but not in PayFlow Pro. Also, 95% of the orders worked OK. It was the 5% that encountered the "Internal Errors" message during checkout that made us shut it off.

Three customers called today with an "Internal Error" message during store checkout. I'm now reverting back to old system. The last customer said they were using FireFox. I turned off reference checkout while the customer was on the phone. They went through again without any issues (using the old cart). I looked in our…

From my post #37. 1. "main domain" seems to be working 2. ??? still don't know 3. It works with payPal. Just in a confusing way. The customer gets sent to Paypal and it shows up like they're purchasing <null> for <null> dollars. They enter their credentials and continue (if they're not afraid to sign what looks like a…

Three things: 1. Edit the configuration file for the bundle, you can add your tracking id and url there and Google analytics will work ! So, do we enter our checkout domain or our main domain in the code below? I assume it is our domain, but it had a cart/checkout domain in there by default and so it made me wonder if it…

I see two recipes for fixing Google Analytics in Suite Answers. Are both valid for this issue. Is it one or the other or both that needs to be done? 1.https://netsuite.custhelp.com/app/answers/detail/a_id/32972/kw/google%20analytics%20Reference%20Checkout 2.…

Yes, new cart page / touch point

Was your site designed/built by John at Cantalupi or by Ruben at BluePoint ? -Tom

I'd like to see netSuite include a responsive design sample in its list of default themes. If changes outside of the theme are needed (like matching responsive item/category templates), they could be annotated as well.

I wonder if would be possible for a company to offer bundled responsive design Themes ?

Rob, email rpena@bluepointusa.net about that cantalupiusa site. They built it for or with John. That is what I've been told.

Never mind. Our tab labels are little "wonkey". We have a tab labeled "checkout tab" and that has nothing to do with "checkout.netsuite.com" pages. To add to <head> in checkout.netsuite.com pages we are to edit the "shopping cart" tab and NOT the "checkout tab". I had something wrong in my code in the first attempt.

Looks like some templates could be made adaptive with CSS using this method.. http://lemonade.im

THANKS. That helped. Now it just sends the users to: ourdomain.com/?whence= That is better. It resolves to our home page and not a failed search page.

FYI: The scripted way the SuiteAnswers describes is not the best way IMHO. They tell you to hide the NLCRUMBTRAIL by default by wrapping the <NLCRUMBTRAIL> in a <div> with the ID = "hansel" (do this in your sites theme) and set the div's visibility to 'hidden'. Then they say to put their script in the body of pages that…