Insider One AI Decisioning: What Replenit Adds

Replenit can add customer × SKU replenishment and coordination across retail lifecycle decisions when those jobs remain unresolved in an existing Insider One implementation. Use Insider One’s native AI capabilities when they already cover the decisions your team needs. Another layer earns its place through demonstrable additional capability and net commercial value, with clear ownership between decisioning and activation.

A refill reminder arrives after the customer has reordered. A promotion discounts a purchase they would have made anyway. A relevant cross-sell competes with a more urgent product need. These are the retail decisions an AI investment should help improve.

Replenit’s AI Decision Engine powers Maestro, its retail AI CRM manager. Maestro brings customer, product and order context into lifecycle decisions. In an agreed Insider implementation, Insider activates the selected eligible interaction. This brings product need, purchase history and competing opportunities into the same customer decision. The retailer can then measure commercial outcomes and the effort required to maintain those decisions.

L’Occitane achieved a 235% uplift in automation revenue with Replenit, while retaining Insider for activation and using data from its in-house ERP. Maestro’s replenishment decisions reached customers through the marketing stack L’Occitane already used.

What Insider One Already Does Natively

Agent One and AI Decisioning: Scope, Availability and Controls

Insider One already offers individual AI decisioning, choosing content, channel and send time for each user and learning from their responses. With Suppression enabled, the Decision Agent can withhold a message while the customer continues through the journey. It optimises each send independently rather than jointly optimising a multi-message sequence. [1]

The Architect Decision Agent is currently in beta, requires account enablement and supports non-transactional journeys. Confirm availability in your account before making it the baseline for a purchase decision. [2]

Agent One Teams coordinates decisions and execution across the customer lifecycle. The independent-send limit applies to the Decision Agent’s per-send optimisation, rather than the whole Agent One Teams system. [3]

Predictive Models and Product Recommendations Already in the Stack

Insider’s Next Best Channel uses machine learning to estimate individual engagement probabilities and choose a delivery channel. Its Smart Recommender includes behavioural, complementary-product and contextual recommendation approaches. [4]

A specialist should add a decision or operating benefit beyond these existing capabilities.

Replenishment Timing, Nested Data and Journey Priorities

Architect can already activate customer-specific replenishment timing. Wait Until Dynamic Time waits on an individual date/time event parameter; Wait for Some Time supports a dynamic duration from a numeric event parameter. Insider also supports nested Array of Objects for timing, conditions and personalisation. Values used as constant parameters are captured at journey entry, so they should not be assumed to refresh during the journey.

Its Journey Prioritization resolves competing journeys through configured ranks and eligibility mechanics. [5]

Distinguish three questions: who estimates product need, who selects the lifecycle action, and who delivers it? Native activation of an individual refill date establishes the third job; the source and quality of the underlying estimate still need checking. Missing public detail about a depletion model does not prove Insider lacks one.

When Insider One’s Native AI Is Enough

The Required Decision Is Already Covered

Stay native when enabled Insider capabilities can produce the required action, use sufficiently current context and apply the necessary controls at an acceptable operating cost.

Reliable refill dates, relevant recommendations and effective journey priorities may already cover a retailer’s needs. Another system earns its cost only through better outcomes or a material operating benefit.

An authored priority can be the right solution when it handles the retailer’s actual conflicts.

Your Existing Model Can Supply the Missing Signal

A prediction gap does not automatically require a new decisioning platform. Your data team may already estimate customer-level reorder timing and supply it to Architect.

Insider’s Upsert User Data API supports external attributes and events. Combined with native timing elements, this provides building blocks for using externally generated signals. [6]

Retain that arrangement when the model is reliable, monitored and economical to maintain. A prototype alone does not establish production readiness.

What Decision Would a Specialist Actually Add?

Personalisation, Prediction, Orchestration and Decisioning Are Different Jobs

These functions describe responsibilities, not mutually exclusive software categories:

Function	Retail question	Example
Personalisation	How should this experience appear?	Show the purchased shade and relevant product content.
Prediction	What is likely to happen?	Estimate when this customer may need another bottle.
Orchestration	How should interactions be coordinated?	Manage journey steps, waits, transitions and contact rules.
Decisioning / next-best action	Which eligible intervention, if any, should happen?	Choose a refill reminder over a cross-sell—or wait.
Execution	How is the selected intervention delivered?	Send an approved email through the engagement platform.

One platform can perform several of these jobs. Next-best action selects an eligible intervention under the retailer’s objectives and constraints, including delay or no contact.

Customer × SKU Need Is More Than a Refill Date

Customer × SKU replenishment estimates need for a particular person and product, potentially including the purchased variant, size and quantity. It connects purchase history with product context instead of treating every buyer as following the same interval.

For a first assessment, prioritise matching customer identifiers, dated order lines, exact SKU variants and quantities, and current catalogue context. The workflow also needs a defined source and freshness standard for stock, contact history and eligibility.

Sparse history, gifts, returns and subscriptions can make need harder to infer. Establish how uncertainty changes the action: wait, use a conservative fallback, or exclude the case until better information arrives. Product enrichment supplies context; it does not eliminate uncertainty or guarantee a reliable estimate.

At Escentual, Maestro reasons about consumption per SKU variant across replenishment, cross-sell and substitution workflows. The purchased size or format helps inform when a refill may be needed and which product to offer.

How Maestro Brings Retail Context Into the Action

Maestro uses customer, product and brand memory across replenishment, cross-sell and retention workflows. Our Data Enrichment adds product-use and consumption context, while the AI Decision Engine applies commercial controls such as discount ceilings and exclusions. Maestro weighs product need alongside previous purchases and competing opportunities, then passes the selected interaction to Insider under the agreed implementation.

Bringing these inputs together can help the team resolve competing campaigns through one action-selection process. Measure whether that changes outcomes or maintenance effort in your implementation; shared context is not exclusive to Replenit.

Refill, Cross-Sell, Promotion—or No Contact?

Prediction provides an input. Decisioning determines what to do with it.

Prem Kwapisz puts the relevance problem plainly: “What gets replies is relevance and timing, not personalisation.” His observation comes from B2B outreach. The useful retail application is to establish a reason to contact the customer before polishing the message: a beautifully personalised refill email is still unnecessary if the customer has already reordered.

A customer near a predicted refill window might still be a poor candidate for a reminder because they recently reordered, received another relevant contact or have an unresolved service issue. A complementary product might be appropriate later. A discount may be unnecessary.

Evaluate competing actions against customer need, objectives and constraints. High purchase propensity does not show that a message will cause an incremental purchase.

Native AI, a Specialist or an Internal Model: A Fair Buying Framework

Compare the Decision Job, Not the AI Label

There are three practical operating choices:

Native Insider One: use enabled AI capabilities and configured policies for action selection and activation. Your team owns configuration, contact rules and ongoing journey operations.
Replenit alongside Insider: assign Maestro a defined retail decisioning job, with an agreed handoff to Insider. Assess its customer-by-SKU context, competing-action choices and the added software and operating cost.
An internal model feeding Insider: supply a prediction—or action selection if your team builds it—to native activation. Your team remains responsible for data quality, model monitoring and production support.

Use equivalent underlying customer, order and product records, with the retailer’s strongest current enabled native approach as the comparator. Additional enrichment can legitimately be part of Replenit’s capability. Record material differences in enrichment, context, offers, available actions, execution and operating practice as part of the policy being tested. When several things change together, the result measures that combined policy; it should not be attributed solely to the decisioning algorithm.

Six Checks Before Adding a Decisioning Layer

Before buying, answer:

Can the current stack already produce the required decision?
Is the necessary customer, order and product context available and fresh?
Can the candidate demonstrate the additional job on representative cases?
Is there a clear action owner and feasible activation handoff?
Can you compare against the strongest current enabled native policy and document what changes?
Would the expected net value cover software and ongoing operating costs?

An independent architecture is not unique to Replenit. The decision job and its economics matter more than a longer feature list.

Data → Decision → Insider One Activation

Decide Who Owns the Action—and Who Optimises the Send

A specialist can select the retail action while Insider retains agreed send optimisation. Define ownership so two systems do not independently change the same offer, channel or contact plan.

One feature-specific check matters: enabling Insider’s Architect Send Time Optimization automatically enables Override Global Frequency Capping. Confirm the actual contact controls when retaining send optimisation; do not assume the ordinary global cap still applies. [7]

Use this operating loop to agree responsibilities for your implementation:

flowchart TD

D["Customer, order and product updates"] --> R["Designated decision owner"]

R -->|Selected action| I["Insider activation and agreed optimisation"]

R -->|No action| N["Record and reconsider later"]

I --> C["Final eligibility and delivery checks"]

C -->|Eligible| E["Deliver interaction"]

C -->|Context changed| N

E -->|Responses and new orders| D

Define the Handoff, Updates and Outcome Feedback

Agree which customer and product identifiers travel with the decision, when it becomes valid, when it expires and how a recent purchase or stock change updates or suppresses it. Establish ownership of retries, duplicates, failed matches and outcome feedback.

Replenit accepts customer, order and product inputs, enriches their context, selects actions and dispatches executable decisions. The Integration API Reference sets out these inputs and responsibilities. Marketing automation handles message consent and suppression at execution. Separately, Replenit’s GdprOptin processing-permission flag defaults to false: Replenit does not process, enrich or generate decisions when it is false. Valid and current consent must be handled upstream before data reaches the API. Permission for Replenit to process customer data and permission to deliver a message are separate responsibilities.

For European operations, include market-specific catalogue availability, language and channel permissions in the final delivery checks.

Agree the Insider event mapping, supported behaviour and delivery controls for your implementation.

A Retail Worked Example: One Customer, Several Possible Actions

A Beauty Customer Qualifies for a Refill, a Cross-Sell and a Promotion

In an illustrative beauty scenario, a customer has bought a 50 ml moisturiser and also qualifies for a serum cross-sell and a promotion. Maestro considers the competing actions; Insider delivers the selected eligible interaction.

The observed facts are the purchased variant, quantity, dated orders, available stock and recent contact history. The inference is that a refill may be approaching, based on the customer’s reorder pattern. The bottle’s actual remaining contents are unknown.

Assume the customer is eligible for contact, the goal is profitable repeat purchase, and the retailer’s policy excludes unsolicited discounts from an initial refill reminder. In this moment, prior purchases and the inferred refill window provide stronger support for the moisturiser than the serum’s general routine fit.

Candidate	Evidence or assumed policy	Illustrative decision
Refill reminder	Prior moisturiser purchases; inferred need window; no reorder recorded	Select contact without a discount
Serum cross-sell	Plausible routine fit, but weaker evidence of an immediate need	Defer; reconsider only if later context supports it
Promotional discount	Initial-refill policy excludes an unsolicited incentive	Exclude under that policy
No contact	Need or eligibility may be too uncertain to justify contact	Choose this when the evidence or controls require waiting

In the illustration, Maestro considers the competing actions and selects the reminder; Insider delivers it subject to the agreed controls. The policy explains the discount exclusion. Measure the effect of contact and incentives separately from the customer’s likelihood of purchasing.

A small scenario like this can also be implemented with rules. Maestro maintains customer-by-SKU context and coordinates these choices as baskets, pack sizes and lifecycle opportunities change. A pilot should measure the commercial effect and the work needed to maintain the workflow.

A New Order Changes the Decision to No Contact

Now suppose the customer reorders before the reminder is delivered. A new order should trigger re-evaluation before delivery. Agree how the integration updates or suppresses a pending reminder.

The new order does not automatically justify a cross-sell. No contact can be appropriate while the retailer waits for the purchase and recent communication to settle.

Yesterday’s correct prediction can produce today’s unnecessary message without timely updates and activation checks.

Measure Contribution After Discounts, Contacts and Platform Costs

Compare contribution per assigned customer over one common outcome period, including customers selected for no contact and those whose messages were not delivered. Do not analyse only selected messages or converters.

Define contribution consistently in both arms: net revenue after discounts and returns, less product and relevant variable costs. Deduct added software, implementation/services and operating costs once, for that same period. Do not subtract discounts again if net revenue already includes them, or count operating savings twice.

Estimated net value = contribution difference per assigned customer × comparable eligible population − added costs for the same period.

Track repeat purchase, contact pressure, unsubscribes, returns and delivery failures alongside this estimate.

Use a window long enough to reveal whether a reminder merely brings forward a purchase that would have happened later. Report the population, duration, uncertainty and limitations.

Prem’s wider measurement principle applies here: marketing should be judged at the business outcome, rather than at its handoff. In retail, that means following a selected action through to incremental contribution and customer response. More sends, clicks or attributed automation revenue can coexist with weak economics.

Set the adoption criterion before the pilot: improved contribution, comparable contribution with less operating work, or another explicit outcome.

When Replenit Adds Value—and When Native Insider Is Enough

Consider Replenit when customer-by-SKU need and competing lifecycle actions remain unresolved, and the data and ownership can support that job. Its retail context and workflows should change a named customer decision. If the required capability is already operating well, another platform may add little.

Stay native—or retain your internal model—when the required decisions and economics are already satisfactory. Fix unreliable identifiers, order history, catalogue context or feedback before expecting another platform to solve them.

Bring One Unresolved Customer Decision to the Evaluation

Prem argues that real conversation becomes more valuable as automated outreach grows. For this buying decision, use that conversation to settle who owns the action, what data is available and which outcome matters.

Talk to us about one unresolved Insider journey. Bring representative baskets, your current contact policy and the commercial outcome you want to improve. The objective is to define what Maestro would change, how Insider would activate it and what a fair pilot would measure—or establish that the current setup is sufficient.

FAQ

Does Insider One Already Have AI Decisioning?

Yes. Insider makes individual content, channel, timing and no-send decisions, with broader Agent One lifecycle capabilities. The Architect Decision Agent is currently in beta, requires account enablement and supports non-transactional journeys. Confirm the relevant features in your account.

Can Insider One Run Customer-Specific Replenishment Reminders?

Yes. Wait Until Dynamic Time uses date/time inputs; Wait for Some Time can use numeric dynamic durations for refill reminders. Separately establish where those inputs come from, how they reflect customer × SKU need and how they change after new purchases.

Is Next-Best Action the Same as a Prediction or Product Recommendation?

No. A prediction estimates an outcome; a recommendation ranks relevant products. Next-best-action selects an eligible intervention, potentially including a recommendation, delay or no contact. These functions can operate together within one platform.

Where Does Decisioning Sit Between a CDP or Warehouse and Insider One?

Functionally, decisioning converts customer context into an action before activation. It can be native to Insider, supplied by an independent platform or implemented internally. A separate software purchase is not inherently required.

Can Replenit Work Alongside Insider One?

Yes. L’Occitane uses Replenit for replenishment decisioning and Insider for activation. For your own implementation, agree the event mapping, supported behaviour and responsibilities.

When Do We Not Need Another Decisioning Platform?

When the current stack already handles the required decisions, or an existing model can supply the missing signal economically. Another platform is also premature when the data, ownership or measurement needed to operate it is missing.

How Should We Compare a Specialist with Insider One’s Native AI?

Use equivalent underlying records and the strongest current enabled native policy. Include legitimate specialist enrichment, but document it and other material changes. Compare controls, implementation effort and net outcomes across all assigned customers; a combined-policy result does not isolate the algorithm’s effect.

Why Can No Contact Be the Next Best Action?

A customer may have already purchased, received a relevant message or have no useful intervention available. Choosing no contact avoids an unnecessary interruption or incentive. It is a legitimate decision outcome, not a capability unique to Replenit.

Measure the Added Value Against Your Current Native Policy

Use an Optimised Native Baseline and a Defined Experiment

Compare Replenit’s policy against the retailer’s strongest current enabled native approach, using the underlying-record and change-documentation principles above. Adoption needs improved outcomes or comparable outcomes with a material operating benefit.

Start with one decision point rather than a stack-wide transformation. Prem’s approach is to prepare enough to test, then let real responses refine the assumptions. Here, that means a bounded pilot once the required data, controls and measurement are ready.

Use comparable eligible populations and one common outcome period. Where feasible, assign customers persistently and randomly to policies, with assignment and outcome rules defined before launch. Document the additional enrichment or other policy changes rather than requiring identical derived inputs.

Insider’s Architect Control Group excludes its assigned users from all Architect journeys; A/B Split Control Group is specific to one journey. Neither establishes a stack-wide marketing blackout: other marketing exposure can remain. [8]

A no-message holdout can assess intervention impact. It does not alone show that a specialist is better than native AI. That requires a native-policy comparator.