One Wizard Instead of Two Manual Transfers

One Wizard Instead of Two Manual Transfers

If your company runs more than one warehouse under the same legal entity, you've probably hit this in Odoo. Moving stock from Warehouse A to Warehouse B out of the box means creating two separate transfers: one outbound from the source, one inbound to the destination. Every product line and quantity has to be typed in twice. Miss a line, or let the two documents drift out of sync, and you end up with a reconciliation problem nobody notices until a stock count doesn't add up.

This isn't a one-off complaint. Looking across our own support history, this exact pain point shows up for roughly 1 in 9 of the multi-warehouse teams we work with. It's a recurring theme, not an edge case.

The fix: one form, two transfers, automatically

For one client, we built a small custom wizard that asks for exactly three things: a source location, a destination location, and the product lines to move. A transit location is selected automatically, and it can be overridden. Confirm once, and Odoo generates both transfers behind the scenes, correctly linked through the transit step, with the relationship between the outbound and its matching inbound maintained natively instead of by memory. A companion report lets anyone check an outbound against its matching inbound side by side: validation dates, references, and statuses in one view, instead of hunting through two separate documents to confirm a transfer actually completed.

The second, smaller win came from how the product lines get entered. Instead of clicking "add a line" repeatedly for every SKU, the team can paste a block of SKU-and-quantity pairs straight from a spreadsheet, hit parse, and the wizard fills in every line at once. For a transfer covering dozens of products, that turns a genuinely tedious task into a five-minute one.

The bigger pattern

None of this is glamorous. There's no dashboard, no AI, no new report type. It's a wizard that removes one specific piece of repetitive manual work and one specific class of reconciliation error, and we don't have a clean "hours saved" figure to quote, because nobody was timing the old process. What we do know is straightforward: the standard flow means two manual transfers, re-keying product data twice, and manually matching one to the other after the fact. The custom flow means one entry, zero re-keying, and an automatic match. That's usually where the real ROI in ERP customization lives, not in the features that demo well, but in the ten-minutes-a-day tasks that quietly eat a team's week.

If there's a process in your own Odoo that still means re-typing the same data twice, or manually keeping two documents in sync by memory, that's usually worth a second look.