Receipts, grading and credit notes
What booking a receipt actually does
When the 3PL reports received quantities, the connector:
- Creates the reverse transfer from the order's original delivery
- the return receipt is linked to the outbound in Odoo's chain, so
traceability survives.
- Sets the receipt lines to what the warehouse actually counted
(
ActualReceived, not what was expected), with the batch numbers
and expiries the 3PL reports. Lot-tracked goods reported without a
batch fall back to the UNBATCHED lot with a logged warning.
- Routes each line by its grade. The warehouse grades returned
goods; the connector reads the grade/action and marks each RMA line
Restockable or not - a grade or action containing one of the
instance's Non-restockable Keywords (damage, dispose, scrap and
so on; the list is editable, see Settings reference) marks the
line non-restockable, and you can override the tick per line before
processing. Restockable stock goes to normal sellable stock;
non-restockable stock is received into the Damaged Returns
Location (auto-created "Returns - Damaged" under the warehouse,
or the location you configured) - so a write-off never pollutes
sellable inventory.
- Validates the receipt and moves the RMA to Booked into Odoo, with
smart buttons to the receipt and the credit note.
- Acknowledges the return to the 3PL (providers that support it -
the 3PL's "set viewed") - only after Odoo has successfully booked
it, so a crash can never leave a return marked processed at the
warehouse but missing in Odoo.
The credit note
On booking, the connector raises a draft credit note for the
received quantities, priced from the original order lines with their
taxes - but only when it makes sense:
- only if the order has a posted customer invoice (nothing to
credit otherwise - chatter says so);
- only if no credit note already exists for the order - whether
raised manually by accounting or by an earlier return. The RMA's
chatter names the existing one instead of duplicating it.
The credit note is always a draft: accounting reviews, adjusts if the
refund policy says so (restocking fees, partial refunds), and posts.
The connector never posts money movements by itself.
Related Articles
Stock, inbound, returns and housekeeping settings
The remaining Sync Settings sections: returns, multi-company, inbound and stock, operational limits, provider-specific options, background jobs and housekeeping. Returns Behaviour (shown when the provider supports returns) Damaged Returns Location. ...
Clarus WMS adapter - process maps
How every flow in the LataSys 3PL Connector runs when the Clarus WMS adapter is installed. Transport: hybrid - writes are JSON:API REST under /api/..., reads are GraphQL via POST /graphql, both on the tenant's own subdomain ...
Clarus WMS adapter - setup and reference
Everything you need to connect the LataSys 3PL Connector to Clarus WMS: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. What this adapter provides Flow Supported Order push and despatch write-back Yes Order ...
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 ...
ShipHero adapter - setup and reference
Everything you need to connect the LataSys 3PL Connector to ShipHero: prerequisites, connection setup, mappings, capabilities and provider-specific behaviour. What this adapter provides Flow Supported Order push and despatch write-back Yes Order ...