MiniCRM Sync for WooCommerce

By MiniCRM

50+ active installationsVersion 1.8.4

Synchronizes WooCommerce orders with MiniCRM, with optional subscription cards.

Description

The plugin synchronizes orders on the following events (when all required
options are filled in settings).

  • New orders created by your customers are synchronized.
  • Orders created or updated by administrators are synchronized. Orders are synchronized too, when an admin updates multiple orders with checkboxes.
  • Trashed/restored orders are synchronized with legacy storage and HPOS.
  • Manual sync submits the next selected number of orders in requests of at most 100 records, then stops. Keep the page open during a batch. Resume with Next batch or Continue batch; manual runs do not continue automatically in the background.
  • Live updates persist individual source IDs. Shutdown and each background worker handle at most 100 orders and, separately, 100 enabled subscriptions. Action Scheduler continues eligible overflow without requiring a full-shop sync.

The manual batch size defaults to 1,000 records and can be set between 1 and 10,000.
This counts actual source orders, without automatically exporting all their customers’ older orders.
The UI confirms submission to MiniCRM; check MiniCRM for asynchronous import errors.

Live queue status distinguishes ready, delayed, manual recovery, paused and
sending records. HTTP 429 rejections retry automatically after 1, 5, 15 and
60 minutes, respecting a longer Retry-After. The first attempt counts toward
the five-attempt limit; only affected IDs pause afterward. Timeouts, unknown
transport failures, 5xx, redirects and unexpected acknowledgements require a
targeted manual retry. Correct credentials/configuration or other 4xx errors
before retrying. Other ready records continue independently.

An administrator can retry up to 100 selected IDs from the settings page.
Capability, nonce and current row-version checks protect the operation; active
sending records cannot be restarted. Retry uses current source data and fresh
XML. An uncertain request’s earlier XML and nonce remain available until their
original expiry, at most six hours. Repeated submissions cannot guarantee
exactly-once CRM automation effects.

Background execution depends on Action Scheduler and WP-Cron/site traffic.
Queue entries use non-autoloaded WordPress options, with no new table or schema
upgrade. Deactivation preserves them; reactivation resumes eligible work while
manual/paused records still need administrator recovery. A full manual sync is
only the fallback for a legacy reconciliation notice whose affected IDs are
unknown. It does not clear an unrelated targeted live queue.

WooCommerce Subscriptions support is OFF by default. To enable it, configure a
separate generic MiniCRM module, a default status ID, and subscription field
mappings including the raw subscription status. Each subscription becomes its
own card named with the contact, product, billing cycle and available dates.
Renewal purchases remain ordinary orders; subscription cards do not add revenue.
Mapped empty dates clear previously exported dates. Disabling the feature keeps
existing MiniCRM cards. Payments and renewal scheduling remain in WooCommerce.

Known Issues

  1. SyncFeed submission does not confirm asynchronous import completion; review MiniCRM import errors.
  2. Permanent deletion does not delete MiniCRM cards. Cancel or trash subscriptions before permanently removing them if their final state must be exported.

Installation

  1. Upload the plugin files to the /wp-content/plugins/minicrm-sync-for-woocommerce directory, or install the plugin through the WordPress plugins screen directly.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress admin.
  3. Use the WooCommerce->Settings screen (Settings link on plugin too) and the “MiniCRM feed” section, to set your MiniCRM system’s details.
  4. You find your System ID in your browser’s address bar after logging in to your MiniCRM account. For example, if you see https://r3.minicrm.io/1234/#TodayView, then your System ID is 1234.
  5. You can generate an API Key in your MiniCRM account on the Settings(cogwheel)->System screen.
  6. To find out your Category ID, select the Webshop module in your MiniCRM account. Use the number followed by #!Project- in the address bar. For example, if you see https://r3.minicrm.io/1234/#!Project-21, then your Category ID is 21.

Changelog

1.8.4

  • Refresh inherited subscription variation SKUs after parent SKU changes, including WooCommerce product instance caching.
  • Reject swallowed HPOS source-query exceptions instead of falsely completing sync or exporting incomplete customer history; preserve valid cached empty results.
  • Preserve every consecutive WooCommerce and extra product option mapping line, including LF, CRLF and CR line endings.
  • Preserve literal XML special characters in billing and shipping address text without dropping ampersands or creating malformed XML.
  • Fix live queue status counts on MySQL by quoting reserved SQL aliases.
  • Validate the connecting proxy address before trusting the original client IP header; require an allowed MiniCRM source IP.
  • Export canonical Romanian county names regardless of the shop’s display language.
  • Normalize county codes and recognized stored names in shared order/subscription addresses.

1.8.2

  • Add optional last_order_date subscription mapping using WooCommerce’s Last Order Date in UTC.
  • Refresh the subscription card when a renewal order is created, including unpaid renewals.

1.8.1

  • Show newly saved settings immediately, including cleared subscription mappings.
  • Preserve sync controls through WooCommerce settings rendering so batch actions work.
  • Send feed error status codes through WordPress for compatibility with Studio.

1.8.0

  • Bounded, resumable manual sync with explicit batch controls and saved progress.
  • Export changed orders without loading each customer’s complete history.
  • Validate MiniCRM submission responses and show reconciliation notices.
  • Optional subscription cards with descriptive names and configurable mappings.
  • Handle HPOS trash/restore events.

  • Initial public release