UNBATCHED stock, forced syncs and a worked example

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 detail for a product, the product's UNBATCHED bucket at that location is cleared while the true batches are written - keeping both would count the same physical stock twice. You will see this on the report as an adjustment line on the UNBATCHED lot alongside the new batch lines.

Forcing a sync now

Three equivalent triggers, all role-gated to Ops and above, all logged to the instance chatter as manual runs:

  • Dashboard card > Perform Operation > Run Inventory Sync;
  • Operations > Inventory Syncs > Run Inventory Sync (pick the instance in the popup);
  • the Inventory Sync button on the instance form.

Worked scenario

Overnight sync, 3PL-master, apply immediately. Sprint reports 412 (product, batch) lines. 396 match Odoo exactly (unchanged). Batch N-M33916/25142 shows 46 at Sprint vs 50 in Odoo - an adjustment of -4 posts, traceable in the product's move history to the sync reference SYNC/00023. Two brand-new batches from yesterday's goods-in appear as new lots with expiry dates. One SKU Sprint reports ("PACKING-TAPE") has no Odoo product - an error line on the report, nothing changed, and you decide whether it should exist in Odoo at all.

    • 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 ...

    • 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 ...

    • 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 master and apply modes

      Stock Master - who is right? 3PL is Master (default). Differences are corrected in Odoo using native inventory adjustments - the same mechanism as a manual stock count, fully visible in Inventory's move history. Choose this when the goods physically ...

    • 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 ...