AisleAMP

Stopping at Two Stores Doesn't Mean Two Budgets

You hit Aldi for milk, eggs, and canned goods. Then you drive to the full-service store for the cut of meat you couldn't find there. Two parking lots, one dinner plan. Somewhere between the cart and the second checkout, the original budget number stopped mattering. Not because you spent wildly, but because the second stop felt like a separate errand.

That is how a $120 week turns into $145 without a single "splurge." You remembered the first total. You forgot to subtract it from the second.

Why two stops break the math

Most grocery budgets are set for a trip, not a store. In practice, people treat each parking lot as a reset. The receipt from Aldi goes in the bag. The remaining dollars live only in your head. By the time you are comparing ribeyes, you are estimating from a vague "I already spent something," which is the same as estimating from nothing.

Split shopping is rational. Staples at the discount store and perishables where quality is better is often the cheapest honest cart. The problem is the bookkeeping: two ledgers for one grocery week.

What AisleAMP actually does

AisleAMP treats a shopping run as one trip with one budget, then breaks that trip into store segments. Each segment keeps its own cart, store name, and running subtotal. Switch stores and the app saves the items you already logged, then either opens a new segment or resumes one you already started at that store.

When the app opens a new segment for that store, matching items from your shopping list preload into it as pending (unpriced) rows, with estimated prices pulled from your price history when you have them. If you resume a segment you already started there, you get what you already logged. Pending rows do not count toward the trip total until you confirm a real price. Confirmed spend at every previous store stays in the header: you see the trip total, what is left of the budget, a "This store" subtotal, and a "Previous" row listing each earlier store and what you spent there. The current aisle never erases the first stop.

If location is on and your saved stores have locations, the app checks when the shopping screen opens whether you are within about 150 meters of a different saved store, and asks whether to switch. You can also switch manually from the store button. Either way, the budget does not restart.

When you finish, the confirmation names how many stores the trip covered. The summary shows a store breakdown, with each segment's item count and subtotal, under the same trip budget you set at the start.

What changes

Before: two receipts, two mental resets, and a week that "felt fine" until the bank app disagreed.

After: one trip total that accumulates as you move. The second store starts with the first store already subtracted. You still shop where the deal is; you just stop pretending the second parking lot wiped the slate.

The takeaway, with or without the app

Before the second stop, write the first receipt total on a note or in your phone, then subtract it from the week's grocery number. Shop the second store against the remainder, not against the original budget. If you split stops often, decide the split before you leave home: staples store first, specialty items second, and treat the combined spend as one trip. Two parking lots can still be one grocery week.