Marketplace Support

On a marketplace, the platform is the customer too

Selling on your own store, poor service costs you customers. Selling on a marketplace, it can cost you the channel entirely.

Marketplaces measure sellers on response time, defect rate, late dispatch, cancellations and negative feedback, and they enforce those measures with suppressed listings, lost buy-box position, restricted selling privileges and account suspension. A metric that drifts out of tolerance is not a KPI conversation - it is a revenue event, and reinstatement is slow and uncertain.

RHI provides dedicated marketplace support teams that work to the platform's clock as well as the customer's.

What the team handles

• Buyer messages - within the platform's response window, which is the metric most easily and most often breached.
• Order management - confirmations, amendments, cancellations and dispatch updates against platform rules.
• Returns and refunds - processed through the platform's own flow, which is not the same as your store's.
• Claims and disputes - responding to buyer claims with the evidence the platform requires, in the format it requires.
• Feedback and review management - requesting removal where a review breaches platform policy, and responding where response is permitted.
• Listing issues - suppressed listings, content policy flags, and the corrections needed to restore them.
• Performance metric monitoring - watching the numbers that decide your selling privileges, and flagging drift early.
• Multi-marketplace coordination - where the same catalogue sells across several platforms with different rules.

The response window is a hard deadline

Most marketplaces require a response to buyer messages within a defined window, and count breaches against your account health. This is not a service level you negotiate; it is a threshold you meet or fail.

Two consequences for how the work is staffed. First, coverage has to span the window including weekends and holidays - a message arriving Friday evening against a short window cannot wait for Monday. Second, an acknowledgement inside the window counts, so the operational discipline is to respond fast and then resolve, rather than resolving before replying.

We roster to the window rather than to office hours, and we report against it separately from customer-facing response measures, because those are different obligations with different consequences.

Metric drift, caught early

Marketplace performance metrics move on trailing windows, which means by the time a metric looks bad the cause is weeks old and the remedy takes weeks more. Watching the trend is the only useful approach.

We monitor the metrics that govern your account - response time, order defect rate, late dispatch rate, cancellation rate, valid tracking rate, negative feedback - and report movement rather than only current values. Where a metric is trending toward a threshold, that is escalated as a commercial risk rather than filed in a monthly pack.

Frequently the cause is not support at all. Late dispatch is a warehouse problem; defect rate is often a listing accuracy problem. Reporting it as a finding with an owner is more useful than reporting it as a number.

Claims and disputes need evidence, not argument

Platform dispute processes are documentary. A well-argued response with no evidence loses; a terse response with tracking data, photographs and the message history wins.

Agents are trained to assemble the evidence package the specific platform asks for, in its format, within its deadline. Missing a dispute deadline usually means an automatic decision against you regardless of merit, so deadline tracking is treated as a work queue rather than a diary note.

Platform rules differ, and they change

Amazon, eBay, Etsy, Walmart and the regional marketplaces each have their own response windows, metric definitions, communication restrictions and prohibited content rules. What is permitted messaging on one is a policy breach on another - for instance, several platforms restrict directing buyers off-platform or soliciting reviews in particular ways.

Agents are trained per platform rather than generically, and policy changes are treated as a training trigger. For platform-specific operational work see this page alongside your own store operations in eCommerce support.

Coverage, systems and languages

Coverage is built from shift units and is usually wider than a store-only operation because of response windows and weekend trading. Where you sell across time zones, continuous cover may be justified by the windows alone - see 24/7 support.

Agents work in the platform seller consoles and in your help desk where messages are integrated. Our teams are experienced across Amazon Seller Central alongside Shopify, WooCommerce and Adobe Commerce for your own store - competence, not partnerships or certifications. See technology. Languages are as listed on our languages page.

Quality and reporting

Two reporting layers, kept separate. Platform compliance: response within window, dispute deadline adherence, metric trend against thresholds, listing issue resolution time. Customer outcome: resolution rate, repeat contact, feedback sentiment.

The first layer protects the channel and the second protects the customer, and they occasionally pull in different directions - which is exactly why blending them would be a mistake. Interactions are sampled and scored, with platform-window and deadline criteria scored pass-or-fail. See quality assurance. Figures published elsewhere on this site are historical or representative and campaign-dependent.

Getting started, and what it costs

Priced per dedicated agent per month with a five-agent minimum - published rates and what moves them.

Bring your current account health metrics for each platform, message volume, and any open listing or policy issues. If a metric is already close to a threshold, say so first - that changes the priority order of everything else. Related: eCommerce support, returns and refunds. Talk to us.