multi-channel marketplace listing · field note

Explore: migrate to eBay Inventory/Sell APIs, retire Browse API

A working diagnosis of this problem and the sequence that actually resolves it, written from the operational side rather than the marketing side.

Reported context: ## Background Currently using the Browse API (buyer-facing) for listing sync, which means seller-specific data like quantity, condition details, and listing state are unavailable or unreliable. Most new listings are now created via the Inventory API anyway. OAS3 spec is at \`sell_inventory_v1_oas3.json\` in the repo root. ## API endpoints available (from OAS3 spec) **Migration** - \`POST /bulk_migrate_listing\` — con

What is actually going on

Cross-channel sync breaks when the source of truth is ambiguous — two systems both writing inventory produce oversells.

Listing rejection is usually a policy metadata problem, not a product problem: restricted category flags, missing compliance documents, or title formatting that violates the marketplace style guide.

The sequence that works

  1. Pull the exact rejection reason code from the marketplace API rather than the dashboard summary, since the two frequently differ.
  2. Rebuild titles against the marketplace style guide: character limits, capitalisation rules, prohibited claims, and required attributes.
  3. Localise rather than translate: convert units, adapt the guarantee wording to local consumer law expectations, and rewrite the first three bullet points for local buying motivation.
  4. Establish a single inventory source of truth and make every other channel read-only against it.
  5. Set a daily reconciliation report that flags any SKU where channel quantities diverge by more than one unit.

Where people lose time

Verify before you trust it

Run the checks above against your own data instead of adopting them at face value. The failure modes are specific enough that a single afternoon of measurement will either confirm this diagnosis or rule it out — both outcomes are useful, and guessing is not.

Inventory Flow Oracle
A ready-to-use package for exactly this workflow — $187, delivered immediately.
Get Inventory Flow Oracle · $187
Sold via Gumroad, which acts as merchant of record and handles payment and applicable taxes. All sales are final; see the return policy before purchase.