Connect Shopify to HubSpot

Shopify has the orders. HubSpot runs the marketing and, for many brands, a B2B or wholesale sales motion. Without a real link, HubSpot contacts have no order history, "high-value customer" is a guess, and the sales team quoting a wholesale deal cannot see the buyer's retail spend.

• Shopify customers become HubSpot contacts with lifetime spend, order count, first and last order date, and average order value as properties
• Orders land as a custom object associated to the contact, each with line items, discounts, and net revenue, so reports and lists work on real data
• An abandoned checkout creates or updates a contact and can enroll it in a recovery workflow, with the cart contents as properties
• Checkout marketing consent maps to the HubSpot subscription, so an opted-out buyer is never emailed

The order-to-CRM flow most teams turn on first.

A paid Shopify order updates the HubSpot contact and creates an order object

Triggered by Shopify's orders/paid webhook pointed at a Neblex endpoint, idempotent on the Shopify order ID.

1. 1Trigger: Shopify orders/paid webhook with the customer, line items, totals, discounts, and customer.email_marketing_consent.
2. 2Upsert contact: HubSpot Create or update contact keyed on lowercased email, setting name, and mapping the consent state to the marketing subscription (never a silent opt-in).
3. 3Idempotency: look for a HubSpot Shopify Order custom object record with this order ID. If found, update it; otherwise create it.
4. 4Order object: write the order object with order number, processed date, gross and net totals, discount, currency, and financial status, associated to the contact.
5. 5Line items: write each line as a line-item record or a JSON property, with SKU, quantity, and price.
6. 6Recompute properties: update the contact's total_spent, order_count, aov, first_order_date, and last_order_date from all order objects, and set a customer_tier from a threshold.

The starting map for the Shopify order and customer to HubSpot.

• Customers and spend. Customers become contacts with lifetime spend, order count, AOV, and tier as properties. (Shopify to HubSpot)
• Orders. Each order lands as a custom object with line items, discounts, net revenue, and financial status, associated to the contact. (Shopify to HubSpot)
• Abandoned checkouts. An abandoned checkout with an email creates or updates a contact and can enroll it in a recovery workflow. (Shopify to HubSpot)
• Segments back (optional). A HubSpot list membership such as "VIP" or "win-back" can write a Shopify customer tag for use in Shopify marketing and discounts. (HubSpot to Shopify)

The same controls apply to this sync as to every other Neblex workload.

• Ordered run log. Every sync records the Shopify object, the contact and order object it resolved to, and the properties written. Replay without re-enrolling workflows.
• Consent guard. The checkout consent state is read on every contact write and cannot be bypassed by a mapping change. An order is never treated as consent.
• Scoped access. Shopify uses a custom app token scoped to read orders, customers, and checkouts. HubSpot uses a private app scoped to contacts, the custom object, and workflow enrollment.
• Environments. Build against a Shopify development store and a HubSpot test account, then promote the same flow to production.