Using SWAP With a 3PL: How Your Returns Platform and Warehouse Should Work Together

Using SWAP with a 3PL means SWAP runs the customer side of a return (the portal, the rules, the label and the refund, exchange or credit decision) while the warehouse receives, inspects and restocks the item. The setup works when the warehouse sends accurate inspection results back to SWAP quickly enough for refunds and exchanges to be released on time.

Most problems with platform-led returns are not in the portal. They sit in the gap between a parcel landing at the warehouse and the platform knowing what was inside it. This guide walks through each handover between SWAP and a 3PL returns operation, the ways inspection results get back into SWAP, where the handover usually breaks, and what to ask a warehouse before you connect the two.

SWAP and the Warehouse: Who Does What

SWAP owns the customer journey and the decision rules; the warehouse owns the physical item and the stock record. Neither can deliver a fast return on its own, because each depends on data the other holds.

SWAP is a returns and exchanges platform from Swap Commerce, a London-based company. Its Shopify app offers instant exchanges for any size, variant or product, store credit with bonus incentives and automated refunds, and connects to 3PLs, warehouse management systems and help desks. Named connections include Brightpearl, Gorgias, Klaviyo, Mintsoft, Patchworks and Peoplevox. SWAP also works with your existing carrier contracts, supports Shopify's returns and exchanges APIs, and offers webhooks and an API for wider systems.

The 3PL does the work SWAP cannot see: receiving the parcel, matching it to a return, checking the condition, deciding where the item goes and updating stock. Your returns policy (windows, eligibility, who pays postage) is set by you and configured in SWAP. The warehouse executes it.

The Six Handover Points Between SWAP and Your 3PL

A SWAP return passes between the platform and the warehouse at six points, and each one needs a specific piece of data to move. If any of them is late or missing, the customer sees a status that does not match what is happening on the warehouse floor.

1. Return created. The customer starts a return and SWAP issues a label or QR code. The warehouse should receive an expected return record at the same time: return ID, order number, SKUs and quantities. Without it, staff match parcels by hand.
2. Parcel in transit. Carrier tracking tells both sides what is coming. The warehouse can plan returns labour, and SWAP can release early refunds or exchanges if your rules allow it.
3. Arrival and scan-in. The parcel is scanned and matched to the return ID. This is the moment the warehouse takes responsibility for the item.
4. Inspection result. The warehouse records the condition and sends it back. SWAP needs, at minimum, the order number or return ID, the SKU, the quantity returned and the condition.
5. Disposition and stock update. The item is restocked, reworked, quarantined or disposed of, and the stock figure changes in the warehouse system and your sales channels.
6. Customer outcome. SWAP applies its approval rules and releases the refund or credit, or sends an exchange order to the warehouse for dispatch.

How Inspection Results Get From the Warehouse Back Into SWAP

Inspection results reach SWAP in one of three ways: a direct quality control integration with the warehouse system, a CSV upload or SWAP's quality control API, or a middleware connector. Which route your 3PL uses decides how fast and how reliable the handover is.

Direct integration. SWAP's quality control by integration covers Mintsoft and ShipBob as of September 2026. Results arrive as items are scanned or in a daily batch, depending on the provider. Mintsoft results land a day later (a return received on 27 May reaches SWAP on 28 May). For ShipBob, SWAP polls for completed returns and sets each item to restock, dispose or quarantine.

CSV upload or API. If your 3PL runs a different warehouse system, results can be uploaded by file or pushed through SWAP's quality control API. This works, but someone has to own the upload or build the connection, and a missed upload looks to SWAP exactly like a missing parcel. Our guide to API, SFTP and EDI integration options explains the trade-offs.

Middleware. Connectors such as Patchworks sit between SWAP and the warehouse system. They save build time, but add a third party to troubleshoot when something stops flowing.

Whichever route you use, the warehouse's condition names have to be mapped to the conditions in your SWAP store. If the 3PL sends "Grade B" and SWAP has no matching condition, the result will not apply. Get the mapping signed off before go-live, and re-check it whenever the 3PL changes its grading.

Why Exchanges Put More Weight on the Warehouse

A refund is a financial transaction; an exchange is a stock transaction, so it only works if the warehouse stock figure is right at the moment the customer asks. That makes the 3PL's speed and accuracy far more visible.

When a customer swaps a size 10 for a size 12, SWAP has to know the size 12 is genuinely available, and the warehouse has to pick and dispatch it quickly. With instant exchanges, that replacement may go out before the original has come back. If returned stock sits in a queue before it is restocked, sizes show as sold out online while the units are sitting in the returns bay. The commercial case for this model is covered in our article on exchange-first returns. The operational point is simpler: exchanges are only as good as the warehouse's stock record.

Where SWAP and 3PL Handovers Usually Break

Handovers fail in predictable places, and most of these failures can be prevented by agreeing and testing the setup before launch rather than fixing it afterwards.

• Parcels with no return record. Returns sent without a platform label, such as international returns or customers using their own postage, arrive with nothing to match against. Staff identify them from packing slips or names, which is slower and can cost more. On ShipBob, for example, a return without an RMA is treated as a blind return and billed as a warehouse receiving order, typically at a higher rate.
• Condition names that do not match. Unmapped conditions mean results arrive but never apply, so returns stall without anyone noticing.
• Batch timing. A daily batch adds up to a day to every return. That is fine if your refund rules allow for it, and a problem if customer service is promising same-day updates.
• Two lines of the same SKU. SWAP flags a known issue where results for a return with two or more lines of the same SKU may all be applied to the first line. Check how your 3PL handles multi-unit returns.
• Refund rules that contradict the warehouse. If SWAP tells the customer the refund is issued on receipt but the warehouse inspects first, the customer chases and your team fields the contact.
• Reason codes lost in transit. The customer's stated reason and the warehouse's finding are both useful. If only one reaches your reporting, you lose the comparison that shows whether "faulty" really means faulty.

Questions to Ask a 3PL Before You Connect SWAP

Ask for written answers, not a general assurance that the 3PL "integrates with returns platforms". These questions cover the handover points that matter most.

• Is the connection to SWAP direct, file-based, API-based or through middleware, and who supports it when it fails?
• Does the warehouse receive an expected return record before the parcel arrives?
• Which events go back to SWAP, and how long after the physical scan?
• What condition and grade names do you use, and who maps them to our SWAP conditions?
• Are inspection photos and reason codes captured, and can our customer service team see them?
• How do you handle parcels with no return record, mismatched items and multi-unit returns of the same SKU?
• How quickly does passed stock become available to sell again, and how is that reflected in our sales channels?
• What happens to items that fail inspection, and who decides?

How Fulfil with Synergy Runs SWAP Returns From Northampton

Fulfil with Synergy is a founder-led UK third-party logistics provider that runs multi-channel, retail and Amazon Seller Fulfilled Prime fulfilment for growing and household brands from purpose-built facilities in Northampton, combining AutoStore automation and the RedPrairie Dispatcher warehouse management system with high-touch services such as kitting, bonded warehousing and returns management.

Its returns service is fully integrated with SWAP, or with the returns platform you already use. Every item is scanned, inspected, reason-coded, photographed and processed within 48 hours, so refunds can be released quickly. Items that pass inspection to your standards go back to good stock. Items that do not are flagged, scanned and held for your instruction. Returns flows are built around your brand and commercial priorities rather than a fixed template, and an on-site returns team works six days a week.

The handover data comes from the warehouse system itself. RedPrairie Dispatcher gives real-time stock visibility down to unit, SKU, batch and location, with a time-stamped audit trail of every stock movement, which is what exchange-led returns depend on. Fulfil with Synergy connects to other systems by API, flat-file SFTP or SOAP web services, and its client portal shows returns alongside stock and order status, so your customer service team can see where a return is without having to ask.

Not every return goes straight back on the shelf. Light rework such as spot cleaning or removing scuffs on footwear helps recover resale value, and non-perfect stock has several exit routes, from outlet and donation to recycling or refurbishment. Our guide to grading, reworking and reselling returns covers how to set those rules.

Measure the Handover, Not Just the Return

Track the time between each handover point, because the total return time hides where the delay actually sits. A monthly review of these figures with your 3PL catches most problems before customers notice them.

• Carrier delivery to warehouse scan-in
• Scan-in to inspection result showing in SWAP
• Inspection result to refund or credit released
• Exchange request to replacement dispatched
• Share of returns arriving with no matching return record
• Share of items marked missing or needing review in SWAP
• Gap between customer return reasons and warehouse findings

If you are agreeing targets for these, our article on returns processing SLAs sets out what to put in writing.

FAQ

Can I change 3PL without rebuilding my SWAP setup?

Yes, your SWAP portal, rules and customer experience can stay the same, but the warehouse side has to be rebuilt and tested. That means a new return address, a new connection for inspection results, fresh condition and reason mapping, and a plan for returns already in transit to the old warehouse.

The risky period is cutover. Customers who started a return the week before the move will still post parcels to the old address, so agree with the outgoing 3PL how long it will receive, inspect and report those returns into SWAP. Run a handful of test returns through the new warehouse before switching labels over, and check each one reaches the right status in SWAP.

Should refunds be released on carrier scan, on receipt or after inspection?

It depends on your margins, product risk and legal obligations. Refunding on carrier scan is fastest for the customer but carries the most risk of refunding for the wrong or damaged item. Refunding after inspection is safest but slowest. One middle route is a split rule: refund low-value items early and inspect high-value ones first.

For change-of-mind cancellations on online orders, the Consumer Contracts Regulations 2013 require the refund within 14 days of receiving the goods back, or of the customer giving evidence they sent them, if that is earlier. So waiting for inspection does not stop the clock. GOV.UK guidance covers deductions for used or damaged items. This is general guidance, so check your returns policy with a legal adviser.

How quickly should a return show in SWAP after it reaches the warehouse?

Aim for the inspection result to reach SWAP within one to two working days of delivery to the warehouse. Integrations that report as items are scanned are fastest; daily batches add up to a day. If nothing arrives within 72 hours, SWAP marks the item as missing and moves the return to needs review.

A late result still counts if the return has not been processed, so a slow warehouse does not lose the return, but it does create manual work for your team and a wait for your customer. At Fulfil with Synergy, every returned item is processed within 48 hours, which keeps results inside that window. Agree the timing in writing and track it monthly.

What data does SWAP need from the warehouse for each returned item?

At minimum, SWAP needs the order number or return ID, the SKU of the returned item, the quantity returned and its condition, such as sellable, damaged or missing. Without all four, the result cannot be matched to the right return or applied to the right line.

Beyond the minimum, the most useful extras are photographs of the item as received and the warehouse's own reason code. Photos settle disputes quickly when a customer says an item was sent back unused and the warehouse found otherwise. Warehouse reason codes, compared with the reasons customers give in SWAP, show you which products have a sizing, description or quality problem worth fixing upstream.

Does Fulfil with Synergy only work with SWAP?

No. Fulfil with Synergy's returns service is fully integrated with SWAP, but it also works with the returns platform you already use. Connections can be built by API, flat-file SFTP or SOAP web services, depending on what your platform supports.

The handover principles in this guide apply whichever platform you choose: an expected return record before the parcel arrives, inspection results sent back quickly in a format the platform understands, agreed condition and reason mapping, and clear rules on when refunds and exchanges are released. If you are choosing a returns platform and a 3PL at the same time, test the connection between them with real returns before committing to either.

If you use SWAP or another returns platform and want it connected to a warehouse that keeps up, talk to Fulfil with Synergy about your returns flow.

‍