Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $299.00 USD
- magento_2-Versionen
- —
- Rüstzeit
- 20 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
Customer-Specific Pricing & B2B Catalog
A build-to-order Magento 2 / Adobe Commerce extension that adds per-customer and per-group pricing, tiered and contract prices, hide-price / login-to-see-price, and group-restricted catalog visibility — engineered, installed and supported by ECOSIRE.
$299.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
Per-customer price overrides resolved ahead of group and tier pricing via a final-price observer and price-model plugin
Per-customer-group pricing with full cart, checkout, GraphQL and REST price parity
Tiered and contract pricing bands with optional validity date ranges per customer or group
Hide-price and login-to-see-price enforced server-side through block plugins and layout handles, not CSS
Conditional add-to-cart suppression when a price is hidden or the visitor is unauthorized
Restricted catalog visibility per customer group via category, search and product collection plugins
Hidden SKUs excluded from listings, layered navigation, sitemap and storefront APIs
Bulk price import via CSV using a console command plus admin grid, backed by a cron message-queue consumer
Admin ACL resources, system configuration section, and audit logging for all pricing rules
Service contracts (interfaces under Api/) so your team can read and write pricing programmatically
GraphQL and REST endpoints returning customer-aware prices for headless / PWA Studio storefronts
Upgrade-safe install with Setup data patches, declarative schema, and a clean uninstall routine
Über dieses Produkt
Wholesale and B2B selling on Magento 2 breaks the moment every buyer needs a different number. Magento Open Source gives you tier prices and customer groups, and Adobe Commerce adds Shared Catalogs and Company Accounts — but neither covers true per-customer contract pricing, conditional price hiding, and catalog visibility rules in one coherent, upgrade-safe package.
Warum Customer-Specific Pricing & B2B Catalog wählen
Per-customer price overrides resolved ahead of group and tier pricing via a final-price observer and price-model plugin
Per-customer-group pricing with full cart, checkout, GraphQL and REST price parity
Tiered and contract pricing bands with optional validity date ranges per customer or group
Hide-price and login-to-see-price enforced server-side through block plugins and layout handles, not CSS
Conditional add-to-cart suppression when a price is hidden or the visitor is unauthorized
Restricted catalog visibility per customer group via category, search and product collection plugins
This is a build-to-order extension. ECOSIRE engineers it as a proper module under app/code/Ecosire/B2bPricingCatalog, wires it into your store through di.xml plugins and event observers rather than core edits, then installs and supports it on your environment. Nothing is overwritten; the module ships its own etc/, Setup data patches, service contracts, and admin ACL.
Pricing resolution is layered: a catalog_product_get_final_price observer and a price-model plugin apply per-customer overrides first, then per-group, then tier/contract bands, with correct cart, GraphQL and REST price parity so headless storefronts and the Luma/Hyvä frontend agree. Hide-price and login-to-see-price are enforced server-side via a block plugin and layout handle — not just CSS — so prices and add-to-cart are genuinely unavailable to unauthorized visitors. Restricted catalog visibility filters category and search collections per customer group through a collection plugin, keeping hidden SKUs out of listings, sitemaps and APIs.
Bulk price import runs through a CSV/queue console command and admin grid, with a cron consumer for large books. You get admin ACL, system configuration, logging, and a clean uninstall path. We scope your exact rules first, build against your Magento version (2.4.6–2.4.8, Open Source or Adobe Commerce), deliver to staging, and hand over with documentation.
Was Sie bekommen
- Custom Magento 2 module under app/code/Ecosire/B2bPricingCatalog with composer.json, registration.php and full etc/ wiring
- Installation and configuration on your staging environment, then production deploy support
- Admin configuration guide and a short technical README covering ACL, cron and import format
- Service-contract interfaces (Api/) and GraphQL/REST schema for developer integration
- Bulk price import templates plus the console command and cron consumer setup
- 30 days of post-delivery bug-fix support and one round of refinement against the agreed scope
- Source code ownership — the module is yours, no per-seat or recurring license fee
Für wen das ist
B2B & wholesale merchant
Sells to dealers and distributors on negotiated per-account pricing and needs each logged-in buyer to see their own contract prices, not list prices.
Manufacturer with trade and retail channels
Runs one Magento store for public retail and gated trade, where trade SKUs and prices must stay invisible until a verified account logs in.
Magento store owner / ecommerce manager
Wants Adobe Commerce-style B2B pricing behavior on Magento Open Source without a six-figure upgrade, delivered as a maintainable, upgrade-safe module.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Customer-Specific Pricing & B2B Catalog-Moduls von Ihrem Konto-Dashboard herunter.
Auf Odoo hochladen
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Installieren Sie das Modul
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Customer-Specific Pricing & B2B Catalog“ und klicken Sie auf „Installieren“.
Einstellungen konfigurieren
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Verifizieren und live gehen
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.
Wie Customer-Specific Pricing & B2B Catalog im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Per-customer (not just per-group) contract pricing | ||||
| Hide-price / login-to-see-price enforced server-side | ||||
| Catalog visibility restricted per customer group across listings, search and APIs | ||||
| Bulk price import with queue/cron for large books | ||||
| GraphQL & REST price parity for headless storefronts | ||||
| Built, installed and supported for your exact Magento version | ||||
| Upgrade-safe (plugins/observers, no core edits) | ||||
| You own the source with no recurring license fee |
Häufig gestellte Fragen zu Customer-Specific Pricing & B2B Catalog
+How long does delivery take and what is the process?
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.
+Do I get ongoing support and updates after delivery?
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.
+Will this work on Adobe Commerce alongside Shared Catalogs and Company Accounts?
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.
+Is the price actually hidden from unauthorized visitors, or just hidden in the theme?
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.
+Can I bulk-load thousands of negotiated prices?
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.
+Does it support headless or PWA Studio storefronts?
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.
Warum Kunden ECOSIRE vertrauen
SOC 2 ausgerichtet
DSGVO-konform
Sichere Stripe-Zahlung
30 Tage Geld-zurück-Garantie
Lebenslange Updates
LGPL-3.0-Lizenz
Verwandte Module
Angebot anfordern
Customer-Specific Pricing & B2B Catalog
A build-to-order Magento 2 / Adobe Commerce extension that adds per-customer and per-group pricing, tiered and contract prices, hide-price / login-to-see-price, and group-restricted catalog visibility — engineered, installed and supported by ECOSIRE.
- Per-customer price overrides resolved ahead of group and tier pricing via a final-price observer and price-model plugin
- Per-customer-group pricing with full cart, checkout, GraphQL and REST price parity
- Tiered and contract pricing bands with optional validity date ranges per customer or group
- Hide-price and login-to-see-price enforced server-side through block plugins and layout handles, not CSS