Private Store
Building a controlled digital outlet.

The customer-group objectives connected excess-inventory distribution with outlet customer acquisition, retention, reactivation and trade-up or trade-across. Account-based access needed to support that commercial purpose without losing control of who entered the gated environment.

Customers registered through in-store email capture, then received source-code links by email or SMS, typically after about three weeks. Recurring access through an eligible Ralph Lauren account addressed recognition, navigation and activation together.

A customer could qualify through a store sign-up, purchase full-price and Private Store products in the same basket, or later return an item. The implementation needed to preserve what qualified the customer and how each purchase should be reported across the connected systems.

The business rules also had to address customer classification: a PFS customer shopping on RLE could move into the RLE business unit in Zeta while a separate Rapp data-container flag preserved Private Store status. The required hierarchy had to account for that distinction.

I kept the initial scope focused on the UK and EMEA and aligned implementation around customer eligibility, account access and reporting. I led scope tradeoffs, estimating, vendor coordination and budget planning, securing approval for an implementation plan spanning approximately 15 weeks.

NA and APAC were outside the initial MVP scope. The plan retained the existing Private Store pages, sign-up and notification processes, while adding the access and feed requirements needed for account-based entry.

Early planning targeted access within 24 hours of email capture. The implementation plan allowed a two-to-three-day interval between sign-up and customer-group membership.

For the account journey, an eligible customer’s sign-in or registration should reveal Private Store in navigation. The MVP proposal retained limited acquisition source codes as a separate exception, with account creation or sign-in required at checkout even when the basket contained full-price items.

I sequenced the focused UK/EMEA access scope with the broader customer-group capability that followed and launched as tiered experiences. The design connected eligibility and reassignment rules with Lux and Premium experiences, keeping the initial MVP distinct from the broader capability.

Customer-group rules connected purchase activity and recency with eligibility, reassignment and access across customer data, commerce and communications.

The entitlement contract assigned eligibility to Zeta/GCD and specified a daily CSV with email address and entitlement flag. A one-time migration covered active eligible customers only, with CRM defining active. SFCC used email matching, a profile attribute and dynamic customer-group membership to translate that data into account access.

On account creation, the requirement was to recognize eligible sign-ups by email address and add the account to the appropriate customer group. On sign-in, membership controlled gated navigation. I also defined access grant and revocation and the edge cases that could interrupt them: changed emails, duplicate matches and delayed feeds.

Mixed baskets required an explicit distinction between order-level and order-line classification. I led requirements to separate full-price and Private Store purchases and preserve the original classification through returns, supporting consistent downstream reporting in Snowflake.

The reporting requirements called for two item-order-level attributes: the product’s assortment usage flag and the environment from which it was sold. They distinguished full-price, Private Store and price-establishment assortment states. The transaction association had to record the product’s classification when sold, and a return had to retain the value from the original demand order.

Downstream consumers needed different levels of detail. BI required item-level product and environment attributes, stored in OMS and published into reporting. Zeta used order-header classification to distinguish PFS, RLE and mixed baskets. The plan called for OMS and MBS feed updates to carry the required data.

I sequenced dependencies across Zeta, SFCC, Snowflake and customer communications so the eligibility feed, commerce behavior and reporting could be delivered coherently. Account-creation and acquisition events also needed to retain the appropriate business-unit and Private Store-access flags used for marketing.

The reporting work included marketing entry points and gated-environment visits and conversion. Measurement design and attribution for products exposed in both environments remained open for further discovery. Analytics tagging and report creation were outside the implementation estimate; a historical load and Enterprise Planning inventory requirements were outside the reporting scope.

The approximately 15-week proposal placed requirements and technical design ahead of development, SIT/UAT and go-live. Its explicit dependencies were agreed business rules with Zeta and Ralph Lauren architecture, a sample entitlement CSV, and then a working feed containing the customer email and entitlement flag.

As global product lead, I led scope through delivery and coordinated UAT, release readiness and cross-functional work. The journey roster brought together 17 named participants across 12 staffed functions, with architecture, development and QA identified as additional delivery workstreams.

Release planning had to address a sequencing risk: if gated access launched before its outbound reporting feeds, the intervening demand, fulfillment and traffic data would need to be captured for later retransmission. Delivering the feeds concurrently would avoid that gap.

The release sequence and any retransmission requirement remained delivery dependencies to resolve. A general historical load was outside the reporting scope.

The implementation proposal estimated $97,702 across offshore senior SFCC development ($28,408), SFCC development ($15,120), QA leadership ($19,008), product/project management at 50% allocation ($9,216), and a local technical lead at 25% allocation ($25,950). The other offshore roles were allocated at 100%.

The old kickoff R24.02/R24.03 schedule was proposed. Planning connected requirements, feed readiness, UAT and outbound reporting dependencies rather than establishing an actual production date.

As global product lead, I took ownership of the stalled PFS Gated initiative, aligned the cross-functional teams and moved product scope through delivery. The tiered experience functionality launched, giving Private Store a customer-group framework for differentiated shopping experiences. The work established a focused UK/EMEA MVP and aligned integration requirements across customer eligibility, business-unit classification, commerce behavior and downstream reporting.

The commercial case carried a $1M–$5M annual EMEA revenue target; the implementation proposal was approximately 15 weeks at an estimated $97,702.

The lesson was to treat access, classification and communication as related but distinct product decisions. Sequencing the focused MVP and broader tiered customer-group capability kept the delivery path executable.