If you sell on both Amazon and Walmart, you already know the problem: two marketplaces, two sets of pricing signals, and no clean way to manage both without duplicating work. A single repricer that handles both channels isn't just convenient, it's the only setup that lets you run coordinated pricing strategies without constantly context-switching between dashboards.
This guide walks you through the full setup in Informed Repricer, from connecting your Walmart Seller Center account through OAuth authorization, to mapping your product catalog, to configuring marketplace-specific min/max rules that protect margins on both channels.
Who this is for: Amazon + Walmart multichannel sellers managing pricing manually or switching between tools. End result: Both marketplaces connected in one account, products mapped, and marketplace-specific repricing strategies running. Estimated time: 30-60 minutes of active setup, plus up to 4 hours for Walmart's initial sync to complete. Difficulty: Moderate. You'll need admin access to both your Amazon Seller Central and Walmart Seller Center accounts.
Prerequisites and account permissions
"One repricer for both marketplaces" means something specific operationally: you connect Amazon and Walmart as separate channels inside the same platform, then assign strategies per marketplace. The repricing logic runs independently for each channel, which matters because Amazon and Walmart have different fee structures, different Buy Box mechanics, and different data sync behaviors.
Before you start, confirm you have:
- An active Walmart Seller Center account with admin-level access (not read-only; you need permission to authorize third-party app access)
- Your Amazon Seller Central account credentials and MWS/SP-API access already configured in Informed Repricer (or set this up first)
- Clean UPC/GTIN data on your Walmart listings, especially if your merchant SKUs don't match across marketplaces
On the identifier side: Amazon uses ASINs and merchant SKUs to identify products. Walmart uses Item IDs and its own SKU field. These don't map to each other automatically. UPC/GTIN is the common cross-reference key when SKU names differ between channels, so check that your catalog has accurate barcodes before you attempt product mapping.
One constraint to know upfront: multi-variation listings are not supported on Walmart due to API limitations (Informed Repricer Help Center). If you sell size/color variants, you'll map and reprice at the individual child SKU level, not the parent.
Step 1: Connect your Walmart account
Follow these steps inside Informed Repricer:
- Go to Configure > Marketplaces
- Click + Add Marketplace
- Select Walmart
- Click Continue on the Walmart connection screen
- Log in with your Walmart Seller Center credentials when prompted
- Review the access permissions being requested (inventory, pricing, orders, shipping) and click Authorize
- You'll be redirected back to Informed Repricer with the Walmart marketplace connected
The authorization flow uses OAuth 2.0, which is Walmart's standard mechanism for granting third-party applications access to your seller account without sharing your login credentials directly. Under the hood, Walmart's marketplace APIs issue short-lived access tokens that the integration refreshes automatically. You don't manage tokens manually in the UI, but understanding this helps if you ever need to re-authorize after a permission change.
Sync timing: Walmart syncs data differently from Amazon. It can take up to 4 hours for listings or new items to appear in Informed Repricer (Informed Repricer Help Center, January 2026). Don't assume the connection failed if products aren't visible immediately. Wait the full window before troubleshooting.
Step 2: Map products and SKUs
A repricer can't link your Amazon listing to your Walmart listing automatically without a cross-reference key. There's no conversion layer between an Amazon ASIN and a Walmart Item ID; they're independent identifiers assigned by separate systems.
Mapping works in order of complexity:
- Identical merchant SKUs: If you use the same SKU string on both Amazon and Walmart, Informed Repricer can resolve the match directly. This is the cleanest scenario.
- UPC/GTIN cross-reference: When SKUs differ, UPC or GTIN provides a common barcode identifier. Both marketplaces store this field, and it's the most reliable cross-reference for catalog-level matching.
- Manual or bulk CSV mapping: When identifiers don't align, use the dashboard's manual mapping or upload a bulk CSV file with explicit field-level matches.
A mapping template to work from:
| Walmart Item ID | Walmart SKU | UPC/GTIN | Amazon ASIN | Amazon SKU |
|---|---|---|---|---|
| 987654321 | WMT-SKU-001 | 012345678901 | B08XYZABCD | AMZ-SKU-001 |
Before enabling repricing, spot-check at least 10-20 items. Confirm the UPC/GTIN values match on both sides, that the Walmart Item ID is resolving correctly, and that no parent variation IDs are in the mapping (map child variants only, as multi-variation parent listings aren't supported via the Walmart API).
Step 3: Configure marketplace-specific repricing rules
After your products load, the required workflow is: set min and max prices, assign a strategy, then activate repricing. Don't skip the min/max step. Without price floors and ceilings, a strategy has no bounds.
Walmart and Amazon need separate pricing logic. The reasons are concrete:
- Walmart referral fees differ by category. Grocery, for example, is 8% for items priced at $15 or under and 15% above $15 (Walmart Marketplace, official pricing page). Your margin floor on the same product will be different on Walmart vs Amazon.
- Walmart Fulfillment Services (WFS) adds its own cost layer if you're enrolled, just as FBA affects Amazon landed cost calculations.
- Competition signals on Walmart's Buy Box are weighted differently than Amazon's, and Walmart doesn't share the same offer data format.
Set your min prices to cover landed cost plus your minimum acceptable margin per marketplace, not a single shared number across both channels. Your max price should reflect the highest you can charge without losing the Buy Box to a significantly cheaper competitor.
Three practical scenarios:
- Winning the Buy Box without margin erosion: Competitor drops price just below yours. Your strategy lowers to match (or beat by a small increment), but stops at your min. If your min is already protecting margin, you stay in the Buy Box profitably.
- Responding to a competitor price drop below your min: Your strategy holds at your min floor rather than following the race down. You may lose the Buy Box temporarily, but you don't take a loss. Informed Repricer's profit-first model is built around this behavior: the goal is profitable growth, not lowest price.
- Holding price when non-price factors dominate: If you have strong seller metrics, WFS fulfillment, or high review velocity, holding at or near your max can still win or maintain the Buy Box. Configure a price-hold or upward-reprice rule to push toward your max when no cheaper eligible competitor exists.
On the Walmart side, note that price changes are submitted via batch feeds to the API. Rate-limit constraints exist at the Walmart API level (Walmart Developer Portal), which means Walmart-side price propagation isn't instantaneous even when Informed Repricer processes the change in seconds on the Amazon side. Avoid configuring Walmart rules that trigger repricing on every minor signal; batched, deliberate updates perform better here than high-frequency micro-adjustments.
Troubleshooting and best practices
Items not showing after connection: Wait the full 4-hour sync window. If listings still haven't appeared, verify that your Walmart Seller Center account is in active selling status and that the authorization wasn't limited in scope (check under your Walmart Developer Portal app permissions).
Prices not updating: The most common cause is a mapping mismatch. Check that the Walmart Item ID in your mapping resolves to an active listing. Then confirm your min/max range actually allows a change from the current price (if the current price equals your min or max, no adjustment fires).
Strategy not assigned: Products that loaded after you set up your first strategies won't auto-inherit a strategy. Go to the Walmart product list in Informed Repricer and assign strategies to newly synced items explicitly.
Multi-variation errors: Don't attempt to map Walmart parent variation IDs. Map only child/variant-level SKUs. Parent variation listings aren't accessible through the Walmart API.
Debug checklist:
- Authorization status is active (not expired or revoked)
- Products visible in the Informed Repricer Walmart product list
- Identifier match confirmed (UPC/GTIN or SKU-level)
- Min/max range set and allows a price move
- Strategy assigned to the SKU in question
- Enough time elapsed for Walmart's feed propagation
Rollout approach: Start with a pilot set of your top 20-30 Walmart sellers. Monitor Buy Box percentage and margin over 7-14 days before expanding to the full catalog. Keep your UPC/GTIN data clean across both catalogs; a single bad barcode blocks mapping for that product. If you use WFS, configure Walmart rules that account for WFS fulfillment costs separately from FBM listings.
Common questions:
Can I use one repricer for Amazon and Walmart? Yes. Informed Repricer supports both marketplaces in one account with marketplace-specific strategy assignments.
How long does Walmart sync take? Up to 4 hours for listings and new items to appear after connecting (Informed Repricer Help Center, January 2026).
Why are my prices not updating on Walmart? Check mapping accuracy, verify min/max bounds allow a change, and confirm strategy assignment. Walmart's API also has rate-limit constraints that delay feed propagation.
Do I need UPC/GTIN mapping? Only if your merchant SKUs differ between Amazon and Walmart. If SKUs match, direct resolution works. UPC/GTIN is the fallback cross-reference.
Is upward repricing supported? Yes. When no eligible competitor undercuts your offer, strategies can push price upward toward your configured max, which is where profitable pricing decisions actually happen.