Making a Stock Item available to only one customer

Hello,

Restriction Groups may work to create a relationship between a customer and Inventory Item(s).  Try it out in  your Test tenant first, to make sure it works as you need.

All great suggestions that might work on this use case but I think if you have this case often, then you will need a customization as follows:

1. Add a bool field to inventory item indicating whether “Restricted by Customer” or not?

2. Add a Simple Custom Tab to Costumers to Assign the “Restricted Inventory Items” to the desired customers.
3. In your Sales Order (or any screen you want restrictions be applied) override the Inventory Item Selector to retrieve only Unrestricted Inventory Items + the Customer Specific Restricted Inventory Items.

I guess this is your foolproof go to option but of course requires customization.

I was able to solve my problem using Restriction Groups.

Since I am the Salesperson for this account and the Items to restrict should only ever be sold to this one account, I made the restriction relationship between the Items and the User, me (as recommended by Reza above). I also put non-salesperson users in this group, so our buyer, etc… can see these items.

This is an elegant solution for us. I greatly appreciate everyone’s input and help.

@scottaisd00 Perhaps you can create the customer as a warehouse bin location and transfer items to this location. Make sure you have sales allowed unchecked as an extra precaution:

• estebanperalta54 I moved product into a new Warehouse Location via the Location Table. But when i need to sell the item to the customer, i check Allow Sales in that location, but i get error when making a shipment that says, “no items in warehouse to ship” Any ideas?

@Ellie we’ll take you up on your offer.  Let me coordinate with the team and email you some proposed date/times for a deep dive.

Guys, I might be wrong but I guess there is a misunderstanding about the “Restriction Groups”.

My understanding is RGs are meant to restrict a “User” Access to entities like “Projects”, “Stock Items”, and … not cross-reference “Entities” Access to each other. If you open up the “Project Access” screen it is very clear and the same logic applies to the “Neighbour Entities” as per Acumatica terminology. In the PM Access you can clearly see you have a “RelationGroup” which is the form header, A tab for “Projects” which is tied to this Group, and another tab indicating who has access to the selected “Projects” as per the “GroupType” settings.

This logic applies to all other Entities to the best of my knowledge. For example, in your last screenshot you have a group (you can name it whatever doesn’t have any impact in your case “Josh Lewis Games”) then once you are selecting “Inventory Items” Entity and related stock items. One more time you are selecting “Customer” Entity and the associated customers. I assume that you have selected the “User” Entity type here as well and have identified the users who are part of this Group.

Now considering your Group Type is “A” then in fact you are telling the system that the associated user to this group has access to the selected customers and selected inventory items. You are not telling the system that the selected customers are allowed to purchase the selected inventory items.

This is how Acumatica determines whether a user has access to a RelationGroup Neighbor Entities or not. This is for Projects but the same validation goes to other entities as far as I know.

RelationGroup.SpecificModule == null or 
RelationGroup.SpecificModule == typeof(PMProject).Namespace or PX.SM.UserAccess.IsIncluded(EntityGroupMask, RelationGroup)

// The code is not like this. I just put it like this for presentation purposes

To me it all perfectly makes sense. As mentioned in my first response, the only possible way for the aggregated restriction I believe is customization. 

I guess there are some exceptions like Company, GL Account, and Subaccount … but I don’t believe all entities can be used as mish-mash together.

I am still thinking about this question, and I think I can answer my own question: If we add Users to the Restriction Group I suggested,  Scott’s question is not solved, because he’ll need multiple restriction groups by customer and then, his employees will be in all groups and will see all customers anyway.

I am still disappointed; it would be really cool if Customer-Item restriction groups could work like they did in my imagination.  I’m hopeful Dana is asking because Acumatica is considering adding this feature. :-) 

One related idea we can vote for:

HI @scottaisd00 

Did you move the items via Transfer? Or did you only change the location on the Item?

I am interested in this feature.  

Much appreciated! Looking forward.

Hello,

Restriction Groups may work to create a relationship between a customer and Inventory Item(s).  Try it out in  your Test tenant first, to make sure it works as you need.

 

Hello,

Step 1 is shown above. Give your group a name, Select Entity Type “Inventory Item.” Check the box at left, to include the custom inventory item for your customer.  Save.

Step 2: change the Entity type to Customer.  Check the box at left, to include the customer in the same group with their item. Save.

Test.

If the above steps work fine in your testing then repeat the Restriction Group in Live. Good luck!