Skip to main content
Question

Blacklisted Customers

  • Nov 19, 2026 8:10 PM UTC
  • 10 replies
  • 44 views
  • Translate All

Hello,

 

I am looking for help and ideas on how to black list a customer from buying certain brands. Some of our suppliers have recently provided me with a list of customers whom we are no longer allowed to sell those brands products too. All the avenues that I have ventured down tend to rely too much on manual maintenance. I have 3000 plus customers and 100,000 plus SKUs to manually update discount codes with. I am open to any and all ideas. 

The criteria:

Customer A can purchase everything from us.
Customer B cannot purchase anything from brand B (10,000 Skus)
Customer C Cannot purchase anything from Brand B or C (15,000 skus)

How do I prevent customers B & C from purchasing while still allowing A to do so. 

10 replies

MichaelShirk
Captain II
Forum|alt.badge.img+8

How often do these lists change? 
My first thought would be a simple customization that adds a tab to the Stock Items screen, with a list of Customers who are not allowed to purchase the product. Customers can be added or removed using an Import scenario to make it easy to do in bulk. 
Then some simple logic that runs when the customer is updated on an order, or when an item is added to an order to block anything that would match between the item and its blacklisted customers. 

Translate

  • Author
  • Freshman I
  • Nov 19, 2026 8:44 PM UTC

Thank you for the response Michael. The blacklisted customer list would change monthly with any new additions the vendor provides us, usually 1 or 2. The bigger problem is managing to the new parts, when a supplier sends us a new parts list it could be 100+ parts long and to manually update the restricted customers on every part would be a nightmare.

Translate

MichaelShirk
Captain II
Forum|alt.badge.img+8
  • Captain II
  • Nov 19, 2026 8:59 PM UTC

Maybe I’m missing something. It would seems like a simple matter to do this in Excel, then import it with a few clicks using and Import Scenario. 

I don’t know how many customers the blacklisting applies to, but Claude in Excel is super powerful. It could probably take whatever format your vendor sends to you with the blacklist details and turn it into the data structure you need for the import scenario once you give it an example file that you’ve created one time to demonstrate the data structure.

Translate

  • Author
  • Freshman I
  • Nov 19, 2026 9:07 PM UTC

Are you talking about uploading it into the customization? I would prefer to do this natively somehow as customizations require funding which i do not have at this time... 

Translate

MichaelShirk
Captain II
Forum|alt.badge.img+8
  • Captain II
  • Nov 19, 2026 9:17 PM UTC

You could manage the lists with native functionality, but the logic to prevent those customers from buying the forbidden products would need to be a customization. 

You could actually also use native functionality to check line items for customer orders against items they’re forbidden from purchasing, but without code there’s no good way to add a hard stop to prevent the order from processing. 

However, again, if you have Claude, you can explain your use case and it could write a bit of code that you could paste into a customization and save yourself the cost of development. 

Translate

  • Author
  • Freshman I
  • Nov 19, 2026 9:19 PM UTC

Thank you

Translate

Steve Milner
Varsity III
Forum|alt.badge.img+8
  • Varsity III
  • Nov 20, 2026 1:06 AM UTC

My replies are created in part with the help of proprietary AI, built with my AI skills, curated and maintained myself. Most replies are tested on local instances before they go up, and all are reviewed before posted.

@brasch, it depends on how orders get entered. Restriction groups filter items by the user entering the order, not by the customer on it.

If your team keys orders in on the Sales Orders form, the same staff user enters orders for Customer A and Customer C, so restriction groups can’t separate them. That’s where Michael’s customization comes in.

If these customers order through the Modern Customer Portal on 2026 R2, the user entering the order is the customer’s own portal user. Inventory item restriction groups now apply to portal users on the Catalog (SP504001), so a group per restricted brand handles it natively. Making the group a default on the item class picks up a vendor’s new parts automatically. One catch: the class’s Apply Restriction Settings to All Inventory Items action replaces any groups existing items already have.

If you go the customization route, store the restricted brands on the customer instead of listing customers on each part. A new parts list then needs nothing beyond each item’s brand.

 

Translate

KrunalDoshi
Pro II
Forum|alt.badge.img+9
  • Pro II
  • Nov 20, 2026 10:11 AM UTC

Hi ​@brasch,

One approach I would consider is building a small customization around Customer and Brand restrictions, rather than maintaining restrictions at the individual Stock Item level.

Instead of blocking 10,000 SKUs individually for a customer, maintain a list of restricted brands for each customer. For example:

  • Customer A – No restrictions (can purchase everything).

  • Customer B – Restricted from Brand B.

  • Customer C – Restricted from Brand B and Brand C.

Each Stock Item would need to be associated with a Brand. When a user adds an item to a Sales Order, the customization would check the customer's restriction list and the item's brand. If the customer is restricted from that brand, it would display an error and prevent the item from being added to the order.

The biggest advantage of this approach is that you don't need to maintain thousands of individual Stock Item restrictions. If a new SKU is added under Brand B, it would automatically be restricted for Customers B and C without any additional maintenance.

I would also consider adding an import option to upload the supplier's list of restricted customers for a particular brand, so updating these restrictions would be much easier whenever the supplier sends a revised list.

The key is that the logic should be centralized in a reusable method/service, not separately written for every event or every graph.

Recommended solution

  1. Brand field on Stock Item — Ensure all 100,000 SKUs are categorized correctly.

  2. Customer Brand Restriction table — One row per restricted customer/brand combination.

  3. Restriction maintenance screen — Filter, search, enable/disable, effective dates.

  4. Excel import — Import supplier customer blacklist by brand.

  5. Sales Order validation — Block restricted products with a clear error message.

  6. Customer change validation — Recheck existing lines.

  7. Audit/history — Track who imported or modified the restrictions.

  8. Performance optimization — Indexed lookups, no customer-SKU matrix.

The key design principle is: restrict at the Brand level, validate at the transaction level, and maintain restrictions through bulk imports.

This would make the solution much more manageable and scalable, especially when dealing with thousands of customers and tens of thousands of Stock Items.

Hope this helps you design a custom solution!

Translate

  • Author
  • Freshman I
  • Nov 20, 2026 2:49 PM UTC

Thank you Krunal. would it be any easier if my part number schema has the brand already identified in it? Example a part number for brand ABC would like like this: ABC*12345. The “*” is the designator to move on to the next section of the part number. All part numbers from the same brand would begin with the same 3 digit code.

Translate

KrunalDoshi
Pro II
Forum|alt.badge.img+9

Hi ​@brasch 

Yes — that makes the solution considerably easier, because you may not even need to maintain a separate Brand field on every Stock Item, provided your part-number convention is consistent and enforced. Assuming the brand prefix is always consistent, unique, and reliably maintained.

If every item belonging to Brand ABC starts with ABC*, then the customization can identify the brand directly from the Inventory ID.

The biggest advantage is that when a new SKU is created, there is no additional maintenance needed, as long as the part number follows the same naming convention.

Translate