<@U8X7E86M6> <@U7N1AH9LP> Are you able to assist w...
# suitecommerce
a
@Steve Goldberg @Flo Meilan Are you able to assist with the following case I have raised for a client. RE: Case # 3911941 Update: "Defect: 599723 : SCA > One World > Inventory Available" We've had functionality working without customisation for SCA for the last 2.5 years that a singular website record with 4 subsidiaries (NZD default) would filter and display stock / out of stock based on the customers subsidiary - They are B2B suppliers for a dealer network that register via direct contact with the client. In the last 4-5 months we've updated from 19.1 to 20.1 and various hotfixes with the new version. We've experienced the following issue: Customer in AUD subsidiary (not the default) has always been able to purchase Item A which has stock in both NZ and AU locations. When no stock left in AU, the out of stock functionality kicks in - which for some items is to hide it and others is to show message etc backorder etc. What we're seeing is regardless of what subsidiary the customer is in (again B2B so doesnt have to be the default NZ) we're seeing ALL stock reflective of the default (NZ) levels which doesnt help when they have AU or US specific items. We've got PCVs right now to cover the issue and changed the backorder message appropriately but we've been in a constant back and forth the SCA Gold Support Team who INSIST the functionality never worked in the first place however I have it working in my own accounts, test accounts and other clients. Are you able to confirm this was never meant to work and become phased out in the backend? I completely understand the push for multiple licenses for B2C to ensure currency control and other benefits of separate website records but this breaking of a feature they've pivoted the entire investment on isn't helped with NetSuite saying its a defect than an enhancement then both when I've had them on video call showing them the functionality working as it should. Sorry for the long message but this is my last option before the client drops it completely and decides to go with Shopify / Wordpress. Any others who have managed to get here, let me know if you've experienced similar or if I am fundamentally incorrect. Deep breaths in and out 😅
s
I really don't know, sorry. This sort of backend complex behaviour is not really something I can claim to be an expert in
Regarding your final paragraph: I'm a bit confused. Are you saying that NetSuite cannot support this use case but Shopify/WooCommerce can?
Also I'm assuming you've followed all the described steps in Intercompany Cross-Subsidiary Fulfilment? https://netsuite.custhelp.com/app/answers/detail/a_id/70242
I spoke to a colleague and his advice is to revisit your working 19.1 site if you can. Doublecheck all of the customisations you have made including code, extensions, site configuration, web site setup record, etc and make sure that you have migrated them across.
If you have the site, you can also try swapping the customised version of SCA with the 'source' version of 19.1 SCA and see if it works. If it doesn't do a comparison between the two.
f
To my understanding this was never supported as out of the box at the bundle level, thought retrieving all the items in the specified Subsidiary it is supported on the search api by using the region parameter.
The documentation is clear that region parameter retrieves the subsidiary ID you are calling, and not actually the one the customer belongs to.
region
 — You can use the parameter 
region
 to specify the Subsidiary in a NetSuite OneWorld account and retrieve all the items in the specified Subsidiary. For example, if your Subsidiary ID is 4, you can use the following query string to retrieve all the items that belongs to this Subsidiary:
<http://www.mywebstore.com/api/items?region=4>
As Steve mentioned, cross-subsidiary fulfillment may be the reason why your customization is no longer working on your website. https://nlcorp.app.netsuite.com/app/help/helpcenter.nl?fid=chapter_1513107435.html
a
Hi @Steve Goldberg & @Flo Meilan, Thanks for taking the time to reply, i'll list out replies - dot points below: • With regards to Cross-Sub fulfillment, they do not have this switched on and dont expect to turn this on. They manufacture / transfer the stock with WO or TO. • The 19.1 and 20.1 sites are only different in the theme being compiled in the newest extension tools (I made sure we had the working version of EMB installed) with no new customisations added to them since the changeover. • With regards to Region parameter, was this field only made to be important in the functionality recently? I have a working version of this functionality which I can provide the test account ID if you have that level of access. • I've also asked my Managing Director to request a brand new SuiteSuccess WD account with SuiteCommerce Advanced bolted in so I can replicate the functionality working in a fresh environment so I'll keep you posted on that as well with this thread. Thanks again, Benjamin