Skip to main content

Understanding quality control by integration (Returns V2)

A 3PL integration sends return inspection results to Swap automatically, with no upload or API call needed. This article covers how results arrive, the supported provider, what your 3PL must send, and what happens when results don't arrive.

Written by Guido Kaspers

This article explains what happens when quality control results reach Swap through a 3PL integration, and what your provider needs to send.

With an integration in place, your 3PL reports the condition of each returned item to Swap as it inspects. You don't upload anything or call the API, and no one has to update the RMA by hand.


How it works

Your provider is connected in either of two places:

  • On the Quality control page, under Quality control providers, open the WMS Provider tab, choose your WMS from Choose the WMS to integrate with, and click Integrate.

  • On the Integrations page, find your provider in the Apps panel and click Connect.

Once the connection is live:

  • Your 3PL inspects the returned items and sends the results to Swap

  • Swap matches each result to the correct return (RMA)

  • Your approval rules are applied to each item

  • Approved items are processed automatically, if automatic processing is enabled

Results arrive either as items are scanned or in a daily batch, depending on the provider.


Supported providers

Mintsoft and ShipBob are the supported integrations.

For Mintsoft — the connection steps, the API key requirement, and how Mintsoft's return reasons map across — see Mintsoft Integration. Mintsoft sends results on a one-day delay: a return received in Mintsoft on 27 May reaches Swap on 28 May.

For ShipBob — the connection steps (a Personal Access Token, generated from your ShipBob dashboard) and what the integration does — see How to integrate ShipBob with Swap (Returns V2). ShipBob's return creation and QC outcomes are supported; ShipBob is not currently available as a shipping carrier or a source of return labels — existing labels and routing rules are unaffected when the integration is switched on. Swap polls ShipBob for completed returns (not webhooks) and updates item-level statuses — Restock, Dispose, or Quarantine — on the RMA automatically.

⚠️ If a return has two or more line items sharing the same SKU, QC outcomes may all be applied to the first matching line rather than split correctly across each one. This affects both ShipBob and Mintsoft.


What your 3PL needs to send

Every result must include:

  • Order number or return ID

  • SKU of the returned item

  • Returned quantity

  • Condition, for example Sellable, Damaged, or Missing

The condition your provider sends is its own name for that condition, not Swap's. Each one has to be mapped to a Store condition in the Condition mapping table first, or results won't apply — see Condition mapping in Understanding quality control.


When results don't arrive

An item with no result within 72 hours is marked Missing, and the RMA moves to Needs Review.

A result that arrives after that still counts, provided the return hasn't been processed yet — the item moves from Missing to the reported condition. Where some items are reported and others aren't, the RMA is marked Partial. Both cases are covered in Understanding quality control and Understanding partial Quality Control processing.

If results aren't coming through at all, check the connection and your condition mapping before raising it with support.

Did this answer your question?