Learn Mokapen

Main menu
App Integrations Common features Contact us

Shopify

Connect your Shopify store to Mokapen to bring customers (contacts), products (with variants and quantities), and store orders into the CRM, and to export products created or updated in Mokapen to Shopify when the sync direction allows. It helps unify e-commerce and sales management: master data, catalog, and purchase history in the same workspace.

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

 

Requirements

  • Active Shopify store (URL ending in .myshopify.com).
  • Permission to authorize the Mokapen app on Shopify (OAuth) with a store admin account.
  • An appropriate Premium Mokapen plan for e-commerce integrations. Without a plan, the connect button opens the upgrade screen; in some Shopify flows a recurring charge linked to the app may also be offered.
  • 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 Shopify store

  1. User menu → IntegrationsShopify.
  2. Enter the store name (as in Shopify Admin; the full URL ends with myshopify.com). If unsure, open the Shopify dashboard and check the browser address bar.
  3. Start authorization: you are redirected to Shopify to accept permissions.
  4. Accept the requested scopes (read/write customers and products, read orders — see below).
  5. Return to Mokapen: the store appears connected. If you arrive from the Shopify App Store, you may need to choose the Mokapen organization on which to install the connection.

If you do not accept on Shopify, no data is synchronized. After connecting, Mokapen registers webhooks on the store: so updates to customers, products, and orders can arrive in real time, in addition to the bulk sync you launch yourself.

 

What Mokapen requests from Shopify

During OAuth authorization Mokapen typically requests:

  • read_customers / write_customers — read (and potentially write) Shopify customers.
  • read_products / write_products — read and update products/variants.
  • read_orders — read store orders.

Mokapen does not replace the Shopify panel for checkout, themes, or payments: it aligns data toward (and, for products, from) the CRM. If you revoke the app from Shopify or the token expires, disconnect and reconnect from Mokapen. Shopify also requires GDPR endpoints (data request / redact): Mokapen handles these via webhook.

 

What gets synchronized

 

Toward Mokapen (import / webhook)

  • Customers → Contacts — Shopify master data enters the address book; if company data is present, the company may also be created/linked. Webhooks on customer create/update/delete.
  • Products and variants → Products — catalog with variants; Shopify variant inventory quantity is mapped to the Mokapen variant quantity field (not a separate warehouse module).
  • Orders → Orders — Shopify orders become sales orders in Mokapen (with line items), not pipeline deals. Webhooks on order updates.
  • Abandoned checkouts — sync may include a path to import abandoned Shopify checkouts (as orders/related data). Dedicated reports for abandoned carts / e-commerce analytics on the page still show as Coming soon: do not count them as an active feature yet.

 

Toward Shopify (export)

  • Products — with sync direction «toward Shopify» or «both», Mokapen can export/update products on the store (bulk sync and sync-out when you save a linked product, if the integration is active).
  • Outgoing contacts and orders — despite write_customers scopes, the automatic «sync out» export implemented today applies in practice to products. Do not assume full bidirectional export of contacts or orders: customers arrive mainly from Shopify to Mokapen (import + webhook). If marketing text mentions «bidirectional contacts only», verify in your environment what sync actually does after connecting.

In config the integration also lists services, but there is no dedicated e-commerce services sync like for products: use Products for the store catalog.

 

Settings after connecting

On the Shopify page, with the store connected, you typically configure:

 

Sync direction

  • Toward Mokapen only — data flows from Shopify into the CRM.
  • Both — import + export (where supported; today mainly outgoing products).
  • Toward Shopify only — push from Mokapen to the store (products).

 

Entities

Contacts, orders, and products appear as sync scopes (often already selected and not editable from the UI). Historical sync and webhooks cover these three blocks.

 

Share sync

Whoever connected the store can let other members use the same connection (entire organization or selected users), so not everyone has to repeat OAuth.

 

Duplicates and conflicts

  • Avoid duplicates — typical option: contacts recognized by email, to avoid duplicates in the address book.
  • In case of conflict — choose whether Shopify or Mokapen wins when the same record was modified on both sides.

 

Automatic vs manual sync

With automatic sync active, updates (and webhooks) keep data aligned; you can still launch a manual synchronization for the initial historical load. Before syncing, check the data processing/sharing authorization required on the page.

 

Recommended flow

  1. Connect the store and verify Connected account.
  2. Set sync direction (for most cases: Toward Mokapen only or Both if you want to update Shopify products from Mokapen).
  3. Configure duplicates/conflicts and sharing.
  4. Authorize and launch the first sync (may take time on large catalogs).
  5. Check in Mokapen: Contacts, Products (variants/qty), Orders.
  6. Keep webhooks active: new orders and customer/product updates will arrive without relaunching everything each time.

 

Disconnect

From Integrations → Shopify → disconnect. In the modal you can choose whether to keep contacts, orders, and products already imported in Mokapen, or handle them according to the options offered. After disconnecting, webhooks stop updating; data already in the CRM remains if you chose to keep it. You can also revoke the app from the Shopify panel.

 

Common issues

  • Invalid store name — use the *.myshopify.com subdomain, not just the custom storefront domain.
  • Button blocked / upgrade — an appropriate Premium plan for e-commerce is required.
  • Orders not in Opportunities — that is correct: they go in Orders. Open Sales → Orders.
  • Product quantity — comes from Shopify variant quantity; not a full WMS.
  • Cart reports / analytics — if they show «Coming soon» on the page, they are not operational yet.
  • Expired token / sync stopped — disconnect and reconnect; verify the app was not uninstalled from Shopify.

 

Frequently asked questions

Q: Where do I find the store URL?

A: In the Shopify Admin dashboard address bar: it ends with myshopify.com.

 

Q: Do Shopify orders become opportunities?

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

 

Q: Can I update Shopify products from Mokapen?

A: Yes, with a sync direction that includes export and the integration active: products (variants) can be sent/updated on the store.

 

Q: Do contacts also update from Mokapen to Shopify?

A: Import and webhooks bring Shopify customers into the CRM. Automatic contact export is not the main path today (unlike products): verify on your plan/environment after connecting.

 

Q: Do I need WooCommerce alongside Shopify?

A: No: they are two alternative e-commerce integrations. Use Shopify if your store is on Shopify; see the WooCommerce guide if you use WordPress/Woo.

Need help?