mar-pod / b2b-advanced

1.0.1 2026-09-13 15:21 UTC

Requires

• mar-pod-b2b/module-b2b-advanced-approval: ^1.1
• mar-pod-b2b/module-b2b-advanced-pricing: ^1.1
• mar-pod-b2b/module-b2b-budget: ^1.1
• mar-pod-b2b/module-b2b-company-hierarchy: ^1.1
• mar-pod-b2b/module-b2b-procurement-integration: ^1.1
• mar-pod-b2b/module-b2b-quote-template: ^1.1
• mar-pod-b2b/module-b2b-sales-representative: ^1.1
• mar-pod-b2b/module-b2b-shared-catalog: ^1.1
• mar-pod/b2b-light: ^1.0

proprietary

• Marceli Podstawski

• metapackage
• b2b
• magento2

Published on Packagist.org on 2026-09-13 15:26 UTC

README

Composer metapackage for the Marpod B2B Advanced product. It contains no application code of its own — installing it resolves and installs mar-pod/b2b-light (the mandatory B2B Base plus every optional Light add-on) together with every Advanced add-on module, each still its own independently versioned Composer package and Magento module.

What this bundles

Everything in mar-pod/b2b-light, plus:

Add-on	Module
Company Hierarchy	Marpod_B2bCompanyHierarchy
Shared Catalogs	Marpod_B2bSharedCatalog
Advanced Pricing	Marpod_B2bAdvancedPricing
Quote Templates	Marpod_B2bQuoteTemplate
Advanced Approval	Marpod_B2bAdvancedApproval
Budgets	Marpod_B2bBudget
Sales Representative	Marpod_B2bSalesRepresentative
Procurement Integration	Marpod_B2bProcurementIntegration

Marpod_B2bProcurementIntegration ships only its generic integration core (signed/idempotent messaging, retry queue) and a non-production reference adapter — a concrete protocol adapter (cXML, OCI, PunchOut, ...) is a separate package installed on top, not part of this bundle.

Installation

composer require mar-pod/b2b-advanced
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush

Upgrading from B2B Light

Installing mar-pod/b2b-advanced over an existing B2B Light installation adds new tables and relations only — it does not modify, rename, or drop any existing Light table, and it never changes existing entity IDs (companies, customers, quotes, purchase requests, ...). Run the same three commands above; existing Light data, orders, quotes, and company memberships are unaffected.

Every bundled module is still independently enabled/disabled and configured — this metapackage only controls what gets installed, not what runs. A store that only needs a subset of Advanced can composer remove the modules it doesn't want, or module:disable them without losing data. See each module's own README.md for its specific safe-uninstall notes.

Versioning

This metapackage's own version tracks the Advanced product release, not any single module's version. Each require entry is constrained independently per module (Semantic Versioning); bumping a module's major version is a breaking change for that module alone and does not automatically bump this metapackage.

Development

The architecture, module list, and staged rollout plan live in packages/B2B_LIGHT_PLAN.md in the development Magento project (section 0 tracks overall implementation status; section 6a lists the frozen public Api/ contract per module; section 9 covers every Advanced add-on).