1. Store sale first
The base transaction starts with the weekly store deal and required quantity, so the optimizer knows what must be bought to trigger the reward.
This optimizer stacks store deals, required coupons, manufacturer coupons, P&G-style savings, and reward planning into coupon runs that stay inside your budget and save rewards for the next trip.
These plans are built like a pro couponer would shop: earn rewards first, then roll them into the next transaction.
Recent generated transaction chains for the current store.
These are the normalized store offers feeding the matchup engine.
Every plan is trying to act like a store-savvy coupon optimizer, not a generic shopping app.
The base transaction starts with the weekly store deal and required quantity, so the optimizer knows what must be bought to trigger the reward.
Store coupons, vendor offers, manufacturer coupons, and P&G-style coupons are matched only when the required items are represented in the scenario.
ExtraBucks and similar reward balances are treated as future savings, and the optimizer tries to tell you exactly when to spend them next.
Money makers are highlighted, low-confidence stacks get reviewed, and budget limits keep the run realistic while still preserving tomorrow’s savings.
These are the deals that need human eyes before they belong in the cottage window.
Set the habits and limits your optimizer should use every time it builds a coupon run.