Learn Mokapen

WooCommerce

Connect your WooCommerce (WordPress) store to Mokapen to bring customers (contacts), products (with variations and stock), and store orders into the CRM, and to export products created or updated in Mokapen to WooCommerce when the sync direction allows. Same goal as Shopify: unify e-commerce and sales management in the same workspace.

General overview: Integrations. Imported orders become sales orders in Mokapen (Orders module), not pipeline opportunities.

Requirements

• WordPress site with active WooCommerce, reachable over HTTPS.
• Permission to authorize Mokapen via the WC Auth flow (WordPress / WooCommerce administrator).
• An appropriate Premium Mokapen plan for e-commerce integrations. Without a plan, the connect button opens the upgrade screen.
• Mokapen permissions on contacts, products, and orders in your organization (see Roles and permissions).
• Access to Integrations (member/admin depending on white-label and org role).

Connect the WooCommerce store

1. User menu → Integrations → WooCommerce.
2. Enter the store web address (site URL, e.g. https://yourdomain.com). You find it in the address bar when you are in the WordPress backend / WooCommerce storefront.
3. Start authorization: you are redirected to WordPress/WooCommerce to the WC Auth page (/wc-auth/v1/authorize) with read_write scope.
4. Accept generating API keys for Mokapen (consumer key / secret are stored encrypted in Mokapen — there is no manual «paste API key» form).
5. Return to Mokapen: the store is connected. Mokapen registers WooCommerce webhooks (/wp-json/wc/v3/webhooks) to receive real-time updates.

If you do not accept authorization, no data is synchronized. The URL must be valid and HTTPS: otherwise validation fails.

What Mokapen requests from WooCommerce

The WC Auth flow grants Mokapen read/write access to the WooCommerce REST APIs needed for customers, products (and variations), orders, and webhooks. Mokapen does not replace the WooCommerce/WordPress panel for themes, payments, or plugins: it aligns data toward (and, for products, from) the CRM.

If you revoke keys or remove authorization on the WordPress side, disconnect and reconnect from Mokapen.

What gets synchronized

Toward Mokapen (import / webhook)

• Customers → Contacts — WooCommerce customers in the address book (and company if data allows). Updates also via webhook.
• Products and variations → Products — catalog with variations; WooCommerce stock (stock_quantity) is mapped to Mokapen variant quantity.
• Orders → Orders — WooCommerce orders become sales orders in Mokapen (with line items), not pipeline deals. Webhooks on updates.
• Abandoned carts / reports — marketing mentions or «Coming soon» entries in the UI do not equal an active cart reporting import like other flows: do not count them as a complete feature if they still show as coming soon on the page.

Toward WooCommerce (export)

• Products — with sync direction «toward WooCommerce» or «both», Mokapen can export/update products on the store (bulk sync and sync-out on product save, if the integration is active).
• Outgoing contacts and orders — as with Shopify, the automatic «sync out» export implemented today applies in practice to products. Customers arrive mainly from WooCommerce to Mokapen (import + webhook). Do not assume full bidirectional contact export just because commercial text suggests it: verify after connecting.

Config also shows services, but there is no dedicated services sync: use Products for the store catalog.

Settings after connecting

On the WooCommerce page, with the store connected:

Sync direction

• Toward Mokapen only — WooCommerce → CRM.
• Both — import + export (where supported; today mainly outgoing products).
• Toward WooCommerce only — Mokapen → store (products).

Entities

Contacts, orders, and products are the sync scopes (often preselected and not editable from the UI).

Share sync

Whoever connected can share the connection with the entire organization or selected users.

Duplicates and conflicts

• Avoid duplicates — typically contact recognition by email.
• In case of conflict — WooCommerce or Mokapen wins.

Privacy (WooCommerce)

Unlike Shopify, on the WooCommerce page you may also find privacy and collaborators/stakeholder controls related to how synchronized data is visible in the org. Set them if the team should not see all imported catalog/customers the same way.

Automatic vs manual sync

Enable automatic sync for ongoing updates (along with webhooks); use manual sync for the historical load. Check the data authorization on the page before syncing.

Recommended flow

1. Verify HTTPS and up-to-date WooCommerce on the site.
2. Connect the store from Integrations → WooCommerce and complete WC Auth.
3. Set sync direction, duplicates, conflicts, privacy (if present), and sharing.
4. Authorize and launch the first sync.
5. Check Contacts, Products (variations/stock), Orders in Mokapen.
6. Keep webhooks active for new events without relaunching everything each time.

Disconnect

From Integrations → WooCommerce → disconnect. In the modal choose whether to keep contacts, orders, and products already imported in Mokapen. After disconnecting, webhooks no longer update; data already in the CRM remains if you kept it. You can also revoke keys/authorizations from the WordPress panel.

Common issues

• Invalid URL / not HTTPS — use the full site address with https://.
• Authorization failed — a WordPress admin is required; verify WooCommerce and REST permalinks work (firewall/security plugins may block WC Auth or webhooks).
• Button blocked / upgrade — an appropriate Premium plan for e-commerce is required.
• Orders not in Opportunities — that is correct: they go in Orders (Sales → Orders).
• Stock / quantity — comes from variation stock_quantity; not a full WMS.
• Webhooks not arriving — the site must be reachable from the internet; local or basic-auth environments often do not receive WooCommerce notifications.

Frequently asked questions

Q: Do I need to generate API keys manually in WooCommerce?

A: No. Use the WC Auth flow from the Mokapen Integrations page: keys are created and saved when you return from authorization.

Q: Do WooCommerce orders become opportunities?

A: No. In Mokapen they become sales orders. Any text referring to «opportunities» is inaccurate relative to current behavior.

Q: Can I update WooCommerce products from Mokapen?

A: Yes, with a sync direction that includes export and the integration active.

Q: Difference from Shopify?

A: Same data model (contacts, products, orders) and same e-commerce Premium logic. The connection differs: Shopify uses OAuth on the Shopify app; WooCommerce uses WC Auth on your WordPress site URL. See also the Shopify guide.

Q: Is HTTPS required?

A: Yes. Without HTTPS the connection and webhooks are not reliable (and URL validation may fail).