When 80 units are available and two orders need 120, which one gets the stock? In an Odoo application, the answer depends on the reservation method, the moment each order is confirmed, and an operating decision your company should write down before go-live. This article draws on the Odoo 19 documentation 1 and GS1’s global material on event data 2; the operating recommendations are ours. To learn about our team, visit the home page.

How reservation methods work in Odoo

The documentation describes three methods: At Confirmation, Manually, and Before scheduled date. The method is set per operation type (Inventory ‣ Configuration ‣ Operation Types), not company-wide, and using it requires the Sales and Inventory apps. It is not available when the operation type is Receipt. It can also apply to manufacturing, repairs and internal transfers if the relevant apps and settings are enabled 1.

Comparing the three methods

  • At Confirmation: Odoo reserves when the sales order is confirmed, and only if stock is available. In practice, earlier confirmation can allocate stock to an order due later, as in our example; review actual reservations rather than assuming delivery dates alone set priority. If stock is short, the availability icon turns red. Starring a delivery order does not prioritize it for reservation under this method; it only affects how delivery orders are displayed in Inventory.
  • Manually: after the quotation is confirmed, someone checks availability and reserves the quantity. It gives the most control but demands discipline in follow-up.
  • Before scheduled date: you set how many days before the scheduled delivery date reservation may happen, with a separate window for starred transfers. The default is 0, and the documented workflow uses the product customer lead time to derive a scheduled date. Check the delivery order’s actual date before relying on its reservation window.

Our recommendation: do not use one method for everything. Choose per operation type, based on product type, rotation speed and delivery-date commitments.

A hypothetical numeric example

This is a hypothetical illustration, not a customer case. Physical on-hand is 100 units, 20 of which are already reserved for other confirmed orders, leaving 80 unreserved and eligible. There are no incoming receipts, no multiple locations and no quality blocks. Order A is 70 units due 25 November; order B is 50 units due 20 November. The two scenarios are independent and start from the same baseline, so do not add them together.

Item Scenario 1: A confirmed first Scenario 2: manual decision to allocate B first
Physical on hand 100 100
Reserved for other orders 20 20
Unreserved available 80 80
Order A (70) 70 reserved 30 reserved, short 40
Order B (50) 10 reserved, short 40 50 reserved
Total reserved 20 + 70 + 10 = 100 20 + 30 + 50 = 100

New demand totals 120 against 80 available, so the shortage is 40 units either way. Reservation does not move stock: physical quantity stays at 100 until actual delivery. Scenario 2 is an operating decision, not an automatic customer-priority promise. A person or a policy makes the choice, and any manual reallocation must be approved. Odoo provides the Forecasted Report and an Unreserve button to re-order priorities between orders 1.

Timing under Before scheduled date

Assume a scheduled date of 25 November 2026, with the normal window set to 2 days and the starred window to 3. Reservation would be expected from 23 November for normal transfers and 22 November for starred ones. These are calendar days, not business working hours, and the setting is a maximum number of days before the date. Validate the scheduled job’s timing and the configuration in your own instance rather than assuming a reservation at exactly midnight.

The documentation also notes that Check Availability lets a user reserve manually ahead of the window. No reservation does not necessarily mean a shortage: stock may be available while reservation has simply not started yet 1.

Warehouse and sales responsibilities

  • Sales: do not promise a date before you know the reservation status. Confirmation time is part of the decision because it can affect allocation.
  • Warehouse: verify locations, statuses and dates, and review existing reservations before changing anything.
  • Approval: every unreserve in favor of another order goes through a named approver, and the affected order’s salesperson is told before the customer promise changes.

GS1 describes a supply chain event as recording what happened, when, where and in what business context, so visibility can span locations and organizations 2. We take only a principle from this: a reservation decision needs trustworthy location, status and time data. It does not mean Odoo reservation implements EPCIS or that any standard requires it. Availability reports also depend on locations, routes and other reservations, so do not expect one global stock number across warehouses. And a reservation is not a delivery, a transfer of ownership or an invoice.

Practical implementation scope

We suggest starting with an inventory of operation types and a reservation method for each, then setting customer lead times on the relevant products, writing a short policy for priority changes, and training both the sales and warehouse teams. See the Inventory and Sales pages for details, and the retail industry page for sector context. To size the project, use the calculators. If you only want to see the general Sales and Inventory interface, there is the Odoo demo; it does not showcase advanced features.

Acceptance tests

  1. Set At Confirmation and verify that a confirmed order with enough stock reserves immediately.
  2. Confirm an order with insufficient stock and check the red availability icon and the reserved quantity.
  3. Try manual reservation: check availability, reserve, and verify that demand and quantity match.
  4. Configure Before scheduled date (2 days, 3 for starred) and verify when reservation actually starts.
  5. Use Check Availability to reserve early and confirm the status changes.
  6. Cancel an order or deliver part of it, and record how the reservation changes in your instance, without assuming undocumented behavior.
  7. Run the A and B example with your own numbers and confirm that any unreserve goes through written approval.

Frequently asked questions

Does a reservation mean the shipment has left?

No. A reservation allocates stock to an operation; delivery, ownership and invoicing are separate steps.

Does a starred delivery order get stock first?

Under At Confirmation, starring gives no reservation priority. Under Before scheduled date, the star only changes the day window.

Does no reservation mean a shortage?

Not necessarily. Stock may be available while the reservation is deferred until its window.

Conclusion

Reservation is as much an operating decision as a system setting: a suitable method per operation type, a known confirmation time, and a written policy before two orders collide. If you would like a concrete, scoped discussion about your distribution operation, start by sizing the project with the calculators and then contact us to define scope and acceptance tests together. You can always return to the home page.

Source notes

  1. Odoo 19 documentation on reservation methods, plus its At Confirmation and Before scheduled date pages. We took only: the three methods, per-operation-type configuration, required apps, unavailability for Receipt, the day windows, the role of starring, and Check Availability. The numeric example, approval advice and responsibilities are ours.
  2. GS1’s public support article on EPCIS, used only for the idea that events record what happened, when, where and in what context, giving visibility across locations and organizations. It says nothing about Odoo and does not establish integration, certification or a requirement.