Skip to content

Shopify Dude Fix

Shopify customers/enable Webhook Suddenly Fires on First Sign-In? Fix Your Welcome and Loyalty Triggers

Since October 28, 2026, first sign-in to new customer accounts sets Customer.state ENABLED and emits enable/update webhooks; prior users were backfilled silently.

Quick answer: Since Shopify’s October 28, 2026 change, a customer’s first sign-in to customer accounts sets Customer.state to ENABLED and emits customers/enable and customers/update webhooks. If your integration sends welcome email, grants loyalty points, or provisions access on those events, verify that a first sign-in—not merely a record creation—is the business event you intended.
On this page

What changed for new customer accounts

Previously, customers signing in through the newer customer accounts could remain DISABLED in the Admin API. That made Liquid customer.has_account false even after a successful sign-in. Shopify now enables the customer on first sign-in, whether through email code, Shop, Google, Facebook, Apple, or a third-party identity provider. This brings the state transition closer to legacy customer-account activation.

The backfill is the trap

Shopify also set customers who had signed in between May 27, 2024 and October 28, 2026 to ENABLED in a one-time update. That backfill emitted no enable or update webhooks and did not consistently modify updated_at. A webhook-only CRM sync may therefore miss customers whose state is now enabled. Query Customer.state for reconciliation rather than treating webhook history or modification timestamps as complete evidence.

Separate account state from marketing eligibility

Audit flows that consume customers/enable, customers/update, Events API customer state changes, and Liquid customer.has_account. Account enabled is not equivalent to marketing consent, a new customer record, or a first purchase. Do not send promotional email based on activation alone. Make welcome and loyalty actions idempotent by customer ID and the intended milestone.

// Pseudocode: protect against duplicate onboarding
if (customer.state === 'ENABLED' &&
    !alreadyProcessed(customer.id, 'first-sign-in-onboarding')) {
  // Verify your business eligibility and consent rules first.
  processEligibleOnboarding(customer.id);
  markProcessed(customer.id, 'first-sign-in-onboarding');
}

Reconcile existing customers

Build a one-time audit of current customer states against your CRM or loyalty records. Decide separately whether historical first sign-ins deserve backfilled benefits; don’t replay every welcome event automatically. Keep an audit trail of reconciled customer IDs and avoid treating updated_at as a reliable detector for Shopify’s silent state backfill.

Common misunderstanding: A customers/enable event always means a newly created customer or explicit marketing opt-in. It can now mean the first successful sign-in to an existing customer record.

How to test this

  1. Create a new test customer record that has not signed in; record its initial state.
  2. Sign in to customer accounts using a supported method and confirm state becomes ENABLED.
  3. Inspect customers/enable and customers/update deliveries and confirm downstream jobs run once.
  4. Sign in again; verify your onboarding action is not duplicated.
  5. Reconcile a previously signed-in customer by querying Customer.state, not relying on webhooks or updated_at.
  6. Confirm any marketing sends separately respect consent.