Stock, inbound, returns and housekeeping settings

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 mapped warehouse the first time it is needed, then remembers it here. Point it at your own location if you already operate one. Restockable lines always go to normal sellable stock. See Returns for how grading works.

Inbound and Stock Behaviour

Auto-validate GRNs (default on; shown with GRN support). On: when the 3PL confirms goods received, the Odoo receipt is reconciled to the reported quantities/batches and validated immediately; shortages become a backorder receipt so nothing is silently dropped. Off: the reported detail is posted to the receipt's chatter and an activity asks a person to review and validate - the right choice while you are still building trust in a new 3PL's counts.

Stock Master (default 3PL is Master). The single most important inventory decision. 3PL is Master: inventory syncs set Odoo's stock to match the warehouse count, using native, fully-auditable inventory adjustments, batch by batch. Odoo is Master: syncs never change Odoo stock - every difference is recorded as a discrepancy line on the sync report for a person to resolve. Example: most 3PL businesses run 3PL-master (the goods physically live there). Run Odoo-master temporarily during a stock dispute: you keep full visibility of what the 3PL claims without letting it move your books.

Stock Adjustments (default Apply Immediately). Only meaningful with 3PL-as-master. Apply Immediately: differences become posted inventory adjustments during the sync. Leave as Counted Quantities for Review: differences are staged as counted quantities in Inventory > Physical Inventory where a stock controller applies or rejects them - a half-way house that keeps human sign-off while the 3PL still supplies the numbers.

Background Jobs

Run Flows as Queue Jobs (default off). With the OCA queue_job module installed on a Linux server, each operation (each order push, each status check…) runs as an individual, deduplicated background job instead of inline in the scheduler - better throughput and isolation for high volumes. The switch explains itself honestly: it is inert on Windows hosts (the OCA job runner is POSIX-only) and hidden when queue_job is not installed. Failures still land in the Sync Log with one-click retry either way.

Housekeeping

Keep Logs (days) (default 90). Sync Log entries older than this are deleted nightly. Set 0 to keep everything forever. Chatter history on instances, orders and returns is never touched by this - only the technical API log.

    • Related Articles

    • Order behaviour settings

      These settings decide how orders leave Odoo and what happens when reality at the warehouse disagrees with the plan. Each entry covers what the setting does, its default, and a scenario where it matters. Order Behaviour Send Orders Automatically ...
    • How FBM stock reaches Amazon

      "I changed the stock in Shopify, so why has Amazon not updated?" is one of the questions we are asked most often. This article explains exactly when your merchant-fulfilled (FBM) stock is pushed to Amazon, so you can tell the difference between a ...
    • 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 ...
    • 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 ...
    • Settings reference

      Settings is where you manage the app's connection to Amazon, decide which marketplaces your store maps to, choose which AI engine writes your listing content, and look after the data the app stores in your Shopify store. It is organised into five ...