Reconcile & Launch · Controlled design-partner pilot
Loyumi Reconcile & Launch is a fixed-scope, 6–8 week Sandbox pilot for merchants that need to map balances and rules, prove the return path, and make a reviewable migration decision without putting production value at risk. “Launch” means a launch decision—not a live launch.
One program One Sandbox Written evidence and stop criteria
This pilot is designed for an existing loyalty program with real migration or control questions. It is not positioned as a low-cost plug-in or a shortcut around procurement.
The starting scope is intentionally narrow enough to finish, inspect, and reject. Anything outside it must be separately written, priced, and accepted.
Document the current earn, return, reward, expiry, adjustment, identity, and support rules for one existing loyalty program.
Map and rehearse up to 5,000 synthetic, nonfinancial opening-balance test records in one isolated Sandbox environment.
Configure one earn rule, one useful reward, and one return or reversal policy against agreed acceptance cases.
Prove identical retry, full or partial return, balance agreement, pause, recovery, and portable export behavior.
Compare merchant-supplied control totals, imported value, ledger movements, and resulting balances until every difference has an owner and treatment.
Leave with a review-ready evidence pack, unresolved-gap register, and an explicit stop, extend, or proceed recommendation.
The pack describes system-generated and team-reviewed evidence. It is not an independent audit, financial statement, certification, customer reference, or claim that Production is ready.
The selected program, systems, data boundary, owners, assumptions, acceptance cases, and stop criteria.
The source-to-target mapping, merchant-supplied control totals, rejected records, approved exceptions, and mapping version.
Request identifiers and outcomes for earn, identical retry, balance, return, pause, recovery, and export.
Opening and closing control totals, differences, explanations, owners, and finance-review notes.
What the pilot established, what remains unverified, what would block Production, and who owns the next decision.
Your current program or vendor, approximate member and balance-record volume, decision trigger and date, available synthetic test evidence, and any connector or assurance requirement that could block you.
Loyumi will not present a Sandbox migration proof as proof of retention impact. A future retention pilot depends on verified production connectors, accepted data quality, approved customer treatment, sufficient sample, and a separately agreed measurement design.
Bound one migration question and produce a written Sandbox decision pack.
Prove the actual commerce, identity, return, messaging, and customer-surface paths before any live promise.
Run a separately scoped, controlled retention pilot. No causal uplift or ROI is claimed in advance.
Loyumi publishes implemented contracts, test evidence, limitations, and assurance gaps. Named production references, independently verified volume benchmarks, contractual SLA history, native connector availability, and external certification are not currently claimed.
Share the current program, decision trigger, record volume, available evidence, and known blockers. If the fixed pilot is not a fit, that should be clear before either team commits.