How do we use RR when we ship the replacement and pick up the return at the same time?

Hi , Did you find a solutions for this 

Yes, thank you. 

Can you please share how did you manage to do it 

We created Order Type RP with the following settings: 

We created Order Type RP with the following settings: 

We CREATE SHIPMENT for the first line item, replacement item/Issue line item, and CONFIRM SHIPMENT at time of delivery. This gets invoiced immediately.

While onsite, our driver picks up the second line item, the Return Item/Receipt line item, and brings it back to our shop RECON location.

Our Returns Team evaluates the item to determine if credit is due. When it is determined that credit is due (Warranty due to failure verified), we then CONFIRM SHIPMENT for the Return line and issue the appropriate Credit to the customer.

Thanks for the detailed answer. However, our situation is slightly different.

We have a scenario where a customer requires both a return and a replacement, and we are using a 3rd-party courier that pulls shipment records overnight and needs to collect the return and deliver the replacement at the same time.

The issue we are facing in Acumatica is that We cannot process the replacement until the return receipt is completed,

Given this dependency, how can we handle return and replacement transactions when the courier must collect and deliver simultaneously, but Acumatica requires shipments and receipts to be completed sequentially? We would like the system to allow us to create two shipment record 1 for receipt and 1 for delivery. Is it possible ?

I do not have experience with the method you are describing. 

When I search the web, it brings back this result: 

This is a known limitation / design behavior in Acumatica, and you’re not doing anything “wrong.” I’ll break this down into why it behaves this way and then give you practical ways companies handle RR (Return for Replacement) when using company trucks and delayed pickup.

Why Acumatica behaves this way (RR mechanics)

In Acumatica, Return for Replacement (RR) is designed as two linked but sequential logistics events:

1. Replacement = outbound shipment

2. Return = inbound receipt

Key system rule:

The replacement shipment must be confirmed before Acumatica allows the return shipment to be created.

This is intentional because:

• The return references the completed replacement

• Inventory and costing must be established for the outbound item first

• The system assumes the customer has the replacement before returning the defective item

So while SO Entry looks perfect (replacement + return lines together), shipping documents are intentionally separated.