Amazon Repricing Service — Margin-Protected Algorithmic Repricing
A repricer that knows your breakeven before it knows your competitor's price.
If you're dealing with...
- Rule-based repricers racing your catalog to the bottom one penny at a time
- Winning the Buy Box on sales that lose money after fees
- MAP violations because your repricer doesn't know your MAP agreements exist
- Prices thrashing up and down all day with no strategy behind the moves
- No idea what your true breakeven is per SKU, so floors are guesses
- A repricer you're afraid to turn on because you can't see what it would do first
Why Most Repricing Loses Money
The standard repricer failure mode is well known: two rule-based repricers meet on a listing, each set to beat the other by a penny, and the price walks to the floor by lunchtime. Whoever set the lower floor “wins” — the Buy Box, and a margin that no longer covers fees.
The less obvious failure mode is worse: the floor itself is wrong. Most sellers type a floor into their repricer once, based on a cost number from memory and a fee number from last year. Amazon fees change. Unit costs change. Fuel surcharges land. The repricer keeps happily selling at “2% above floor” while the floor sits 4% below actual breakeven.
Our amazon repricing service was built around one principle: know the breakeven first, react to competitors second.
How the Repricer Works
Floors stack, and nothing crosses them. Every SKU carries two stacked floors. First, a breakeven margin floor: true unit cost from your recent purchase orders plus actual Amazon fees, plus your minimum margin. Fee data cascades through three tiers — exact SP-API fees where Amazon publishes them, market-data estimates where it doesn’t, category medians as the fallback — so the floor reflects reality, not a guess. Second, MAP and manual minimums from version-controlled configuration layered on top. The effective floor is whichever is higher. No decision, human or algorithmic, prices through it.
Strategy is nightly. Reaction is intraday. They never swap jobs. Once a day, with complete sales, fee, and competitive data, the engine computes a full pricing plan: which tier each SKU sits in, how prices decay on aging inventory, where elasticity says you can push up instead of down. That’s strategy, and it’s made calmly, once, with everything on the table.
During the day, a watcher monitors Buy Box and competitor movement and re-runs the competitive decision within minutes of a change — but only inside the floors and bounds the nightly plan established. It can chase a competitor down to the floor. It can recapture price headroom when a competitor stocks out. It cannot change strategy, move a floor, or improvise. This split is what prevents the thrash-and-spiral behavior that makes sellers afraid of their own repricer.
Everything is previewable, and everything is logged. New strategies run in dry-run mode by default: you see every price the plan would touch, the old price, the new price, and the rule that produced it — before anything hits Amazon. Every live price change is written to an audit log with its reasoning. And a single kill switch halts all price writes instantly, catalog-wide, if you ever want everything frozen.
Pricing connects to the rest of your economics. Repricing decisions feed the same margin model our replenishment engine uses, so the SKUs the repricer defends hardest are the ones actually worth defending. If your pricing strategy includes promotions or Buy Box recovery work, the floors and tiers reflect it.
Who This Is For
You’re a fit if:
- You’re resellling or competing on shared listings where the Buy Box moves hourly
- You’ve caught your current repricer selling below breakeven — or you can’t tell whether it is
- You have MAP agreements and need enforcement you can prove, with change history
- Your catalog has 100+ SKUs and manual repricing stopped scaling a long time ago
- You suspect you’re leaving money on the table when competitors stock out and your price stays parked at the floor
You’re not a fit if:
- You’re a private-label brand alone on your own listings with no competitive pressure — you need pricing strategy, not a repricer
- Your problem is unauthorized sellers undercutting MAP — that’s an enforcement problem, and it’s covered by brand management
How We Work
Week 1: Pricing audit. We reconstruct true breakeven for every SKU — real unit costs, real fees — and compare it against your current prices and floors. Most brands find SKUs selling below actual breakeven and SKUs parked far below what the market would bear. You get both lists, quantified.
Week 2: Floor and strategy configuration. Breakeven floors computed, MAP agreements and manual minimums loaded into tracked config, tiers and decay rules set per product class. Everything runs dry-run; you review the full would-change list before go-live.
Week 3 onward: Live operation. Nightly plans, intraday watching, weekly reporting on Buy Box share, average selling price versus floor, margin captured on competitor stockouts, and every floor save — the moments the system refused to follow a competitor below breakeven.
Why Brands Choose Altus Commerce for Repricing
Because the repricer was built by operators, not by a SaaS growth team. Every safeguard in it exists because the absence of that safeguard cost real money on a real catalog: the dry-run default, the kill switch, the strategy/reaction separation, the fee cascade, the version-controlled MAP floors. We don’t sell you software and wish you luck — we run it, watch it, and report on it as part of your pricing operation.
Find out what your real breakeven is. Request a pricing audit.
What's Included
Stacked Price Floors
Breakeven margin floor computed per SKU, then MAP and manual minimums layered on top — no price ever crosses either floor
True Breakeven Calculation
Fee data cascades from actual SP-API fees to market estimates to category medians, against real unit costs from your purchase history
Nightly Strategy Plan
Pricing tiers, decay schedules, and elasticity decisions computed once per day with full data — strategy never gets made mid-panic
Intraday Competitive Response
A watcher reacts to Buy Box and competitor moves within minutes, but only inside the floors and bounds the nightly plan set
MAP Compliance Built In
Vendor MAP agreements and manual price minimums live in version-controlled config — enforced on every price decision, auditable forever
Dry-Run Transparency
Every strategy change runs in preview mode first — you see every price it would touch and why, before anything goes live
Kill Switch & Audit Trail
One switch halts all price writes instantly, and every price change ever made is logged with the reasoning that produced it
Results We've Delivered
Frequently Asked Questions
Most repricers are rule engines: match the lowest offer, beat it by a penny, floor at whatever number you typed in. They don't compute your breakeven, they don't know your MAP agreements, and their 'strategy' is whatever reacts fastest. Ours separates strategy from reaction: a nightly plan sets tiers, floors, and decay with full data, and the intraday watcher can only act inside that plan. You get fast competitive response without the death-spiral behavior.
Real unit cost from your recent purchase orders, plus actual Amazon fees. Fee data cascades in three tiers: exact SP-API fee data when Amazon publishes it, market estimates when it doesn't, and category medians as a last resort. The floor is your true breakeven plus your minimum acceptable margin — computed per SKU, refreshed nightly.
The floors, structurally. The intraday watcher is only allowed to re-run the competitive decision inside the current plan's floors — it cannot lower a floor, change a tier, or make a strategy call. If a competitor prices below your breakeven, you simply don't follow them there. Strategy changes happen once a day, deliberately, with full data.
Yes — that's mandatory, not optional. Every plan runs as a dry run first: full output of every price it would change, from what to what, and which rule produced the decision. Nothing writes to Amazon without explicit approval, and a kill switch halts all writes instantly at any time.
MAP and manual minimums are first-class floors, stacked on top of the breakeven floor. They live in tracked configuration with full change history, so you can prove to any vendor exactly what floor was enforced on any date. If you're fighting MAP violations from other sellers, that's a different problem — see our brand management service for unauthorized seller enforcement.
Both. FBA and FBM offers on the same ASIN get coordinated strategy, so your own offers never race each other down. Multi-marketplace catalogs are supported as well.