LOG // LISTIA · DRAFT · BROWSER

Browser execution

Listia lists through the same marketplace screens small sellers already use — controlled DOM automation with a human publish gate. It is not a marketplace developer-API product and not an enterprise connector stack.

Project: Listia
Type: Field note · draft
Audience: Builders · operators

DOM_INJECTION SMALL_SELLER NO_CHANNEL_API PUBLISH_GATE

Who this is for

Solo and small multi-channel sellers: phone photos, a few weekly listings, no ops team, no appetite for developer portals, API keys, app review, or “advanced” channel integrations. They already work in eBay / Amazon / Etsy in the browser. Listia meets them there.

What this is not

Not marketplace APIs — no eBay / Amazon / Etsy seller API integration as the product path
Not for advanced sellers already on inventory sync tools, ERP connectors, or full API stacks
Not a general web scraper — only channel seller UIs Listia has adapters for

When someone is ready for official channel APIs and warehouse-grade sync, they have outgrown Listia’s wedge. The product stays honest about that ceiling.

What browser execution is

A channel adapter that drives the real seller UI: fill forms, pick taxonomy, attach media, walk multi-step wizards — same surfaces the seller would click, from a structured listing document produced in Listia.

Input: listing JSON (product + channel overrides + confirmed assets)
Runtime: browser context with the seller’s marketplace session
Output: draft on-channel and/or publish under an explicit gate

Place in the pipeline

Listia catalog / aiContext
        │  channel-shaped payload
        ▼
[Adapter / DOM]  ← browser execution (seller UI, not channel API)
 session · form fill · media attach
        │
 ┌──────┴──────┐
 ▼             ▼
[Human review] [Publish gate]
        │
        ▼
  Marketplace listing (as if the seller clicked through)

Rules

UI path by design — small sellers live in the browser; adapters follow that, not a developer roadmap
Least privilege — session scoped to the seller account and the action
No silent publish — irreversible clicks stay behind confirm
Observable runs — step log / failure trace so “stuck on Etsy step 3” is diagnosable
Adapters version per channel — seller UIs churn; treat that as the cost of this wedge

What stuck

One listing in Listia, many channels, without asking a hobby seller to become a developer. Browser execution is the last mile on purpose — same screens they trust, automation they can still stop before Publish.

Open questions (draft)

Hosted browser vs seller-local extension — session residency and CAPTCHA reality.
How often adapters break when marketplaces redesign their seller UI.
Clear “you’ve outgrown Listia” moment when channel APIs become the right tool.