Unmatched returns and worked scenarios

Unmatched returns and worked scenarios

Unmatched returns

A parcel the 3PL cannot tie to any Odoo order (unknown reference, hand-written label…) becomes an RMA flagged Unmatched with an orange ribbon and a to-do activity. The 3PL's reported lines are on the RMA for identification, but no stock moves until a person links the sales order and presses Process Receipt (Admin action). This is deliberate: goods with no owner get a human decision, not a guess.

Worked scenarios

Label return. Customer emails about a wrong size on SO1042. CS opens the order > Create 3PL Return > unticks nothing, picks Royal Mail Tracked 48, Create Return. RMA/00007 is created, label PDF attached two seconds later; CS emails it to the customer. Ten days later the returns poll shows Sprint received 1 of 1, grade A - the reverse receipt books into stock, a draft credit note for that line appears for accounting.

Own-label return, damaged. A customer ships back unaided. The poll creates RMA/00011 (origin: Arrived at 3PL) matched to SO0977 by reference; Sprint grades the item "Damaged - Dispose". The receipt books it into Returns - Damaged, not sellable stock; the credit note still drafts (your policy decides whether to post it); the RMA line shows the verbatim grade for the dispute file.

RTS. A parcel comes back marked undeliverable. RMA/00013 carries the red ribbon; CS phones the customer, confirms the address, and re-sends the order - the RMA documents why stock reappeared.

    • Related Articles

    • Holds, cancellations and worked examples

      Holds A hold is the 3PL saying "we have the order but cannot progress it" - no stock, replenishment needed, back order, manual hold. Holds are not errors: the order stays at the warehouse and usually resolves there. The connector shows holds on the ...
    • How returns work - the three origins

      Customer returns through a 3PL are messy in real life: some you authorise and label, some just turn up at the warehouse, some are couriers bouncing undeliverable parcels back. The connector models all three, keeps stock honest (including damaged ...
    • Stock, inbound, returns and housekeeping settings

      Returns Behaviour (shown when the provider supports returns) Damaged Returns Location. Where returned stock graded non-restockable by the warehouse is received. Leave empty and the connector creates a Returns - Damaged internal location under the ...
    • UNBATCHED stock, forced syncs and a worked example

      The UNBATCHED bucket When despatches had to ship lot-tracked goods without batch data (see Allow Un-batched Despatches), that stock lives under the special UNBATCHED lot. The inventory sync is what heals this: as soon as the 3PL reports real batch ...
    • Roles and permissions

      Access to the connector is controlled by a single role picker on each user (Settings > Users > 3PL Connector): Read Only, Ops or Admin. Each level includes everything below it, and every button in the app is role-aware - users simply do not see ...