From checkout to customer to campaign, in one database

Orders sync on checkout, status change, admin edit and refund, idempotently, so re-syncing never duplicates. Each order becomes a ledger record — order number, status, total, currency, items, payment method, billing country, dates — and a deal in an auto-created Orders pipeline whose stages mirror WooCommerce statuses.

Every customer becomes a CRM contact carrying lifetime value and a configurable RFM segment — New, Repeat, VIP or At-risk — computed from their actual order history, not a manual tag someone forgets to update.

Revenue, average order value, repeat-purchase rate and top products sit on a dedicated store dashboard, pulled from synced order data rather than a separate analytics subscription.

Beyond the order total, Stillpoint captures gross subtotal, discounts, tax, shipping, partial refunds, coupons used, category, brand, variant and SKU, unit cost when your store records it, store or sales channel, and UTM parameters where present. That detail is what lets reporting layer gross sales down to net sales down to total sales, instead of showing one flattened number.

An at-risk segment or an abandoned WooCommerce checkout can create a follow-up task for a rep — a person reaching out, not a generic discount blast — so recovery is a workflow rather than a one-off campaign someone remembers to send.

Automations can react to a segment change or an order event by creating a task, a work item, or a whole project from a template — a VIP customer's custom order becoming a production project the moment it is placed, for example.

Journeys and segments are built from actual purchase behaviour rather than form fills alone. Delivery of the email itself goes out through a real send adapter — SendGrid, Mailgun, Postmark, Amazon SES via SMTP, capped direct SMTP, or a FluentCRM handoff — because Stillpoint does not run its own outbound bulk mail infrastructure.