The business doesn’t ask for a plugin. It asks for a decision: ready plugin, own code or an external service.
The request
“We need B2B prices for our 300 wholesale clients.” Individual prices on 5,000 SKU, deferred payment, a minimum order amount, a daily price sync from the ERP.
The client doesn’t ask which plugin to install. The client asks if this will work, what it costs and what breaks.
The answer by the scheme
Requirements → data → flows → risks → verification.
- Data. Prices are not product meta (300 × 5,000 = 1.5 million values), but an own table
(customer_group, sku, price)with an index. Clients are price groups, not 300 separate rules. - Catalog prices. Price filters plus the variation cache hash with the customer group. Page cache off for logged-in wholesale clients.
- Checkout. A “Deferred payment” method only for the B2B group, status
on-hold, minimum amount throughwoocommerce_check_cart_items. Tested in block checkout. - Sync. Daily ERP price import through Action Scheduler in batches, upsert into the table, an error log.
- Risks. Wholesale prices leaking to guests through the cache, price filter performance, conflicts with discount plugins.
- Verification. Price calculation tests, an E2E wholesale order, monitoring of failed sync jobs.
Plugin, own code or an external service
A ready plugin when the feature is standard and critical for money (subscriptions, payments, taxes) and the plugin is maintained. Own code when the business is specific and ready solutions need more workarounds than your own code. An external service when the data or the process already lives elsewhere: ERP, CRM, or a migration to or from Shopify.
The interview question
Design monthly coffee subscriptions with delivery.
Weak answer. I’ll install WooCommerce Subscriptions.
Strong answer. First I clarify the requirements: automatic or manual payment, changing the blend and pauses, the number of subscribers. If automatic payments are needed, a ready subscriptions plugin with a gateway that supports card tokenization, because building recurring payments yourself is a big risk. Own code only for the specifics: choosing next month’s blend, syncing with production through a queue. Risks: failed charges and retries, plugin updates, testing renewal dates.
👉 The full chapter is in the course WooCommerce Development for Middle Devs: Module 10. Interview
🔔 More WooCommerce videos: youtube.com/@4wpdev