Contract-only items
Not every customer should see every item, and not every item has the same price.
Approved catalogs, contract pricing, lot rules, and compliance paperwork in one portal.
When your store isn’t wired to your ERP, your staff ends up doing the work by hand.
Not every customer should see every item, and not every item has the same price.
A substitute can be clinically and commercially different.
Lot, expiry, and order history need a clear path.
Customers get self-service answers, and your team gets hours back every day.
The customer sees the items and prices their account is allowed to buy.
Substitutions and restricted items route to the right person.
The account can see what was ordered and where to find the record.
The website should respect the main system, not recreate it.
Account eligibility, pricing, and approved-item context.
Units, lot, expiry, and substitution rules where the ERP holds them.
The transaction and paperwork trail stay in the main system.
Start with the real version. Prove the rules before launch.
Document which items and prices belong to which account.
Define restricted items, substitutions, and who can approve.
Make eligibility and restrictions visible.
Test the lot, expiry, and order-history path before launch.
Bring the hard questions to the first working session.
Start with the product catalog the customer is allowed to see.
Clinical and commercial rules may need different owners.
Do not promise traceability the ERP cannot support.
The answer should shape the customer portal, not just the checkout.
Start with the closest piece, then widen the scope.
Show us the contract, approval, and paperwork rules. We will map what the website can show and what the ERP must own.