Australia's Only Premier Laravel Partner Brisbane-based, Australia-wide

Klaviyo integration for custom ecommerce and subscription platforms

Pixel connects custom Laravel platforms to Klaviyo, so your marketing team gets the events, customer profiles and product data that a Shopify store would send by default, plus the ones only your business has. We have built this on several production platforms, including our own.

Start with a Technical Blueprint
Our Clients
chemist-warehouse-logo
hellofresh-logo
absolute-domestics-logo
factor-logo
youfoodz-logo
trilogy-care-logo
nourishd-logo
canary-logo
astrid-logo
cannabis-warehouse-logo
dress-for-dignity-logo
cannareviews-logo

A Klaviyo integration sends events, customer profiles and product data from a custom platform to Klaviyo, so email and SMS flows can be triggered by what customers actually do. It is for businesses that have moved off Shopify, or never fitted it, and do not want to lose their marketing automation. Pixel scopes the integration in a fixed-fee Technical Blueprint and quotes it as a fixed price.

The problem

What You Lose When Your Platform Is Not Shopify

Klaviyo is built around the events a standard store sends. A custom platform sends nothing until someone builds it, and marketing notices on day one.

01

Flows with nothing to trigger them

Abandoned cart, post-purchase and win-back flows all depend on events. Without them the flows exist but never fire.

02

Segments built on stale data

If lifetime spend, order count or subscription status are not kept up to date on the profile, segments quietly go wrong.

03

Events your business has and Shopify does not

A paused subscription, an approved account, a document about to expire. These are often the most valuable triggers, and no connector knows about them.

04

Emails with no products in them

Product recommendations and dynamic blocks need a catalogue feed. A custom platform has to publish one.

05

Marketing to people who have left

When a customer deletes their account, Klaviyo needs to be told to stop.

What we send to Klaviyo

These are the parts of a Klaviyo integration we have built in production.

Order events

Placed Order and Ordered Product with full line items, plus order packed, delivered, refunded, edited and cancelled.

Cart and checkout events

Added to cart, checkout started and abandoned cart, sent from the server so ad blockers do not drop them.

Subscription events

Subscription created, paused, resumed and cancelled, failed payments and upcoming deliveries.

Customer profiles

Custom properties such as totals spent and earned, account type and acquisition source, kept in sync as they change.

Catalogue feeds

A product or listings feed that Klaviyo reads, so emails can show live items from your platform.

Consent and suppression

Email and SMS subscription at sign-up, added to the right list, and suppression when an account is deleted.

In production

Three platforms, three kinds of event

Subscription meal delivery. For Nourish'd, the platform sends the standard order events and the ones that matter to a subscription business: paused, resumed, cancelled, payment failed, delivery coming up. When the courier confirms a delivery, Klaviyo receives an event with the proof-of-delivery link. Funded-care customers have their own events for quotes, invoices and signed service agreements.

A marketplace. On Rethread, our second-hand school uniform marketplace, a person can be a buyer, a seller or both. Events cover a listing being started, published and sold, an order placed or cancelled, and a payout becoming due. The profile carries buyer and seller totals, so the marketing team can write to people who have sold but never bought, or the reverse.

Wholesale ordering. On a wholesale ordering platform for pharmacies, the events are operational: account approved, a compliance document approved or about to expire, a product back in stock, a loyalty tier reached. Scheduled jobs send win-back and reminder events each morning.

In each case the list of events was agreed with the marketing team first. The most useful ones were specific to the business.

How We Build It

Marketing events should never slow down or break a checkout.

01

Server-side

Events are sent from the server through Klaviyo's API, not from the browser, so they are complete and reliable.

02

Queued

Every event and profile update is a background job. If Klaviyo is slow, your customer never notices.

03

Retried

Failed jobs are retried with a delay, and errors are reported to Sentry.

04

Scheduled triggers

Time-based events such as abandoned cart, upcoming delivery and win-back run from scheduled commands.

05

Bulk sync

A command re-syncs every profile, with a dry-run mode, for when a new property is added.

06

Environment aware

Test and local environments do not send events, so staging never emails a real customer.

Custom or connector

When Klaviyo's own integrations are enough

If your store runs on Shopify, use Klaviyo's Shopify integration. It is very good and there is nothing for us to build.

A custom integration is for platforms Klaviyo does not connect to out of the box, which includes anything built specifically for your business. It is also how you get events and profile properties that no standard store has.

If you are deciding whether to leave Shopify at all, our Shopify to custom software page covers when that makes sense. Keeping Klaviyo working is part of every migration we do.

Klaviyo in production

Nourish'd

A custom meal delivery platform managing subscriptions, funded-care billing, fulfilment, and operational reporting across three customer segments.

30+

Operational Reports

199

Support at Home Providers

3

Customer Segments

Read the Nourish'd case study →
FAQ

Klaviyo integration
FAQs

Couldn't find the answer you were looking for? No worries, get in touch with us.

Contact Us

Can a custom platform work with Klaviyo as well as Shopify does?

chevron-down

Yes. Klaviyo's API accepts the same events a Shopify store sends, and a custom platform can send additional ones. Flows and segments work the same way once the events arrive.

Which events should we send?

chevron-down

Start with Placed Order, Ordered Product, checkout started and abandoned cart, because most flows depend on them. Then add the events specific to your business. We agree the list with your marketing team before building.

Will our existing Klaviyo flows keep working after we leave Shopify?

chevron-down

They can. We match the event names and structure your flows expect, so most of them continue with little or no change. Any that relied on Shopify-only data are identified during scoping.

Can you sync custom profile properties?

chevron-down

Yes. Properties such as lifetime spend, subscription status, account type or acquisition source are updated on the profile whenever they change, and can be re-synced in bulk.

Does it handle SMS consent as well as email?

chevron-down

Yes. Email and SMS consent collected at sign-up is passed to Klaviyo with the profile, and the customer is added to the right list.

What happens if Klaviyo is unavailable?

chevron-down

Events wait in the queue and are retried. Your platform carries on taking orders in the meantime.

Agree the events before the build starts

A Technical Blueprint lists every event and profile property your marketing team needs, with a fixed price to build it.

Book a Technical Blueprint

$2,990 inc. GST · credited against your first invoice if you build with us

Related integrations

Discovery Call

One call.
We'll both know.

20 minutes to walk through your project, ask the hard questions, and work out honestly if we're the right team for it.

  • One call per day - it gets our full attention
  • Australia's only Laravel Premier Partner
  • Trusted by Chemist Warehouse, HelloFresh and Youfoodz
  • Senior engineers only - no juniors on your project
  • Brisbane-based, onshore team

Press Esc to close  ·  B to reopen