Product Updates

When nesting multiple different items onto a sheet of material, a lot of math goes into deciding how many sheets to buy, and how many parts you can make from the different pieces and dimensions you have on hand. This update, in short, optimizes the algorithm to maximize what you can make from existing pieces, and minimize how much you would need to buy to produce the parts.

When on the Items & Inventory > Materials grid - clicking the calculator will show a component that will display the density we store for that material and enable users to do any quick calculations needed to help them purchase by weight.

You can now update the Expected Receive Date and Promise Date on Purchase Orders via API using either the PUT or PATCH endpoint:

https://developers.fulcrumpro.com/api-schema#tag/Purchase-Order/operation/PatchPurchaseOrder

The lines data when creating a receipt now takes a lotNumber. If that lotNumber exists, it’ll use the existing lot on that item, if it doesn’t it’ll create the lot during the receiving.

https://developers.fulcrumpro.com/api-schema#tag/Purchase-Order/operation/PatchPurchaseOrder

‍

To keep things clean and performant, our system automatically deletes empty lots once all inventory has been removed. However, this caused an unintended side effect — when users tried to return materials that were originally picked from a now-deleted lot, that lot no longer appeared in Job Tracking. As a result, users had to post returns without a lot assigned, leading to inventory inaccuracies and incorrect job costing (often defaulting to $0 values).

With this release, we’ve enhanced the logic so that empty, deleted lots will now appear in Job Tracking whenever the user previously picked inventory from that lot for the same item. If a return is posted to a deleted lot, the system will automatically reactivate that lot to ensure both inventory balances and job costing values remain accurate.

‍

In Process Tracking checkpoints are a cool way to digitally capture quality data in Fulcrum, live. However, most people don’t have well structured data to import into Fulcrum during their onboarding, so it usually gets added later on. When added, it’s common for people to add default checkpoints by adding them Business Setup > System Data > Operations. But adding them didn’t impact items that already had that operation, only when that operation was newly added.

Now, after editing your default operations setup, you can click the “Apply IPT Changes to Items” to update all items that have that operation!

In this update, we’ve added the ability to switch material items back to fixed quantity mode. This gives you the flexibility to use scaling when needed, while still allowing for direct control over pick values. To use this option, simply click the ‘lock’ to edit the pick quantity. Once adjusted, the quantity will operate as a fixed value rather than scaling with the bounding box.

This update will be available to all customers who currently have the “Scale Material Items on BOM” feature enabled. We’ll begin rolling it out to all materials users next week.

There’s a new public API endpoint for attaching certifications. It works for PO receipts, sales order receipts (customer supplied), and attaching directly to lots.

For example, to attach directly to an item lot, (in addition to the file) use the below image. Note that because you’re supplying the specific receipt line, Fulcrum can automatically identify the related lot.

‍

If you accidentally enter the wrong completed quantity on a job, you can correct it directly from the Job page.

1. Scroll down to the Operations section.
2. Click the ✏️ pencil icon next to the item you want to update.

This opens a window showing the related inventory transactions for that item. When you update the completed quantity, both inventory quantities and cost values are automatically adjusted.

Example: Suppose you completed a subcomponent job and entered the wrong quantity:

• Before correction
  • Reported: 10 units completed at $15 each → $150 total.
  • 8 units were picked to a parent item ($120), leaving 2 units in inventory ($30).
  • The finished good shipped with a total cost of $200, which included $120 from the subcomponent.
• After correction (actual = 15 units)
  • The same $150 total cost is now spread across 15 units → $10 each.
  • 15 units are added to inventory at $10 each → still $150 total.
  • 8 units picked to the parent are re-valued at $10 each → $80 total (a $40 decrease).
  • The finished good’s value also decreases by $40, which carries forward to the shipment cost.
  • You now have 7 units in inventory (instead of 2), worth $70 total.

❗Note — this feature requires the Roll Forward Job Cost Changes setting to be enabled. It works by retroactively updating both the quantity and cost of previously completed inventory. If you can edit the Actual Qty but don’t see all the related inventory transactions, check your Inventory Adjustment Cutoff window in Items & Inventory Settings. Only transactions within the adjustment window are available to edit.

When you try to reopen a job, the system checks for any inventory transactions on the same item/lot that happened after the job’s receipts. If such transactions exist, reopening is blocked to prevent issues with downstream activity.

With this enhancement, other receive transactions are no longer included in that check—since those receipts aren’t affected by reverting earlier ones.

The result: this change gives you more flexibility to reopen jobs when you need to, without compromising data integrity.

The WIP report shows two sets of costs for each in-progress job:

• Total Costs – all costs accrued so far.
• To Make – accrued costs tied to items still being made, not yet added to inventory.

Totals aren’t changing. What’s new is how costs from made-to-stock subcomponents are grouped within the report. Instead of being placed all under material, those costs are now distributed across labor, material, outside processing, and machine buckets—using the same breakout as the subcomponent itself. You may not even notice the change, but it helps the report stay more consistent throughout the process and reduces small discrepancies later on.

Previously, when receiving an item in Fulcrum, the cost of the item would be price on the Purchase Order. However, people often want to include things like shipping costs in the landed cost of the item. Now you can! To do this, you can open a fee line item on the Purchase Order and tell Fulcrum how to distribute that cost across the parts on the PO. Thanks to other recent improvements, this will also retroactively update job costs wherever this item might already have been picked.

Check out this video!

SolidWorks imports are a convenient way to get the Bill of Materials quickly into Fulcrum. However, SolidWorks doesn’t provide any information about the operation steps to make the item. So once you import the BOM, the operations needed to be added to the items. Now, you can select a template item, which will copy the steps from that item to any newly created make items on your SolidWorks import.

Previously, the way demand planning worked is that whenever something changed that impacted demand, Fulcrum would run an update to that information and recalculate the new demand. This meant there was a delay between the update itself and what showed in demand planning, and required a complex calculation for every change.

Now that Fulcrum uses SQL, the data in demand planning can be efficiently calculated live - no more waiting for the calculations to refresh!

Previously, the only way to get and manage required items on a work order was to make sure those items were on the jobs and associated to the work-ordered operation. Now, you can manage the items directly on the work order. This is a huge time-saver as you can edit the items once on the work order, as opposed to every single job associated to the work order.

Users can log into job tracking using their PIN login. Previously, once someone was logged into Job Tracking, they could then navigate to the main site and still be treated as logged in. Now, if that user has only entered their PIN for the session and not their password, then navigating to the main site will prompt the user for their password.

‍