A Checklist for Segment or RudderStack in Omnichannel Retail

Before anything else, confirm your point-of-sale system can attach a loyalty ID, email, or phone number to an in-store transaction and send that to whichever CDP you pick. If your POS vendor doesn't support this natively, both Segment and RudderStack become far less useful for omnichannel identity resolution, since neither can invent a link between an anonymous in-store sale and an online browsing session.

Pitfall: some POS systems only expose transaction totals through nightly batch exports, not real-time events. If that's your setup, expect a lag of up to a day before in-store purchases show up in your unified customer profile, which limits same-day retargeting suppression.

Start this conversation with your POS vendor before you sign a contract with either CDP, since discovering a batch-only limitation after implementation begins usually means renegotiating the whole rollout timeline.

A BOPIS order should fire an order-completed event online and a separate fulfillment event when the customer actually picks it up, since the gap between those two moments matters for measuring whether your in-store pickup experience is fast enough. Both platforms can capture this if your systems emit both events distinctly; the risk is a retailer treating the online order as the only event that matters and losing visibility into pickup friction entirely.

Pitfall: if your fulfillment system doesn't send a distinct pickup-completed event, you'll never know how many BOPIS orders sat uncollected, which is a real revenue leak most retailers don't measure.

Once both events are wired up correctly, the time between them becomes a genuinely useful operational metric on its own, not just a data-quality checkbox, since a store consistently slow to fulfill pickup orders is losing repeat BOPIS customers to a competitor down the street.

A return processed at a different location than the original purchase needs to be matched back to the original order in your CDP, or your customer lifetime value numbers will overcount revenue that later got refunded. This requires your return system to reference the original order ID, not just record a standalone return transaction.

Pitfall: without that link, a customer who buys online and returns in-store shows up as having made two unrelated transactions in your data, inflating both revenue and purchase frequency metrics.

This matters most for retailers with a generous cross-channel return policy, since a high return rate against unlinked transactions can make a genuinely healthy customer base look like it's buying and returning constantly, when it's really the same handful of orders being counted twice.

Most successful omnichannel retailers use their loyalty program number as the consistent identifier across web, app, and in-store, since it's the one ID a customer actively provides at checkout regardless of channel. Both Segment and RudderStack can use a loyalty ID as the primary user identifier, but only if your loyalty program is actually asked for at every point of sale, not just online.

Pitfall: a loyalty program with low in-store adoption, because cashiers don't consistently ask for it, undermines identity resolution no matter which CDP you pick.

Identity resolution isn't a one-time setup, it's an ongoing responsibility, because a new POS terminal model, a loyalty program migration, or a new store opening can each quietly break the link between channels if nobody's watching. Assign a named owner, usually whoever runs retail operations or marketing analytics, who checks a sample of customer profiles monthly to confirm cross-channel matching is still working.

Pitfall: treating identity resolution as a project that finishes at launch, rather than a system that needs periodic checking, is the single most common reason a retailer's unified customer view degrades silently over a year or two.

Get clear answers to these questions before you commit:

• Can your POS attach a loyalty ID, email or phone number to in-store transactions and pass it to the CDP?
• Does a buy-online-pickup-in-store order create an order-completed event online and a separate event at pickup?
• Do returns reference the original order ID, so refunded revenue doesn't inflate customer lifetime value?
• Is your loyalty number the consistent identifier across web, app and in-store?
• Who owns identity resolution once it's live, by name?