Les détails du produit sont affichés en anglais. Traductions à venir.
Faits en bref
- Prix
- $299.00 USD
- Versions magento_2
- —
- Temps d'installation
- 20 minutes
- Licence
- Perpétuel unique
- Langues
- 11 langues
Achat unique
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
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Fonctionnalités clés
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
À propos de ce produit
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.
Pourquoi choisir Customer-Specific Pricing & B2B Catalog
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.
Ce que vous obtenez
- 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
Pour qui c'est
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.
Aperçu de l'installation
Télécharger depuis ECOSIRE
Achetez la licence sur ecosire.com et téléchargez le module ZIP Customer-Specific Pricing & B2B Catalog depuis le tableau de bord de votre compte.
Télécharger sur Odoo
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Installer le module
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez Customer-Specific Pricing & B2B Catalog et appuyez sur Installer.
Configurer les paramètres
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Vérifier et mettre en ligne
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
Comment Customer-Specific Pricing & B2B Catalog se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| 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 |
Foire aux questions sur 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.
Pourquoi les clients font confiance à ECOSIRE
SOC 2 aligné
Conforme au RGPD
Paiement sécurisé Stripe
Remboursement sous 30 jours
Mises à jour à vie
Licence LGPL-3.0
Demander un devis
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