Last updated: 5 May 2026 — Tax and pricing regulations change; confirm GST treatment with your chartered accountant.

Key takeaways

• Start from a written price matrix (segment × SKU family × UoM) before you touch plugins.
• Roles scale until sales negotiates exceptions—then you need per-customer lists or ERP-led price APIs.
• Moosi Web implements WooCommerce development with finance-reviewed rules—read catalog fit first.

Start from a price matrix

Export a spreadsheet finance already trusts. Columns might include customer group, SKU, unit, currency, effective dates, and whether GST is inclusive or exclusive at display time. If marketing cannot explain a row, engineering should not encode it.

Version the matrix with change logs—silent Sunday edits are how margin leaks.

Roles and approvals

Map WordPress roles to commercial reality: dealer vs distributor vs employee purchase. Add approval queues when carts exceed credit limits or when first-time buyers need KYC. Log who approved overrides for audit trails.

Avoid duplicating HR identity in Woo long-term—plan SSO or periodic HR feed reconciliation for large orgs.

Imports and guardrails

Nightly ERP imports should validate totals, reject unknown SKUs, and alert on deltas beyond thresholds. Never let a partial import half-update tiers without wrapping in a transaction where your stack allows.

See inventory and ERP sync when stock and price must move together.

UX for buyers

Show why a price appears: contract name, tier, or campaign—reduces “your website is wrong” calls. For MOQ and pack sizes, validate at add-to-cart with plain language, not only at checkout. Pair with UI/UX design so dense tables stay readable on mobile.

When ERP must own price entirely, switch the UI to “request quote” rather than pretending live cart totals are authoritative.

FAQ

FAQ structured data appears in the head; keep answers aligned with finance-approved wording.