A wholesale portal should enforce which SKUs a customer may see or buy, not only which price they get. Week one on Parcel Build is that first working version: allowlists or blocklists for known accounts so restricted products never reach checkout. You own the code. Flat monthly. See custom software for wholesalers. If customer-specific product restrictions in a wholesale portal is the gap, start a free 30-day build.
What product restrictions belong in week one for wholesale accounts?
Week one can cover allowlists or blocklists tied to known accounts so buyers only see or can buy permitted SKUs, and blocked items stay out of cart and checkout. Full PIM governance suites, regulatory compliance engines, and warehouse slotting rules can wait until that restriction path earns its keep.
On Parcel Build, week one is a first working version of that path. Flat monthly. You own the code.
Why emailing "do not sell them that SKU" fails when a new buyer user joins the company
Restrictions live in a sales email or a sticky note. A new buyer user on the same account never sees that note. They find the SKU in search, add it to cart, and place the order. Inside sales catches it late or not at all.
The stall is missing enforcement at browse and cart. Price rules alone do not keep a blocked SKU out of the cart. Account-level product restrictions do.
What stays out of month one
Defer full PIM governance suites. Defer regulatory compliance engines. Defer warehouse slotting rules. Month one is allowlists or blocklists for known accounts so restricted products never reach checkout.
FAQ
Are product restrictions the same as customer-specific pricing?
No. Customer-specific pricing sets what a buyer pays when they can buy the SKU. Product restrictions decide whether they may see or buy that SKU at all. They can sit together later. Week one can prove restrictions without cloning a full price-rules engine as the primary path.
Does week one need both allowlists and blocklists before restrictions help?
No. Week one can start with the model that matches how you already manage assortment: allowlist only, blocklist only, or a simple mix for known accounts. Both models at once can wait until that path earns its keep.
Next step
If customer-specific product restrictions in a wholesale portal is what feels hardest, start a free 30-day build. Name that gap on the form. We scope a free 30-day build on that problem: first working version in week one, flat monthly after if you want to continue.