There’s a version of loyalty that lives almost entirely on the storefront.

Someone buys something. They earn value for that purchase. They come back later and use it.

Nice. Clean. Easy enough.

And honestly, for some brands, that may be exactly what they need. But businesses rarely stay that simple. A return happens days later. Only part of an order actually ships. The customer paid a different price through another channel. Inventory changed what could be fulfilled. Maybe the person buying from you online is also buying somewhere else entirely.

None of those things are really “loyalty events.” But every one of them can change what the loyalty program should do. And that is where things start getting interesting. Because somewhere in the business, those changes are already being recorded. The question is whether loyalty knows about them.

The program can only react to what it can see

This is probably the simplest way I can explain the problem. If your loyalty program sees a $500 purchase, it acts on a $500 purchase.

Makes sense, right?

But what if half of it gets returned a week later? What if part of it never ships? What if the price the customer actually paid was determined somewhere else? What if that transaction is just one piece of a much bigger relationship with the customer?

The program cannot magically know any of that. It can only do things based on the information it has. And this is where a lightweight plug-in can start running out of context. Not because the plug-in is bad. Not because the storefront data is useless.

It is just one piece of what happened.

And once the business starts getting more complicated, that missing context starts to matter a lot more.

This is where I started getting really interested

When I first saw what was possible when loyalty was connected more deeply into the systems already running the business, my immediate reaction was, “Holy wah. Where was this when I needed it?!”

Because I have lived the alternative.

Downloading report after report from different systems. Trying to figure out which fields match. Cleaning up data. Merging files together. Building some absolutely unhinged Excel workbook just to get to one usable view of the customer.

And then doing it all over again the next time someone needed an answer.

Which, let’s be real here, is probably later that same day because someone thought it would be “neat” to see the data sliced a slightly different way.

If you have ever owned loyalty reporting, you know exactly what I mean.

It’s not that the data isn't there. It is. Somewhere.

That was never really the problem.

The problem was getting it together in a way that was actually useful.

Every Monday.

This is where the integration starts to matter

This is where platforms like Oracle NetSuite and Adobe Commerce become interesting to me. Not because it’s exciting to say two systems integrate. But because these are often the systems where the rest of the customer and transaction story already lives. Orders. Returns. Pricing. Inventory. Customer records. What actually shipped. What came back. What changed after the initial purchase.

The opportunity is to let the loyalty program operate with more of that same context.

In NetSuite, the correction already exists. The return authorization. The credit memo. The updated transaction record. Those records are sitting right there. The only question is whether loyalty ever sees that data.

In Adobe Commerce, it is the order's life after checkout. Shipped. Cancelled. Partially refunded. Again, all of it recorded. Again, the only question is whether the program is able to see it.

If a return happens, loyalty can respond. If part of an order is cancelled, loyalty can respond. If the business knows something important about the transaction that changes what the customer actually bought or paid, loyalty does not have to keep operating from the original storefront event like nothing changed.

That is a very different thing than simply putting a loyalty widget on a website.

And this is where pricing, inventory and finance sneak into the loyalty conversation

I know. Very exciting stuff.

But this is exactly why I think the conversation gets more interesting as a brand grows.

Take pricing. A lot of mid-market brands do not have one customer, buying one way, at one price. There may be wholesale pricing. Different account structures. Promotions. Channel-specific offers. Contract pricing.

And I am not suggesting your loyalty team suddenly needs to become experts in every pricing rule the business has.

Please, for your own sanity, do not do that to yourselves.

But the program does need enough context to know what actually happened. The same goes for inventory. Something being ordered does not always mean something was fulfilled exactly as expected. An item may be unavailable. Only part of the order may ship. Something may get cancelled later.

Again, those are not loyalty problems. Until the loyalty program is still rewarding the original transaction as though none of those things happened. Then they become loyalty problems pretty quickly.

Cue your CFO slapping a meeting on your calendar that already looks like a Tetris board.

We all know the rule that we should be friends with finance. And maybe you are. But I cannot say I know anyone who wants to sit in a room trying to explain why the loyalty numbers and the financial numbers are telling slightly different stories.

Because if I am going to defend the value of a loyalty program, I want to know the numbers underneath it are legit.

Not mostly right. Not right depending on which report we pulled or which direction the wind is blowing that day.

Just plain right.

I owe you an apology for the most jargon-y phrase in this article

Operationalizing data.

I know. But all I mean is making the data your business already has actually do something. That is it.

If the business knows a transaction changed, the loyalty program should be able to change with it. If the business knows more about the customer than what happened on the storefront, loyalty should be able to use that context when it matters.

And if loyalty knows something valuable about that customer, like their tier or available rewards, that information should not necessarily be trapped somewhere only the loyalty team can see it.

This is where integrations stop feeling like a technical checkbox and start becoming business enablement. Because the value is not the connection itself. The value is what the connection lets you do.

Of course, none of this is as easy as I just made it sound

Not only have I lived through this myself, I talk to enough people who are living it today to know the reality, and I can practically hear some of you from here as you are reading this.

Platform work is hard.

Proper planning and the technical architecture required to make sure everything flows the way it should takes time.

I see you, scrum masters, and your brilliant sprint planning.

Then you get to identity. Because connecting two systems is one thing. Getting those systems to agree that they are talking about the same person is another. Is the Amanda who ordered online the same Amanda who bought through another channel? What happens if the email addresses are different? What if only part of an order comes back? What if the customer used a promotion? What if the transaction changed after the loyalty program already acted on it?

This is where the edge cases live. I feel on edge just talking about it. And unfortunately, the edge cases are usually where you find out how good the integration really is.

This is the part I think gets missed

We tend to talk about integrations like they are logos on a partner page.

NetSuite. Adobe Commerce. Shopify.

Whatever else is in the stack.

But the logo is not the value. The value is how much more of the actual business the loyalty program can understand because that connection exists.

That is what starts separating a surface-level loyalty experience from a platform that can participate in how the business actually operates.

And I think that distinction matters more as brands grow. Because eventually the question stops being, “Can the loyalty program issue points when someone buys something?”

Of course it can!

The better question is whether the loyalty program still knows what actually happened after the rest of the business got involved.

Because that is where the customer story gets a lot more interesting.

About the author

Amanda Boshell is a Product Marketing Manager at TrueLoyal. She spent twelve years as a loyalty practitioner before moving to the platform side, across agency, tech, and retail, in roles spanning program operations, strategy, and marketing. She has sat on both sides of the table, as the operator running the program and as the buyer evaluating the platforms.