The CRM your WooCommerce store actually needs

Plug a typical WordPress CRM into WooCommerce and you get a list of buyers with tags on them. That is useful for sending a newsletter, and close to useless for running a commercial operation, because it throws away the two things that actually matter: what a customer is worth, and what should happen next.

Stillpoint takes the opposite view. An order is a commercial event, so it belongs in a pipeline with a stage, a value and an owner — exactly like a B2B deal. That single decision means your store data shows up in the same forecast, the same reports and the same follow-up queue as the rest of your revenue, instead of living in a parallel marketing world.

The practical payoff: you can see revenue at risk, identify who is worth phoning, and have the CRM create the follow-up task itself rather than hoping somebody notices a lapsed VIP customer.

Orders sync as they happen — on checkout, on any status change, on an admin edit in WooCommerce, and on refund. There is no nightly job to wait for and nothing to press.

Each order becomes two things at once. First, a record in a dedicated orders ledger that holds the commercial detail and line items. Second, a deal in an auto-created "Orders" pipeline whose stages mirror your WooCommerce statuses: Pending payment, Failed, On hold, Processing, Completed, Cancelled and Refunded. Completed maps to won; cancelled and refunded map to lost. Move an order in WooCommerce and the deal follows.

Sync is idempotent. Re-syncing an order, re-running a backfill, or an admin saving the same order three times updates the existing records rather than creating duplicates.

Capturing discounts, tax, shipping and refunds as their own fields — instead of just a single order total — is what makes true gross → net → total sales layering possible in reporting: gross sales, minus discounts and refunds, minus tax, equals what actually reaches the business. Gross profit and margin are a different question, though, and an honest one: they need a real unit cost, and a unit cost is only as good as what your store actually records against each product. Where cost data is not being recorded, the report says "requires cost data" rather than rendering a silent, misleading zero. None of this extends into cart-abandonment or website-conversion analytics, ROAS, CAC, MER or multi-touch attribution — Stillpoint reports on orders that exist, not on marketing spend or the browsing sessions that never became one.

Every order is matched to a person. Stillpoint matches on email address first, falling back to phone number where an email is missing. If no match exists the contact is created; if a match exists it is enriched with anything new the order carries — a phone number, a billing country, a company name.

The result is one contact record per human being, whether they bought through the store, arrived through a website form, or were added by a rep after a phone call. Their orders, deals, quotes, notes and email history sit on the same timeline.

For every customer Stillpoint maintains total spent, order count, average order value, and first and last order dates. From those it assigns an automatic segment, and the logic is deliberately plain rather than a scoring black box:

All three thresholds — VIP spend, VIP order count and at-risk days — are configurable, so the segments mean something in your business rather than in a vendor's average. A R50,000 furniture customer and a $30 coffee customer should not share a definition of VIP. Which order statuses count as revenue is configurable too, defaulting to processing plus completed.

The dashboard answers the questions a store owner actually asks on a Monday morning: is revenue up, are people coming back, and who needs attention. Everything on it respects your revenue-status configuration, so the totals reconcile with your own accounting view of the store.

Knowing a customer is at risk is worth nothing if nobody follows up. A daily background scan turns the insight into work: it creates follow-up tasks for at-risk customers, and for unpaid or failed checkouts older than the number of hours you choose.

Crucially it does not spam your team. The scan never creates a second open task for a target that already has one outstanding, so a customer who has been at risk for three months produces one task, not ninety. You can also run the scan on demand after changing your thresholds.

Because these are ordinary CRM follow-ups, they appear on the dashboard, in the assignee's queue and in the ICS calendar feed alongside everything else.

A CRM that only knows about orders placed after installation cannot tell you who your best customers are. Backfill imports your entire existing order history in batches, so segments, lifetime value and revenue-by-month are correct from day one.

It runs in batches specifically so it works on shared hosting without hitting a timeout, and because sync is idempotent you can safely re-run it if a batch is interrupted.

Orders are events, and events can trigger work. An order syncing, an order total crossing a threshold you set, or a customer's segment changing (moving into VIP or At-risk, for instance) can each fire an automation: create a work item on a fulfilment board, spin up a project from a template for a large or complex order, create a CRM follow-up for the account owner, send an internal notification, or fire a webhook out to another system.

These commerce triggers run through the same automation engine as the rest of Stillpoint, so they carry the same idempotency guarantee: a webhook retry or a duplicate sync event cannot make the same automation fire twice for the same order. See Automations for the full list of triggers, conditions and actions, and Reporting & Analytics for the commerce report templates that use the same order data.

WooCommerce is the native path, but it is not the only one. A token-protected JSON intake endpoint accepts a normalised order payload from any store: a headless storefront, a custom checkout, or another platform pushed through a small middleware step.

Those orders behave identically once inside — same ledger, same contact matching, same lifetime value and segment logic, same win-back scan. See the full feature documentation for the API and webhook detail, and getting started for the setup steps.

For report templates built specifically around commerce data — revenue layering, RFM breakdowns, top products and more — see Reporting & Analytics. And if you want to see how the whole ecommerce suite fits an agency running client stores, or a brand running its own, visit Ecommerce brands.