Features

• Auto raw SGR move per MO — _get_moves_raw_values is extended so that every MO whose finished product has an sgr_product_id gains one extra raw component move for the SGR product, with quantity equal to the produced quantity in the SGR product's UoM.
• BoM stays clean — the SGR component is not injected into the BoM itself, only into the MO raw moves at runtime. The same BoM can therefore be used in test environments or by analysts without carrying packaging noise.
• Per-MO opt-out — mrp.production.sgr_auto_lines adds an Auto-add SGR Component boolean on the MO form (next to bom_id), defaulting from the company-wide toggle. Disable on MOs whose BoM already declares the SGR packaging explicitly.
• Works on any production type — manual MOs, MOs from MRP, MOs from sale-order routing all go through the same hook, so the SGR consumption is captured no matter how the order is created.
• Plays nicely with stock reporting — the consumed SGR products appear as standard internal stock moves and feed the parent module's SGR Stock & Movements and SGR Position reports unchanged.
• Composable with nexterp_sgr_account — when the SGR liability account (462/461) is set as the SGR product's expense account, the cost of consumed empties books on the balance sheet rather than on manufacturing cost, keeping the deposit out of the P&L.

Configuration

1. Link each finished product to its SGR companion

On every finished good produced by manufacturing that is subject to SGR (a bottle of beer, a can of soda, a jar of yoghurt drink, etc.), open the product in Inventory → Products and set the SGR Deposit field to the matching SGR product (the one with the right category — Glass Small, Plastic Large, Metal, etc.). This is the standard field provided by nexterp_sgr; no extra field is added by this module on the product itself.

2. Stock the SGR packaging

Make sure the warehouse source location used by the MO actually holds the SGR packaging — typically purchased upstream through nexterp_sgr_purchase or received from RetuRO as fresh empties. The MO will reserve the SGR component like any other raw material, so the usual reordering rules apply.

3. Per-MO opt-out

Each manufacturing order exposes an Auto-add SGR Component boolean next to the BoM selector. The default is inherited from the company setting Settings → Inventory → SGR → Auto-add SGR Lines.

• Keep it enabled when the BoM is purely about ingredients and the SGR packaging should be appended automatically.
• Disable it on the rare MOs whose BoM already lists the SGR packaging as an explicit component (legacy BoMs, edge cases, etc.) — the module then takes no action and the BoM line is used as-is.

4. Costing accounts (optional)

If you also install nexterp_sgr_account and configure an SGR Liability Account on the company, that account is automatically used as expense account on every Is SGR Product. The cost of consumed empties then books on the liability account at MO close instead of on a manufacturing cost account — which is what you want for SGR, since the deposit must not show up in P&L.

How it works

Bottling scenario

1. The finished product (e.g. Beer 0.5L Glass) has its SGR Deposit field set to SGR Glass Small. Both products are stockable.
2. Create a manufacturing order to produce 1000 units of beer.
3. Open the MO. The Components tab lists:
   • the BoM-defined ingredients (beer content, label, cap, …);
   • plus 1000 units of SGR Glass Small appended by the module.
4. Reserve and consume the components as usual. The MO reservation will pull the empty bottles from the warehouse source location like any other raw material.
5. Close the MO. You now have 1000 finished beer items in stock and 1000 SGR Glass Small units have been consumed from the empty-bottle pool.

Downstream consistency

If the bottled beer is later sold (through nexterp_sgr_sale / nexterp_sgr_pos) or invoiced (through nexterp_sgr_account), the deposit line is added on those documents per the usual flow. There is no double-counting because the SGR product on the MO and the SGR product on the sale invoice are tracked at the same per-unit packaging level.

Opt-out per MO

If a specific MO uses a BoM that already declares the SGR packaging as an explicit raw component, untick Auto-add SGR Component on the MO header. The module then skips the runtime injection and the BoM line takes effect on its own — preventing double consumption of empties.

Versions

19.0.1.0.0 (2026-05-25)

• Changelog tracking starts at this release.