What is Merchant’s Favor in WoW Forever?
Merchant’s Favor is a currency connected to WoW Forever’s supply organisations and profession rewards. Wowhead’s beta currency record names Durotar Supply and Logistics and the Azeroth Commerce Authority. Crate hand-ins are the route described by beta testers. This guide was checked on 28 September; reports and database records can change before launch.
The latest planning question comes from 27 September player feedback: will a character outlevel a useful recipe before earning enough currency? That is one tester’s concern, not an announced balance change. For a guild, it makes the next useful purchase more important than collecting every pattern immediately.
How to fill Waylaid Crates without duplicating work
Mobalytics’ 25 September crate guide describes alternative material bundles: one complete option fills a crate. Read the actual shipment tooltip before sending guildmates gathering. Copy the exact crate name, selected bundle and quantity into your request; a request for ‘ore for crates’ is too vague to act on.
Compare what members already hold with what they would need to buy or gather. Choose one bundle, then give each contributor a quantity and recipient. Keep a small reserve for already-promised crafts. The cheapest auction listing is not automatically the best choice if completing it consumes materials reserved for another member’s upgrade.
Do all crates give five Merchant’s Favor?
Do not budget as though every crate pays the same amount. The September 27 forum post reports five Favor for its repeat hand-ins, while a September 23 tester comment on Wowhead distinguishes Apprentice and Journeyman crates by quality, reporting rewards of 5, 10 or 20. These are community observations, not a verified universal reward table.
Record your own crate’s exact item, displayed reward and date. Separate a one-time quest bonus from a repeatable reward. For illustration, a 30-Favor purchase with a balance of 20 requires ten more: that means two hand-ins only if each relevant hand-in actually pays five. The arithmetic is useful; the assumed reward must be checked.
Check who can use the finished item before buying
Treat the recipe, the crafter and the finished item as separate checks. A guildmate knowing a recipe does not establish that its output can be traded to your intended recipient. The Sealed Apprentice Crate database record itself is marked binds when picked up, so a plan to pass around an already-filled crate also needs scrutiny.
At the vendor, confirm the current currency price, profession skill requirement and any other conditions. Then inspect the finished item’s binding and equip requirements. Ask the intended user whether it solves an actual gear gap. Record ‘personal upgrade’ separately from ‘guild supply’ so an officer does not promise an item the crafter cannot deliver.
| Check | Record before spending |
|---|---|
| Recipient | Character, intended use and current gear gap |
| Recipe | Exact name, price and required profession skill |
| Output | Binding, equip requirements and whether it can be supplied |
| Materials | Selected crate bundle, contributors and remaining quantity |
| Evidence | Tooltip or vendor check, client build and date |
Turn the recipe choice into a guild profession plan
Use the RaidMuster guild profession planner to identify relevant crafters and coordinate shared preparation. Keep currency balances and crate details in your accompanying notes; the screenshot below demonstrates profession coordination, not automatic tracking of Merchant’s Favor.
After a purchase, update three things: who learned the recipe, what was actually made and what remains blocked. If the item is personal, acknowledge the completed upgrade without counting it as shared stock. Review the next purchase when the character levels or the beta changes, rather than turning an early shopping list into a permanent guild requirement.
If the crate will not accept the materials
Blizzard’s known-issues thread lists crate stack-size problems and an Apprentice Curiosities essence mismatch. Its older entries promise fixes in a subsequent build; that wording alone does not confirm what works on your current client. Check the build and report the exact shipment and rejected item before buying more materials.