Nine Marketplace Integration Mistakes That Quietly Kill Margin

When marketplace profitability disappoints, everyone audits pricing and ad spend. The money is usually leaking somewhere less glamorous: the integration layer. These are the nine failures we find most often, roughly in order of damage.

1. Settlement reports nobody reconciles

Marketplaces pay you in settlements netting sales, fees, refunds, adjustments and ad spend. Most finance teams book the deposit and move on. Every audit we run finds discrepancies — fee category errors, refunds without returned inventory, damaged-in-warehouse credits never claimed. On Amazon at volume, unclaimed reimbursements alone typically run 1–3% of revenue. That is margin lying in a report nobody opens.

2. Stock buffers set by folklore

"Keep 10% back so we don't oversell" — set in 2022, never revisited. Too big and your bestsellers show out-of-stock while inventory sits; too small and oversells burn seller metrics. Buffers should be per-SKU, computed from sales velocity and sync latency, and recomputed continuously. This is exactly the kind of logic that belongs in software, not tribal memory.

3. Price sync slower than repricing

Your repricer moves a price; the marketplace gets it minutes later; meanwhile the old price sold units below floor. Pricing changes must be first-class events with delivery confirmation, not rows in an hourly CSV.

4. Listing rejections handled by email

Feeds fail per-attribute, and the failure notice lands in a mailbox. Weeks later someone notices the new range never went live in Germany. Rejections belong on a dashboard with owner and age, validated before submission against each channel's schema so most never happen.

5. Orders arriving in three systems

Marketplace orders flowing into a different queue than the webshop's means separate picking logic, separate support visibility, and returns that reference orders your helpdesk cannot see. One consolidated order pipeline, tagged by channel, is the only sane shape.

6. VAT logic hard-coded to yesterday

Rates change, thresholds change, marketplace facilitator rules shift per country. Hard-coded VAT is a compliance incident on a timer — especially cross-border EU, where OSS/IOSS treatment differs by channel and fulfilment path.

7. Returns without reasons

Every return carries a reason code your integration probably discards. Aggregated, they are your best product-quality signal: sizing runs small, photo misleads, damage in transit. Losing them means paying for the lesson and skipping the class — the theme of our returns piece.

8. Ad spend invisible to channel P&L

TACoS computed against channel revenue, with fees allocated per-SKU, changes decisions weekly. Brands flying without per-channel P&L routinely scale losing SKUs and starve winners. The dashboard is not vanity; it is the steering wheel.

9. API deprecations discovered on cutoff day

Marketplaces sunset API versions constantly. Miss a migration and listings freeze mid-quarter. Someone must own the deprecation calendar — we do this for clients as part of managed operation, because the alternative is discovering it from a production outage.

None of these is exciting. Together they are commonly 3–6 points of net margin — which, for most marketplace P&Ls, is the difference between a channel that works and a channel leadership wants to exit.