Marketplace vs. DTC: Who Gets Called First by Agents?

Consider a composite scene. A home-comfort brand sells a 50-pint dehumidifier two ways: a marketplace storefront and its own store. A growth lead types a constrained request into a shopping agent — a 900-square-foot basement in Ohio, under $300, delivered before Friday, returns without a restocking fee. Three marketplace links come back. The brand’s store, cheaper and better shot, is never opened: “before Friday” sits in a hero image, the return terms behind a footer link.

An agent does not call the larger brand or the better page. It calls the source that can confirm, in one pass, that the order completes at that price, by that date, with a way back — so marketplace versus DTC is a question about verifiable facts, not traffic.

The first filter is verifiability, not affection

The agent’s job is completion, not recommendation. It turns an open request into checkable constraints: region, budget, dimensions, deadline, return window, payment. Each needs a value. A missing value does not lower your rank; it removes you from the candidate set.

A marketplace keeps those values in listing and fulfillment data — price, stock, delivery promise, seller rating, a dispute path — readable in one call. A DTC store scatters them: price above the fold, lead time in a FAQ, returns on a policy page, stock only at checkout. The agent infers, and low confidence loses to a listing that states a date.

The second filter is accountability. A wrong order, a late delivery, a refused return: the cost lands on the agent and buyer. A marketplace carries ratings and arbitration, so a bad outcome has a route. A DTC store often carries a support address. The agent prices that risk before your discount.

Brand affection does not decide the call; it operates inside the candidate set, after the source is chosen. Counterexample: a DTC store built as a prettier copy of the listing — same SKU, price, images. Nothing lets the agent verify more, so why open a second source?

Six lines of comparison

Instruments, not rivals for one shelf.

Dimension	Marketplace	DTC store	What the agent needs
Product and stock	Structured, platform-validated	Self-built; your discipline	Every attribute in one read
Delivery	Platform promise plus tracking	Yours to state and keep	A date, not a range
Returns and disputes	Platform rules and escalation	Your policy, enforced by support	Who answers when it fails
Trust signals	Ratings, sales history	Brand entity, third-party corpus	Evidence you did not write
Customer data	Platform’s; you see a summary	Yours, for repeat orders	Nothing this call
Price and margin	Transparent, fixed fees	Controllable; traffic you buy	A total it can compute

The marketplace’s advantage is verifiable fulfillment, not traffic. The DTC store’s advantage is an asset you keep, not freedom. The first decides whether the agent dares to order; the second, whether a first order becomes a repeat.

Choose the primary carrier by scenario

Ask per SKU: which of my facts can the agent check here? Put that fact on the primary carrier.

Scenario	Primary	Supporting move	Signal to watch
Standardized, price-compared, deadline-driven	Marketplace	Store answers brand and comparison queries	Marketplace links recur
High-ticket, needs explaining, accessory repeat	DTC store	Marketplace listing as trust anchor	Agent quotes your specs
New market, no demand data	Marketplace	Validate demand, then build the store	Search terms, return reasons
Custom, regulated, complex after-sales	Neither yet	Write the data and policy first	Agent keeps asking one field

Three errors repeat: high marketplace revenue read as proof the marketplace should lead; a store that holds everything and exposes no field; and two carriers priced apart, so the agent reads two values, trusts neither, and drops the brand.

One set of facts, two entry points

Two carriers are not two shops; they are one set of facts readable at each entrance.

Step	Action	Owner	Passes when
1 Map the calls	Ten constrained prompts in two agents; log the sources	Growth	Every prompt names a source
2 Assign carriers	Mark each SKU primary or supporting; one primary only	Category, growth	Written into the product record
3 Single source	Price, stock, lead time, returns from one master record	Ops, engineering	Two SKUs compared, no gap
4 Write fields	Promises in feed attributes and structured data, not images	Engineering	A crawl returns four values
5 Measure apart	In-platform calls logged apart from outside referrals	Measurement	Each order names its entrance

Step 3 fails most often. A one-sided promotion: the agent reads two prices and files the brand unreliable. Split master data does not add a channel; it amplifies the contradiction. Anchor the reading in an AI visibility baseline, or the entrances get judged on different clocks.

Example: one dehumidifier, two answers

Example — brand, SKU, and figures are invented; no real product described.

Before: the store opens with “Quiet comfort for damp basements.” Delivery reads “3–5 business days”; returns live in the footer; stock appears at checkout. The agent lists three marketplace links and adds, “also sold by the brand.”

After: four values move into structured data and the feed — 50-pint capacity to 1,200 square feet, in stock in a Midwest warehouse, ordered by 2 p.m. for Friday delivery, 30-day returns with a prepaid label. The store link appears, and “arrives Friday” becomes part of the reason.

The copy did not change. The promise moved from a sentence a marketer wrote to a field a system can read. Whether checkout can finish depends on live price, stock, delivery, and payment endpoints — the subject of agentic commerce readiness.

Where this breaks

First, whether a marketplace opens listings and checkout to third-party agents is the platform’s call, market by market; no timeline here. Without it, the advantage stops at “humans check out here.”

Second, a DTC store with no off-site evidence will not get risk taken on an unknown domain; settle whether your brand entity exists first.

Third, price conflict across carriers triggers marketplace price rules and hands the agent contradictory values; a traffic price and a margin price cannot both hold.

Fourth, repeat and accessory purchases start from habit, not an agent call; the first call is not the last.

Fifth, being called is not being chosen. Inside the candidate set the contest is the answer unit and its evidence, not storefront count.

This month, take your best-selling SKU, write ten constrained prompts, run each in two agents, and log which source was called and which field was missing. Fix the field, rerun in 30 days. The rest of the channel line is on the strategy and market hub.