Public Ticket #4533990 Multiple equipment per customer / multiple logical groups (visibility + price) Open
Comments Damien started the conversation5 hours agoHello, I’m currently looking for a WooCommerce B2B project using B2BKing Pro, and I’m running into a structural limitation that I’m trying to solve. Business context We have ~5,000 B2B customersAround 700 productsProducts are consumables linked to specific laboratory analyzersEach customer can have:One or multiple analyzersDifferent analyzer types (e.g. Analyzer A, Analyzer B, Analyzer C)A customer should:Only see consumables compatible with the analyzers they own or useNever see products for analyzers they don’t have Ownership / pricing logic For the same consumable: If the customer owns the analyzer → price AIf the analyzer is provided / rented → price B (fixed price, NOT a % markup)Additionally: Some customers belong to a commercial group with a global discount (e.g. -10%) Current limitation From what I understand: A customer can only belong to one B2BKing groupGroups are the main driver for:Product visibilityPricing rulesThis becomes an issue because: Customers can have multiple analyzersModeling one group per analyzer does not work since we are limited (1 group max)Modeling one group per analyzer combination quickly explodes (3000+ combinaisons)Managing rules per customer is not realistic at this scale ( 5000 customer) What I’m trying to achieve Conceptually, I’m looking for something like: Multiple “logical memberships” per customer (equipment-based)OR a way to combine:Equipment-based visibilityOwnership-based fixed pricingOptional global discount groupsAll of this without: Creating hundreds of groupsManaging product rules customer-by-customer My questions Is there a recommended pattern in B2BKing for handling:Multi-equipment customersWith strict product visibility and price?Any undocumented best practice?Thanks in advance for your guidance. Sign in to reply ...
Hello,
I’m currently looking for a WooCommerce B2B project using B2BKing Pro, and I’m running into a structural limitation that I’m trying to solve.
For the same consumable:
Additionally:
From what I understand:
This becomes an issue because:
Conceptually, I’m looking for something like:
All of this without:
Thanks in advance for your guidance.