Open-source manufacturing ERP, MES and QMS. Quoting, MRP, inventory, shop floor, quality and lot/serial traceability on one Postgres schema, with a REST API and MCP server. Self-host or use Carbon Cloud.
TypeScript ai-agentsbill-of-materialserpinventory-managementleanmanufacturingmanufacturing-execution-systemmcp-servermesmrpopen-source-erppostgresqlproduction-planningqmsquality-management-systemreact-routerself-hostedsupabasetraceabilitytypescript
Merge remote-tracking branch 'origin/main' into naveenkash/item-master-revision-data-copy
naveenkash51cfdf80f7cf
diff --cc docs/content/docs/reference/items.mdxindex dadeef54d7,389336e1ee..bfce47a895--- a/docs/content/docs/reference/items.mdx+++ b/docs/content/docs/reference/items.mdx@@@ -29,17 -29,8 +29,17 @@@ The tracking type sets how units are co## Revisions- Each revision of a part is its **own item record**, sharing the same part number but a different revision. A design change creates a new revision rather than rewriting the old one, so jobs built against an earlier revision keep their history.+ Each part revision is a separate item record with the same part number and a different revision. Creating a revision preserves the item used by existing jobs.+A new revision starts as a copy of the revision you created it from, so you don't set it up again. Along with the item's properties and its method, it carries over:++- **Batch Size**, **Scrap Percent**, and <Term id="lead-time">lead time</Term>+- each location's <Term id="reordering-policy">reordering policy</Term> with its parameters, such as the accumulation period and safety stock+- the <Term id="item-group">item group</Term>+- the preferred supplier, and every supplier part with its price breaks++Costs, the sale price, and stock are not copied. They belong to the revision they were recorded against. Change anything on the new revision and the old one is left as it was.+<Callout type="info">An item's <Term>costing method</Term>, one of *Standard*, *Average*, *FIFO*, or *LIFO*, lives on its cost record, not the item itself, and decides how consumption is valued.</Callout>diff --cc docs/content/guides/change-order.mdxindex 97dcd17bd8,d702aa4fb3..13641e1438--- a/docs/content/guides/change-order.mdx+++ b/docs/content/guides/change-order.mdx@@@ -59,33 -49,28 +49,30 @@@ method, removing all draft edits<Screenshot src="/screens/co-affected-item.png" label="Affected item with change-type selector" caption="An affected item's draft method open for editing on CN-000001, with the 'Change type' select on the item card." ratio="wide" />- - <Term id="change-order-change-type">Version</Term> revises how the *same* part is made. You edit its BoM and- BoP; release publishes a new method version and archives the old one. No new part, nothing superseded.- - **Revision** mints a new revision of the part (same Part ID, next revision). You edit its attributes,- documents, and method; release reveals the new revision and supersedes the old one.- - **Replacement Part** derives a brand-new part *number* from this one. Release reveals it and supersedes the- old part with it. The 1:1 replacement.- - **New Part** introduces a genuinely new part with no old part behind it. Release reveals it, but supersedes- nothing, because there's no predecessor to phase out.+ - <Term id="change-order-change-type">Version</Term> changes the BoM or BoP for the same part. Release activates+ a new method version and archives the previous version. It creates no item or supersession.+ - **Revision** creates the next revision under the same Part ID. Its draft supports attributes, documents, and+ method edits. Release activates the revision and supersedes the previous one.+ - **Replacement Part** derives a new part number from the affected part. Release activates it and supersedes+ the affected part in a one-to-one replacement.+ - **New Part** creates a part without a predecessor. Release activates it without creating a supersession.<Callout tone="amber" badge="A VERSION MOVES THE METHOD, NOT THE PART" title="Only Revision and Replacement Part supersede.">- This trips people up. A **Version** bumps the recipe on the existing bracket, so existing stock and history- stay put and nothing is superseded. A **Revision** and a **Replacement Part** each derive a new item *from* the- old one, so each auto-writes a supersession at release. A **New Part** is net-new — there's no old part to- phase out, so it supersedes nothing. Pick the wrong type and you either strand stock or fail to phase it over.- A purchased part has no method to version, so adding a **Buy** item lands on **Revision** automatically.+ A **Version** changes the method on the existing item, preserving its stock and history without supersession.+ A **Revision** or **Replacement Part** derives a new item and writes a supersession at release. A **New Part**+ has no predecessor and creates none. Because a purchased part has no method to version, a **Buy** item defaults+ to **Revision**.</Callout>- For the bracket we want the wall change to carry a new drawing revision and phase over cleanly, so this is a- **Revision**. You thicken the wall in the attributes, drop the extra fastener line from the BoM, and attach- the updated drawing — all on the draft.+ This bracket requires a new drawing revision and a stock phase-over, so select **Revision**. Update the wall+ attribute, remove the fastener from the BoM, and attach the revised drawing to the draft.-<Callout tone="amber" badge="PURCHASED PARTS NEED A SUPPLIER" title="A bought revision releases un-buyable unless you set its supplier up first.">-A purchased revision includes a **Supplier Parts** grid. Supplier parts are not copied from the old revision.-Before releasing a **Buy** revision, add its supplier, supplier part number, price, and ordering quantities.-Without a supplier part, the released item cannot be added to a purchase order.+<Callout tone="green" badge="PURCHASED PARTS KEEP THEIR SUPPLIERS" title="A bought revision inherits the old revision's suppliers.">- If the revised part were purchased instead of made, its line would carry a **Supplier Parts** grid. A Revision- draft starts with the old revision's supplier parts and price breaks, along with its lead time, batch size, and- reordering policy, so it releases ready to buy. You change the grid only where the new revision differs, such- as a new supplier part number. A **Replacement Part** or **New Part** starts with an empty grid, and that one- you fill in before you release.++A purchased revision includes a **Supplier Parts** grid. A Revision draft starts with the old revision's++supplier parts and price breaks, plus its lead time, batch size, and reordering policy. Change the grid only++where the new revision differs, such as a new supplier part number. A **Replacement Part** or **New Part**++starts with an empty grid. Add its supplier parts before you release, or the released item cannot be added to++a purchase order.</Callout>## Review the diff