Customer-Specific Pricing & B2B Catalog

This is built to order, not an instant download. After a short scoping call to confirm your pricing rules, Magento version and edition, typical delivery is about 1 to 3 weeks depending on complexity. We build against your version (2.4.6–2.4.8), deliver to your staging environment for review, then support the production deploy.

Yes. Every build includes 30 days of post-delivery bug-fix support and one refinement round against the agreed scope. Because you own the source, the module is compatible with your current Magento version; we offer paid maintenance retainers for future Magento 2.4.x upgrades, new rules, or feature additions.

Yes. The module is built with plugins and observers, so it coexists with Adobe Commerce B2B features. We scope where our per-customer logic should override or complement Shared Catalogs so the price resolution order is predictable and there are no conflicts.

It is enforced server-side. Hide-price and login-to-see-price use block plugins and layout handles plus collection filtering, so prices, add-to-cart and restricted SKUs are absent from the rendered HTML, GraphQL and REST responses — not merely hidden with CSS that a curious visitor can bypass.

Yes. Bulk price import accepts CSV through an admin grid and a console command, and large books are processed through a Magento message-queue cron consumer so imports do not time out. We provide the import template and map it to your customer accounts and groups.

Yes. Customer-aware prices and catalog visibility are exposed through GraphQL and REST with service contracts, so a PWA Studio, Hyvä headless, or custom frontend receives the same per-customer pricing the Luma storefront does.