WooCommerce B2B modernization: pricing rules, subscriptions and integrations without replatforming

#B2B pricing rules: when standard discounts fall short

The basic pricing hierarchy in WooCommerce covers regular prices, sale prices and optionally role-based prices. For a simple B2B shop with two customer segments that can be sufficient. Problems arise when you have:

• five different customer groups each with a separate framework agreement,
• dynamic prices dependent on order quantity and quarterly purchase history,
• price lists in GBP, EUR and USD for different markets,
• products accessible only to specific accounts (private catalogue).

In these scenarios Role Based Pricing plugins are no longer sufficient and a custom pricing engine becomes necessary. The approach we use is based on account metadata synchronised from the ERP and a dedicated custom table in MySQL holding per-account prices. This enables fast queries without burdening wp_postmeta - with thousands of product variants and dozens of customer groups, that table becomes a significant performance bottleneck.

#Table: when a pricing plugin is enough versus when custom logic is needed

#SAP Business One and Xero integration in a UK B2B context

UK B2B businesses commonly use SAP Business One, Xero, Sage 200 or similar systems. Each has its own API conventions, so integration requires knowledge of both the WooCommerce REST API and the data format of the specific ERP.

For SAP Business One the most reliable path is a connector that uses the SAP Service Layer REST API and synchronises data through an event queue. We typically synchronise:

• stock levels in real time or at configurable intervals depending on transaction volume,
• account data: VAT number, delivery address, payment terms, credit limit,
• orders with document numbers and fulfilment status,
• sales invoices with SAP-assigned reference numbers.

A project for a UK industrial components distributor demonstrated the value of an event queue after SAP went into an extended maintenance window for twelve hours at quarter-end. The queue held all WooCommerce orders and replayed them once SAP came back online. Synchronous REST calls would have lost those orders or left them in an indeterminate state.

#ERP integration: GoCardless, Stripe and UK-specific payment infrastructure

UK B2B commerce has its own payment DNA that differs from mainland Europe. BACS Direct Debit - processed through GoCardless in most modern WooCommerce setups - is the dominant recurring payment mechanism for subscription and invoice-based B2B. Stripe handles card-present and card-not-present for smaller B2B transactions. We configure:

• GoCardless mandate setup integrated into WooCommerce Subscriptions for recurring billing,
• Stripe for ad hoc B2B payments and Net 30 invoice settlement,
• bank transfer with automated reconciliation using Wise Business or similar for international accounts,
• e-invoicing compatible with PEPPOL for public-sector and NHS supply chain requirements.

#Subscriptions and recurring B2B orders

B2B subscriptions are not just “premium access” as in SaaS. For a wholesaler it might be a monthly consumable replenishment order. For a software vendor it is annual licences with automatic renewal and invoice. For a field service company it is maintenance contracts billed quarterly.

WooCommerce Subscriptions handles these scenarios after configuration. The critical element is failed payment handling. When a Direct Debit mandate fails - and in B2B this happens more often than vendors admit - the system should send a reminder, restrict access to subscription-gated materials, and escalate to the finance team rather than immediately cancelling. We configure dunning sequences that cover typical B2B cases: Direct Debit returned as refer to payer, payment in dispute, request for amended charge date.

#Checkout stability at B2B order volumes

B2B checkout differs from B2C: orders are larger, a technical failure means higher revenue loss, and trade accounts have greater expectations of reliability. Typical problems we resolve:

• payment gateway timeouts on high order values (Stripe and GoCardless each have configurable idempotency and retry settings that require tuning for large basket values),
• plugin conflicts in the cart for specific product variant combinations,
• PHP session unavailability under high concurrent load,
• missing VAT number or billing address validation leading to downstream ERP rejection.

We run load tests simulating typical B2B traffic patterns: larger baskets, fewer concurrent sessions, but each transaction significantly more valuable. Monitoring checkout completion rate with threshold alerts enables response within minutes rather than hours.

#Order approval workflow for procurement teams

Larger B2B organisations often require a procurement process where a member of staff configures the cart and a manager or the procurement department must approve the order before payment. WooCommerce does not support this natively, but we implement it through:

• a pending approval order status replacing the standard payment flow,
• an approver email with a link to the order summary and approve or reject buttons,
• an approver panel in the WooCommerce dashboard filterable by department or project code,
• integration with Microsoft Teams or Slack where the business already uses those channels.

This is particularly valuable for multi-branch organisations where each location has its own budget and purchases must be attributed to a cost centre.

#Trade credit management and order limit enforcement

A common B2B model is trade credit purchasing - the account places orders throughout the month and receives a consolidated invoice at Net 30 or Net 60. WooCommerce does not support this natively, but we build extensions that:

• display the available credit balance on the account page,
• block order placement when the limit would be exceeded,
• synchronise limits from the ERP after each posted payment,
• notify the account manager at 80% and 95% utilisation.

#Database optimisation as an alternative to replatforming

Before committing to a costly migration to Shopify Plus or Magento it is worth commissioning a WooCommerce database audit. Common performance problems in B2B shops:

• missing indexes on the wp_wc_order_stats, wp_postmeta and wp_options tables,
• bloated wp_options from plugins storing session data without TTL,
• excessive order metadata from plugins that are no longer active,
• N+1 queries in themes and plugins when loading product variants.

On a project for a UK electrical trade distributor, the audit revealed that wp_postmeta had grown to 65 million rows for only 16,000 products. After cleanup and targeted indexing the API response time dropped from 3.2 seconds to under 190 milliseconds. No platform migration was required.

#Multi-currency and multi-VAT handling for EU-facing UK businesses

Post-Brexit, UK B2B businesses selling into the EU face more complex VAT obligations than before 2020. WooCommerce with a suitable extension stack handles:

• EU OSS scheme threshold monitoring per country,
• automatic application of buyer-country VAT rates for EU B2C sales,
• zero-rating with VIES-validated VAT number for EU B2B cross-border,
• reverse-charge mechanism display on invoices for applicable transactions.

This is an area where manual approaches fail at scale. The HMRC Making Tax Digital (MTD) requirement means VAT data must be machine-readable; a WooCommerce-ERP integration that captures this at order time is significantly less expensive than correcting misclassified transactions quarterly.

#When replatforming is the right call

WooCommerce is not the right answer for every B2B requirement. Situations where we assess replatforming as justified:

• catalogues above 200,000 SKUs with thousands of variants and simultaneous multilingual requirements,
• marketplace requirements beyond available plugins,
• mandatory integration with SAP or Oracle ERP via certified connectors whose vendors do not support WooCommerce,
• industry-specific regulatory requirements in healthcare or defence where the entire platform must be certified.

In these cases we prepare an honest cost-benefit analysis: migration costs, ongoing platform fees, data migration risk and SEO impact.

#Omnichannel B2B: Amazon Business, trade portals and your own store

A growing number of UK and European B2B businesses operate simultaneously through their WooCommerce store and through trade portals like Amazon Business, Ariba or TradeGecko. Keeping inventory synchronized across channels is critical - an order placed on Amazon Business must immediately reduce the available stock visible in WooCommerce to prevent overselling and contract penalties.

We build PIM (Product Information Management) architectures that maintain a single source of product truth distributed to all sales channels. WooCommerce serves as the proprietary channel and pricing engine while external channels handle visibility and new account acquisition. A unified order and invoicing history across channels - visible in a single account portal - is the end goal.

#Customer account portal: self-service over support tickets

For B2B stores with many active accounts, handling order status queries, invoice requests and address changes consumes disproportionate support team time. A well-designed account portal eliminates most of this.

Features we implement in the account portal:

• order history with search - filter by document number, product, date and fulfilment status,
• one-click reorder - repeat any previous order with editable quantities,
• delivery address management - each branch has its own stored addresses,
• invoice PDF self-download - no need to contact support,
• credit limit and balance display - synchronized live from the ERP,
• sub-user management - add multiple employees with view-only or ordering permissions.

#Reporting and B2B analytics

Native WooCommerce reporting is insufficient for stores with hundreds of accounts and thousands of monthly orders. We implement extended analytics:

• account ranking by order value, frequency and quarter-on-quarter growth,
• basket analysis - average order value and behavior near free shipping or minimum order thresholds,
• churn report - which accounts stopped ordering and at what point in the sales cycle,
• credit risk dashboard - accounts nearing limits or showing overdue patterns.

This data integrates with Power BI, Metabase or Google Looker Studio so the sales team makes evidence-based decisions.

#Testing methodology for B2B deployments

Implementing pricing rules and ERP integrations requires rigorous scenario testing. For each B2B project we create a test plan covering:

• purchase path tests for each customer group (verifying the correct price, terms and document type),
• boundary condition tests (behavior exactly at discount quantity thresholds),
• ERP failure tests (WooCommerce behavior during a 10-minute ERP unavailability),
• payment gateway sandbox tests using Stripe test mode and Klarna playground,
• load tests simulating hundreds of concurrent trade account sessions.

Automated smoke tests run before every production deployment so that a pricing rule regression does not silently break other checkout paths.

#Documentation and knowledge transfer

A B2B modernization project is not only code - it is also knowledge transfer. For every project we prepare:

• integration architecture diagrams showing ERP, WooCommerce and payment gateways,
• operational runbooks for key maintenance tasks (updates, backup restore, monitoring response),
• API documentation for all custom integrations,
• admin training covering customer group configuration and pricing rule management.

Without this documentation layer the client team lacks the context needed to manage the environment independently after project handover.

#HPOS and preparing your B2B order architecture for change

WooCommerce 8.x introduced High-Performance Order Storage (HPOS), a dedicated order table replacing the legacy wp_posts and wp_postmeta schema for orders. For B2B stores with high order volumes, migrating to HPOS is not only a performance decision but also a prerequisite for certain integrations and a prerequisite for the WooCommerce roadmap going forward. The new schema enables indexing order fields without restructuring the whole database and makes reporting queries - critical for ERP reconciliation - significantly faster in practice.

Before migrating to HPOS we audit all installed plugins for compatibility, particularly custom plugins used for ERP integrations. Older plugins that write directly to wp_postmeta for order data require code updates before HPOS compatibility is confirmed. We check every read and write path for order data before running the migration, so the store operates reliably in both compatibility mode (both tables active) and full HPOS mode. Migration to HPOS during a broader modernisation project is lower cost than a standalone migration window later, so we recommend timing it alongside the core B2B upgrade work.

For clients who are also planning headless WooCommerce - where the frontend is built in Astro or Next.js consuming data through the REST API or WPGraphQL - HPOS compatibility is relevant because some REST API order endpoints behave differently in HPOS mode. We test the full API surface used by the frontend or integration layer against HPOS before go-live.

#Reporting and analytics for B2B commercial and finance teams

In B2B commerce, reporting is not just about units sold. Sales directors need per-account profitability analysis, finance teams require invoice reconciliation against ERP data, and management tracks KPIs such as average order value by customer segment and order frequency trends. WooCommerce’s native reports rely on wp_wc_order_stats, but for advanced B2B reporting we integrate with external tools - data export to Google Looker Studio, Power BI, or a dedicated data warehouse. With HPOS, historical order data is fast to query without stressing the production database with analytical workloads.

#B2B customer portal: self-service instead of email chains

B2B buyers expect efficiency - the ability to place repeat orders, retrieve invoices and check delivery status without calling account managers. A well-implemented customer portal in WooCommerce typically covers: order history with reorder functionality from saved purchase lists, PDF invoice download, live stock availability by SKU, named account credit balance display, and pending approval status for orders awaiting internal sign-off. For agencies serving UK and Irish B2B clients specifically, integrating with Xero or QuickBooks for automatic invoice reconciliation is often the single highest-ROI addition to the portal.

#Related services and next step

WooCommerce B2B modernisation is part of a broader digital architecture:

• GEO and LLMO optimisation - shop visibility in AI search and language models.
• WooCommerce developer - dedicated WooCommerce development support.
• Speed up WordPress - performance optimisation as the foundation of stable B2B processes.
• Contact - describe your shop and requirements, we will follow up with scoping questions.