All global settings live under B2B Commerce Kit → Settings. The Features tab is the master on/off switch for every one of the 24 modules.
Each module has its own on/off switch. Disabled modules load zero PHP or JS.
Default credit limits, payment terms, overdue behaviour, and interest rates.
Validity period, negotiation rounds, guest access, and auto-response emails.
Approval thresholds, expiry, PO number requirements, editing permissions.
Max sub-accounts, credit sharing, pay-later, approval requirements.
REST API access, remove data on uninstall, debug logging.
Settings → Features. Toggle any of the 24 modules on or off. Changes take effect immediately — no cache clearing needed.
Settings → Credit Settings. Set global defaults that apply to all companies unless overridden per-company.
Settings → Quote Settings. Set validity days, max negotiation rounds, guest permissions, and email templates.
Settings → Advanced. Configure REST API authentication, debug logging, and the data-on-uninstall option.
| Setting | Description | Default |
|---|---|---|
Remove Data on Uninstall | Delete all B2B Commerce Kit tables and options when the plugin is deleted | Off (keep data) |
Debug Logging | Write detailed logs to wp-content/b2b-commerce-kit.log | Off |
REST API | Enable the /wp-json/b2b-commerce-kit/v1/ REST API namespace | On |
REST API Auth Method | WooCommerce API Keys or WordPress Application Passwords | WC API Keys |
No. Toggling off removes the module from the load path (zero PHP, zero JS) but all rules, records, and history stay in the database. Re-enable and everything is exactly as you left it.
When on, deleting the plugin from WordPress removes all B2B Commerce Kit tables and options. Leave off (default) to preserve data during reinstalls or server migrations.
Yes. Every module exposes endpoints under /wp-json/b2b-commerce-kit/v1/. Authenticate with WooCommerce API Keys or WordPress Application Passwords. See Settings → Advanced → REST API for your endpoint list.
Yes. Settings → Migration has step-by-step guides for role mapping, pricing rule recreation, and order history. Run both plugins in staging for a billing cycle before removing the old one on production.