Per-change, not per-day
Every meaningful edit makes a version. A quick flurry of edits by the same person collapses into one, so the history stays readable instead of cluttered.
The canvas
Every change versioned. Open your shop as it was at any moment.
Your shop and its BOMs are versioned on every change. Time-travel to any past state, read-only, and see exactly what changed, who changed it, and when.
×2×1
Supplier
Acme Metals
Component
Battery pack
End product
Camp Lantern
Customer
Summit Outfitters
Viewing v1read-only
Version v3
The new way
How this works in the future of MRP.
In a legacy system, edit a BOM and the version you replaced is gone. TuringDock keeps every version, so months later you can open the exact recipe a build shipped with and see precisely what changed.
How it works
The version number lives on the canvas
The current version sits in the bottom-left corner. Click it to open the full history: each entry names what changed, who changed it, and when.
Open the canvas as it was
Pick any version and the whole shop re-renders as it was at that moment, read-only, with a subtle tint and a one-tap way back to the live canvas.
Per-product BOM history, scoped
Open a product to see every change to just its recipe: what was added, retuned, or removed, line by line, without scrubbing the whole canvas.
Common questions
- What gets versioned?
- Every structural change to the shop: parts, suppliers, customers, the links between them, and BOMs. Each version carries a plain-English summary, who made it, and when.
- Why isn't there an entry for every tiny edit?
- Rapid edits by the same person collapse into one version, so renaming a part, retuning a quantity, and connecting an edge in the same sitting read as a single entry. The history stays readable instead of cluttered.
- How do I look at a past version?
- Click the version number in the bottom-left corner of the canvas to open the history, then click any entry. The whole shop re-renders as it was at that moment, read-only, with a clear way back to the live canvas.
- How do I see the BOM history for one specific product?
- Open the product and expand its Version history to see every change to that recipe, each line naming the component and what changed. This is scoped to that product, so unrelated edits elsewhere don't clutter it.
- What's the main use case?
- Quality investigations and customer disputes. When a defect surfaces months after shipping, open the product and find the recipe change around the ship date to see exactly what parts went into that build.
- Can I roll a version back?
- Today you can open and review any past version of the shop or a product's BOM in full. One-tap restore is on the way; until then, nothing is lost, since every past state stays browsable.
- Who is a change attributed to?
- Each version shows the person who made it. Changes Alan makes are labelled as Alan, so you always see who, or what, made each edit.
- Does it stay fast as history grows?
- Yes. Years of edits stay browsable, and opening any past version stays quick no matter how long your history gets.
Related features
Build what’s next.
Leave the MRPing to our AI. Free to start, set up in an afternoon.
Get started for freeLast updated 2026-06-13