Medical, dental, and lab equipment distribution is B2B commerce with the volume turned up on everything that has to be controlled. Who is allowed to buy a given product. What lot and serial shipped, to which facility. Whether the spec and regulatory data on the page is current. Pricing negotiated per facility or through a group purchasing organization. A storefront that handles the ordering but not the control layer is not usable in this category.
We build for medical and lab equipment distributors on Shopware and Adobe Commerce. These are B2B portals for the B2B commerce sector. This page is about the control and compliance mechanics that sit on top of standard B2B commerce – the things that make or break an equipment distributor’s online channel.
Entitlements: who is allowed to buy what
Unlike most distribution, in medical and lab equipment not every buyer can purchase every product. Licensed practitioners, credentialed facilities, and product-specific authorizations all constrain the catalog. The portal has to enforce this at the account level:
- The customer record carries license, credential, and facility-type data.
- The catalog shows a buyer only what they are entitled to see and order.
- Checkout blocks restricted items for unauthorized accounts, cleanly and with explanation.
- Entitlement data is maintained in the system of record and enforced by the portal – never a manual gate a busy team forgets.
This is account-specific behavior in the same family as account-specific pricing, and it is built on the same account-resolved portal foundation.
Lot, serial, and traceability
Traceability is not optional in this category. For recalls, audits, and compliance, a distributor has to know exactly what lot and serial shipped to which facility. That means the order-to-shipment flow between the storefront and the ERP/WMS has to carry lot and serial detail, and the portal has to surface order and shipment status while the ERP owns the authoritative record. An integration that loses that chain fails the one requirement the business cannot compromise on.
Regulatory and specification data
In a compliance-sensitive category, product data is a liability surface, not just a UX detail. Spec sheets, IFUs, regulatory documents, and technical attributes have to be accurate, current, and versioned. That argues for a PIM or the ERP as the single source of truth, synced to the storefront – anonymized, we have built exactly this kind of pipeline for a medical-equipment distributor, syncing manufacturer specs, images, and regulatory data through a middleware layer so the storefront always reflects the controlled source.
Pricing: contracts, facilities, and GPOs
Medical pricing is contract-heavy: negotiated per facility, per health system, or through group purchasing organizations, often with tiers and eligibility rules. The storefront must resolve the right contract for each account and match it exactly, using the same precedence-based pricing discipline as any distributor – with the added wrinkle that GPO eligibility can itself be an entitlement.
Rep-assisted and reordering patterns
Equipment distribution mixes complex, rep-assisted first purchases with routine consumable reorders. The portal serves both: order-on-behalf-of for reps guiding a facility through a considered purchase, and requisition lists and reorder for the consumables a facility buys on repeat. One system, two motions, complete order history across both.
Who we are
Web Solutions NYC builds compliance-aware B2B commerce for medical, dental, and lab equipment distributors – anonymized examples include a medical-equipment distributor with account-specific catalogs, controlled product data, and a regulatory-data sync pipeline. We are a Shopware Platinum Partner and official Adobe Commerce partner, integrating with the ERPs and systems this sector runs: NetSuite, SAP, Dynamics, Acumatica, Sage, and Epicor P21.
Frequently asked questions
Compliance and control sit on top of normal B2B commerce. Products may be restricted to licensed or credentialed buyers, orders often need lot and serial tracking for traceability, regulatory and specification data has to be accurate and current, and pricing is contract-based per facility or GPO. It is B2B distribution with an added layer of who-can-buy-what and prove-what-shipped.
Through account-level entitlements: the customer record carries their license, credentials, or facility type, and the catalog and checkout gate restricted products against that. A buyer only sees and can order what they are authorized for, and the authorization data is maintained in the system of record and enforced by the portal rather than handled manually.
Yes. For traceability and recalls, orders and shipments need lot and serial capture flowing between the storefront and the ERP/WMS. The portal surfaces the order and its status; the ERP owns the lot/serial record. The integration has to preserve that chain so a distributor can answer exactly what shipped to whom.
Through a PIM or the ERP as the source of truth, synced to the storefront, so spec sheets, regulatory documents, and product data stay accurate and versioned. In a compliance-sensitive category, stale or wrong product data is a liability, not just a UX problem, so the data pipeline matters as much as the storefront.
Selling controlled or credentialed products online? Bring us your entitlement rules, traceability requirements, and contract structure, and we will map a portal that stays compliant. Let’s talk.