Magento for B2B Wholesale

Both reach roughly the same destination — the path is different.

Adobe Commerce B2B (native): ships a Companies module with a parent → child → buyer hierarchy, role-based purchase thresholds (e.g. Buyer can place orders up to $5k, Approver up to $50k, Company Admin unlimited), and an approval workflow that routes a pending order through the right approver before it’s placed. Cost: rolled into the Adobe Commerce license at $30k+/yr.

Magento Open Source: covered by extensions — Mageworx Companies ($299 + 12mo support), Aitoc B2B Suite (~$899), or BSS Companies (free + paid tiers). Combine with Aitoc Quote Workflow ($299–$799) to fill the approval gap. Total: $1–3k one-time vs $30k+/yr for AC.

The honest trade-off: AC ships a more polished UI, vendor-supported upgrades, and 24/7 SLA. OS extensions cover ~85% of the feature set at 5% of the cost — the remaining 15% is mostly "nice-to-have" admin polish. For most wholesale stores under $10M GMV, OS + extensions is the right call.

The shipped pattern across 40+ B2B builds:

• Buyer side: add items to a cart → click "Request a quote" instead of checkout → quote enters "Submitted" state. Buyer can attach notes ("we need this delivered split across 3 warehouses").
• Sales-rep side: internal admin queue shows new quotes. Rep opens the quote, can edit line-item prices, add discount %, override shipping, attach payment terms (Net-30 / Net-45 / Net-60), set expiry (default 14 days). Quote moves to "Counter-offered".
• Buyer review: email link → sees revised quote with line-by-line price changes highlighted → accepts or counter-counters (limit 2 rounds typically).
• Conversion: "Accept" converts the quote to a placed order with the agreed price + payment terms locked in.

PDF generation: auto-generated on every quote save, with company logo, customer billing/shipping address, line items + per-line pricing, tax breakdown, payment terms in the footer, expiry date in red. Library: Dompdf or mPDF for Open Source; native module for Adobe Commerce.

Expiry rules: stale quotes (past expiry) flip to read-only; buyer can request re-quote which spawns a new draft pre-filled with the old line items at current pricing.

Net-30 isn’t a payment method — it’s a credit-extension contract. The Magento mechanics:

1. Customer-segment configuration: "Verified Wholesale" customer group has Net-30 payment method enabled; new buyers default to "Card-only" until verified by AR.
2. Order placement: buyer chooses "Net-30 / Invoice me" at checkout. Order is placed in "Pending Payment" state — no card charge.
3. ERP push: order webhook fires to NetSuite / SAP / Tally / Odoo as a Sales Order with terms = Net-30. Invoice is generated in the ERP at fulfillment, not in Magento.
4. Invoice tracking: ERP pushes back invoice number + due date to Magento (so the buyer dashboard shows "Invoice #INV-1234, due Dec 15"). AR aging stays in the ERP.
5. Payment received: ACH / wire / cheque hits the bank → AR marks paid in ERP → ERP webhook marks Magento order "Paid" → auto-emails buyer the receipt.
6. Dunning: ERP sends 7-day, 14-day, 30-day-overdue emails. If 60+ days overdue, customer-group moves back to "Card-only" until cleared.

Critical: the source of truth for AR is the ERP, not Magento. Magento just shows the buyer their invoice status — the finance team operates entirely in the ERP.

Surprisingly granular. Magento’s native pricing stack lets you layer:

• Customer-group prices: per SKU, per group (Bronze / Silver / Gold / Platinum). 4 prices for 1 SKU is trivial; we’ve done 24 groups on a paint distributor.
• Tier prices: per group, per quantity-bucket. e.g. Gold tier: $10 at 1–99, $9 at 100–499, $8 at 500+.
• Special prices: per SKU, per customer (not just group), with start/end dates. Useful for "this one big buyer gets $7.50 forever".
• Cart price rules: conditional discounts ("any 100 SKUs from category X = 10% off") layered on top.
• Shared-catalog pricing (Adobe Commerce only): a complete alternate price-list per company-account. Open Source approximation: customer-segment + cart rules.

The wholesale reality — a single SKU might have 12 different prices across your buyer base. Magento handles that; Shopify B2B price lists hit limits around 4–5 tiers.

Performance note: with >500 active customer-group prices per SKU, indexing slows. Mitigation: keep group count under 30, push customer-specific overrides to "special prices" instead of new groups.

Different problems, different tools.

Requisition lists are for SKU lineups buyers reorder manually but frequently. The classic example: a hospital procurement officer maintains a "Monthly cleaning supplies" list with 47 SKUs. They open the list, click "Add all to cart", review quantities, place the order. Native Magento feature (Adobe Commerce); via Wyomind or Mirasvit on Open Source.

• Buyer is in the loop on every order
• Quantities can vary each cycle
• Lineup itself can be edited / shared with co-workers ("share with Procurement team")
• Multiple lists per buyer is normal (one for cleaning, one for office supplies, one for janitorial)

Recurring subscriptions are for SKUs that auto-replenish without buyer involvement. Example: a cleaning-services company auto-receives 20 cases of paper towels every Monday. No order placement, no buyer action — just a charge + ship event.

• Fully automated — buyer is not involved per-cycle
• Quantities are fixed (or fixed with skip-this-month buttons)
• Cadence is fixed: weekly / monthly / quarterly
• Best for fast-moving consumables with predictable burn

Stack: Magesterix Subscriptions, Aheadworks Subscriptions, or custom (built on Stripe Subscriptions or Razorpay for India). Avoid building from scratch — subscription billing has 30 corner cases (failed cards, prorated upgrades, paused subscriptions, regional tax).

Rule of thumb: ~70% of wholesale stores need only requisition lists. ~20% need both. ~10% (heavy MRO consumables) lean subscriptions.

The honest list of what works in 2026:

• NetSuite: direct integration via SuiteScript + REST API. Connectors: Patchworks (mid-market, $400–$800/mo), Celigo Integrator.io ($600–$1,200/mo), Folio3 NetSuite-Magento connector (one-time + support). Custom-built: $20–$40k for a clean implementation. Real-time stock + price; near-real-time order push.
• SAP (S/4HANA, Business One): IDoc-based (legacy) or OData (modern). Connectors: Pixafy SAP-Magento, Boltic SAP, Alumio. Custom: $30–$60k due to schema complexity. Batch sync (every 5–15 min) is the norm; real-time is achievable but pricey.
• Tally: XML-over-HTTP integration (Tally’s native pattern). Connectors: tdlexpert.com Tally-Magento bridge, custom modules from Indian dev shops ($3–$8k). Strong India-market choice; pairs with Razorpay for NEFT/IMPS payment.
• Odoo: XML-RPC API. Connectors: Magemodule Odoo bridge, EmiproTech Odoo-Magento. Custom: $10–$20k. Good for SMB wholesalers who run Odoo ERP + Magento commerce.
• Microsoft Dynamics 365: OData / Dataverse APIs. Connectors: Sana Commerce (built specifically for Dynamics), e-bridge by CData. Custom: $25–$50k.
• Zoho Inventory / Books: direct REST. Connectors: SkyVia, Zapier (small scale). Custom: $5–$15k. Good for SMB.

Decision rule: if you’re under $5M GMV with standard SKU master, a connector + middleware is faster (4–6 weeks). Above $5M with complex multi-warehouse / multi-currency / IDoc-based SAP, custom direct integration is more reliable and 3-year-cheaper despite the higher upfront cost.

5,000 lines is the high end of normal; 12,000 lines is doable with care; 50,000 lines needs a bulk-order asynchronous queue.

• 0–500 lines: synchronous. Submit → validate → cart → checkout in <5 seconds. No special handling needed.
• 500–5,000 lines: still synchronous but with a progress bar. Validation runs in chunks of 200 SKUs at a time to avoid PHP timeout. Total time: 10–30 seconds. Stock + price checks happen before cart insertion.
• 5,000–12,000 lines: asynchronous. CSV uploads → queue job → user gets an email with a "review your prepared cart" link in 1–3 minutes. SKU validation, price-snapshot, and stock-availability happen in the background. Buyer reviews + submits.
• 12,000+ lines: custom queue + multi-batch order (split into 2–3 separate orders to keep the order_items table sane). Often combined with multi-warehouse splitting.

Validation pre-submit: always show buyers (a) which SKUs aren’t found, (b) which are out of stock, (c) which have price differences from their list. Letting them edit / remove problem rows pre-submit cuts post-order disputes 80%.

Anti-pattern: never run a 5,000-line CSV through Magento’s standard add-to-cart events — you’ll trigger the catalog-rule indexer 5,000 times. Use direct quote-item insertion bypassing event observers.

Region-specific. Each has a clear preferred path.

ACH (United States): via Stripe Payments (offers ACH Direct Debit + Plaid micro-deposit verification), Authorize.Net eCheck, or NACHA-compliant gateways like Forte. Stripe is easiest to integrate (official Magento module + 2-day verification). Authorize.Net is cheapest at scale (~$0.10 per transaction vs Stripe’s 0.8% capped at $5).

SEPA Direct Debit (EU): via Stripe SEPA, Mollie SEPA, GoCardless. Mollie has the strongest Magento module + SEPA mandate management. GoCardless is purpose-built for B2B recurring debits and has the best webhook reliability for failed-payment retries.

NEFT / IMPS / RTGS (India): via Razorpay, PayU, or HDFC FirstData. Razorpay has the most mature B2B flow — supports NEFT, IMPS, RTGS, and UPI for sub-500k INR transactions. Direct bank transfers for >500k INR with reconciliation via virtual account numbers.

Bacs (UK): via GoCardless or Modulr. GoCardless dominates here.

Reconciliation pattern: all bulk-payment methods are async — the order is placed in "Payment Pending" state, buyer sees the bank-transfer instructions or initiates the debit, payment confirmation comes back via webhook 1–3 days later, order moves to "Paid" and fulfillment kicks off. Build the UX around this delay — pretending it’s instant breaks trust.

Different shapes of business, not "Magento better" or "Shopify better".

Shopify Plus B2B wins when:

• B2B is <30% of revenue and you’re primarily D2C
• One buyer per company (no role hierarchy)
• Quote workflow is single-level approval at most
• Customer pricing is "wholesale price + Net-30" with no per-SKU complexity
• You don’t need real-time ERP integration (5-min Celigo batches are fine)
• Time-to-launch matters more than long-term flexibility

Magento wins when:

• B2B is >40% of revenue (or pure-B2B)
• Companies with multi-buyer roles + multi-step approval are common
• Customer-segment pricing has 5+ tiers or per-SKU per-customer overrides
• ERP integration is real-time-critical (NetSuite / SAP / Tally / Odoo)
• Bulk-order CSV (5,000+ rows) is a frequent buyer flow
• Requisition lists + recurring orders are core to retention
• You need ACH (US) + SEPA (EU) + NEFT (India) on the same store

The Shopify Plus B2B 2025 update narrowed the gap: companies, customer-specific catalogs, Net-30, draft orders all shipped. But the gaps that remain — multi-step approval, 24+ pricing tiers per SKU, real-time IDoc-based SAP integration, 5,000-row CSV with pre-submit validation — are the gaps that matter for serious wholesale.

Wholesale stores often need products that exist only for specific buyer-segments — restricted-use SKUs, OEM-only items, exclusive bulk packs, or trade-channel pricing that shouldn’t be visible to anyone else.

Magento Open Source mechanics:

• Customer-group product visibility: via Aitoc Customer-Segment Catalog or BSS Hidden Categories ($199–$499). Each product has a "visible to groups" flag — logged-out users + non-matching groups see a 404 or redirect to login.
• Category-level visibility: hide entire categories from anonymous + non-trade groups. Trade buyers see "Wholesale Only" subtree; everyone else doesn’t.
• Login-walled storefront: entire store requires login. New visitors see only a login page + "request trade account" form. Used by pure-B2B distributors who don’t want their catalog scraped or visible to retail customers.
• Per-company custom catalog (Adobe Commerce Shared Catalogs): each company-account gets its own catalog snapshot — SKUs they shouldn’t see are simply not in their feed.

SEO consideration: hidden trade catalogs should return HTTP 404 (not 403) for non-authorised users to stay out of Google’s index. Pair with robots.txt deny rules for the URL paths and a separate sitemap that excludes the trade-only sections.

Pricing visibility: a common ask — show product but hide price until login. Native cart-rule: "Display price = $0 / login to see" with a "Request quote" CTA replacing the price. Done with a small Hyvä template override.

Common path. Risk is real but quantifiable.

The typical custom-portal stack: Laravel / Django / Rails app + MySQL/Postgres + manual ERP scripts. Built 5–10 years ago, hard to hire for, no upgrade path, every new feature is a custom build. Maintenance is a tax on the dev team.

Migration plan (12–20 weeks):

1. Data audit (week 1–2): companies, buyers, customer-group pricing rules, requisition lists, open quotes, AR balances. Map to Magento entities — companies → B2B Companies module, buyers → customers, segment pricing → customer-group prices.
2. Feature parity matrix (week 2): what does the custom portal do that Magento doesn’t out-of-box? Build the gap list. Usually 6–12 items, 3–5 of which need custom modules.
3. Magento + extensions setup (week 3–5): base Magento, Hyvä theme, B2B extensions, ERP connector, payment gateways.
4. Custom-portal data export (week 6): SQL dumps + CSV exports of all customer + order + pricing data. Validate counts.
5. Magento data import (week 7–9): via dataflow / API / direct SQL. Spot-check 100 customers + 50 orders for accuracy.
6. Parallel run (week 10–14): both portals live. New orders go to Magento; old portal is read-only for AR / reporting. Buyers get a "we’ve moved" email + reset-password link.
7. Cutover (week 15): DNS flip. Old portal stays read-only for 90 days for any AR queries.
8. Stabilisation (week 16–20): bug fixes, buyer training, ERP sync tuning.

Risk hotspots: (1) password migration — you can’t move hashes if the algos differ; force a reset email at first login. (2) saved-card tokens — need to re-tokenise at the new gateway via account-updater service. (3) custom-portal-only URLs — build a redirect map covering >95% of indexed traffic before DNS flip.

Real ranges from 40+ shipped projects:

Greenfield Magento Open Source B2B (no migration):

• Timeline: 12–16 weeks build + 4 weeks stabilisation
• Build cost: $30k–$80k depending on segment-pricing complexity + ERP integration depth
• Extensions: $3k–$8k one-time (Companies, Quote Workflow, Subscriptions, etc.)
• Hyvä theme licence: $1,000 one-time
• Hosting: $400–$1,500/mo (Cloudways / dedicated)
• 3-year TCO: $80k–$200k

Migration from Shopify Plus / SAP Hybris / custom portal:

• Timeline: 16–24 weeks build + 4 weeks parallel run + 4 weeks stabilisation
• Build cost: $50k–$140k
• Data migration: $10k–$30k (companies, buyers, pricing, AR balances)
• ERP re-integration: $15k–$50k depending on system
• 3-year TCO: $130k–$320k

Adobe Commerce B2B (vendor-supported):

• Same build cost as Open Source + Adobe Commerce license $30k–$80k/yr based on GMV
• 3-year licence: $90k–$240k on top of build cost
• Pays for itself when (a) you’d need 24/7 SLA anyway, or (b) you’re >$10M GMV with full B2B usage

Below $5M B2B GMV: Open Source + extensions is the right call. $5–$10M: close call — depends on team. Above $10M: Adobe Commerce + Cloud often wins on operational cost despite the licence.

Cheapest B2B build that’s not a regret: $30k. Anything cheaper skips ERP integration or quote workflow and you’ll rebuild within 18 months. The honest floor.