Klaviyo integration for wholesale Shopify stores: RevLogic intelligence on every profile

Why a wholesale store needs more than the standard Klaviyo Shopify integration

Klaviyo’s Shopify integration is excellent at what it was built for: orders, products, browse activity, and the consumer email flows that follow from them. What it doesn’t know is anything a wholesale sales team would recognise as account intelligence.

It can’t tell you that an account is 12 days past its usual reorder point. It has no idea which customers are key accounts your reps are phoning this week, so nothing stops a 15%-off campaign landing on a buyer mid-negotiation. Its predictive “expected date of next order” is tuned for consumer stores with thousands of similar shoppers and needs a minimum volume of history before it switches on, which is the wrong shape for a distributor with 300 accounts that each order on their own rhythm.

RevLogic already computes all of that from your Shopify order history. The Klaviyo integration hands it to Klaviyo as profile properties, so your B2B email marketing runs on the same intelligence your sales team calls from.

Seven RevLogic properties on every Klaviyo profile

Connect Klaviyo in RevLogic Settings, turn on the push, and RevLogic keeps these custom properties current on each customer’s Klaviyo profile, matched by email:

They’re typed properly. The health score is a number you can filter with greater-than or less-than. The two dates are real date properties, written at noon so a date-triggered flow doesn’t fire a day early for anyone west of Greenwich. Key account is a real boolean, not a string you have to match by spelling.

These are the same values as the ones on the RevLogic dashboard: the health score your reps sort by, the churn risk and winback status that puts an account on the call list, and the key-account flag your team can set to Always or Never on the customer card. A Klaviyo segment and a RevLogic call list never disagree about who is at risk.

Klaviyo segments and flows worth building on them

Every one of these is a Properties about someone condition in Klaviyo’s segment builder. No CSV imports, no tag spelling to get right.

Keep automated email off your key accounts

The first thing most teams do, and it works the other way round from a normal segment: you want these people out of the send. Add a flow filter to your automated flows, or the same condition on a campaign segment:

• revlogic_key_account equals false

Your automated email now skips your most important accounts, and a salesperson calls them instead. If your sales team owns winback calls too, add revlogic_status does not equal winback.

A reorder reminder that lands before they are due

This is the flow a wholesale store can’t build from the standard integration. Trigger a date-property flow off revlogic_expected_reorder_date with an offset of a few days before, and a light-touch replenishment email reaches the buyer the week they would normally order. Because the date is per-account, a customer on a six-week cycle and one on a quarterly cycle each get it at the right moment.

RevLogic clears the date for any customer it can no longer predict, such as one with a single order, so the flow never fires on a guess.

A Klaviyo winback flow that clears itself

Segment on revlogic_status equals winback and keep the message light, so it supports the call rather than competing with it. When the customer orders again, RevLogic moves them back to on-track and they drop out of the segment within minutes. Nobody who has just placed an order keeps receiving “we miss you” email.

Growing and shrinking accounts

Two more worth a flow each:

• revlogic_trend equals shrinking: a check-in while there’s still time to ask what changed. The trend compares an account’s recent stretch against the one before it, sized to how often that account orders, so a frequent buyer easing off is caught within weeks.
• revlogic_trend equals growing: the audience for a new-range announcement, because these accounts are already buying more.

Health-score bands

revlogic_health_score is less than 40 gives you a dynamic segment of accounts that need attention. Pair it with revlogic_revenue_tier equals whale and you have the short list a sales manager wants to see before anyone else does.

How it stays current

• Property changes reach Klaviyo in about 15–20 minutes. RevLogic sends within a couple of minutes; Klaviyo then re-evaluates segments on its own schedule.
• The first push covers every customer RevLogic can reach. After that, only changes are sent. A quiet week is a quiet week in Klaviyo too.
• No Shopify sync in between. The properties go straight from RevLogic to Klaviyo, so they don’t depend on a tag being written to Shopify first and picked up later.
• B2B company locations are combined the way a salesperson would. When several locations order under one buyer’s email, that buyer’s profile gets the most at-risk status, the lowest health score, a revenue tier from their combined spend, and the earliest expected reorder date. See native Shopify B2B.

Connecting takes one click, and writes nothing until you say so

Open Settings in RevLogic, find the Klaviyo card, and click Connect Klaviyo. Klaviyo’s approval screen opens in a new tab; approve it and you land back in Settings. You can also start from RevLogic’s listing in Klaviyo’s integrations directory.

Connecting is the first switch. The property push is the second, and RevLogic asks before turning it on: how many customers it can reach, how many it can’t (walk-in and phone customers with no email never reach Klaviyo), and that profiles may be created for customers Klaviyo doesn’t know yet. The card then shows Sending or Connected · not sending at a glance.

Turn the push off and the values already in Klaviyo stay as they are. Disconnect stops the push, clears the expected reorder date so date flows stop firing, and revokes RevLogic’s access. The other six properties are yours to keep.

What RevLogic never does in Klaviyo

Being straight about the boundary, because this is your customer list:

• Never sends email from your account, and never adds, subscribes, or unsubscribes anyone.
• Never reads your lists, segments, flows, or campaign data. The only read is the status of the batches RevLogic itself sent.
• Never writes an empty value. A property RevLogic can’t state is removed, not blanked, so a date property stays a date property.

Everything it reads and writes, in Shopify and in Klaviyo, is listed in What RevLogic can access.

Prefer tags? That route still works

If you’d rather not connect a second app, or you want the same statuses visible in the Shopify admin and in Shopify Flow, RevLogic can maintain Shopify customer tags instead: RevLogic Key Account, RevLogic Winback, RevLogic Growing, and RevLogic Shrinking. Klaviyo’s own Shopify integration syncs customer tags into the Shopify Tags property, so a segment on Shopify Tags contains RevLogic Key Account needs nothing else.

Pick one route. The connected properties are richer and faster; the tags need no connection. Building segments on both means two segments that disagree for a few minutes at a time. The tag route is documented in Build Klaviyo segments from RevLogic statuses.